Turn a conversation into a board card automatically

Every conversation that lands via WhatsApp, Instagram, or Web chat can hide a concrete task: a return, a complaint, a special order. Copying those details into your project board by hand is slow and error-prone. The good news is you can turn a conversation into a board card automatically with the Omnifox workflow engine, so the agent never has to touch it.

In this guide we build the flow node by node using the visual workflow editor (the chat/omnichannel one, not the IVR editor).

What we're building

The goal is simple: when a conversation meets a certain condition, a card is created on your board with the phone number and email already filled in and a direct link back to the chat. Then we move it to the right group and assign an owner.

The node order looks like this:

Trigger Tag added → Create card from conversation → Move to group → Update cell → Add internal note

Step 1: pick the right trigger

Two triggers work great for this case:

• Message received with a keyword filter (say "complaint" or "refund"). Use it when you want the card to appear the moment a customer mentions something.
• Tag added, which is what we'll use here. An agent (or an earlier workflow) tags the conversation as complaint, and that fires the card creation.

Using Tag added gives you control: you don't spawn a card for every single message, only when someone decides the case deserves tracking on the board. Remember the golden rule: one trigger per workflow.

Step 2: create the card from the conversation

The star node is Create card from conversation. Unlike the generic Create item, this node already knows the chat context: it auto-fills the contact's phone and email and drops a link to the conversation inside the card. Whoever opens the card can jump back to the original chat in one click.

In the node settings you choose:

• The destination board (for example "After-sales").
• The starting group where the card lands.
• The card title: lean on variables. A good title is Complaint — {{$contact.first_name}} {{$contact.last_name}}.

If you want a case summary, use {{$conversation.summary}}, which pulls the AI-generated summary of the conversation. And if a variable doesn't exist, Omnifox replaces it with an empty string: an empty {{}} will never break your title.

Step 3: move the card to the right group

Once created, we chain a Move to group node to place it by priority or stage. For example, if the trigger was the urgent tag, move it to the "Priority" group.

Here's a key concept: chaining node outputs. The Create card from conversation node leaves the id of what it created available as {{steps.last.created_item_id}}. The following nodes (Move to group, Update cell) use it to know which card to act on. You don't have to look it up: it's handed over from the previous step.

Step 4: fill fields with Update cell

With Update cell you populate specific board columns: source channel ({{$conversation.channel_name}}), a date, or a status field. You can add several Update cell nodes in series, one per column, or use a Switch upstream to decide which value goes where based on case type.

Step 5: assign an owner and notify

To close it out, you have two paths depending on how you work:

1. Let the board handle assignment (auto-assign by group), or
2. Use an Add internal note node on the conversation so the agent knows the card already exists and on which board.

You can also add Notify team by email or Post to Team if the case needs eyes right away.

Handy variants

• Fire on first message: switch the trigger to Message received with the first only filter to create a "new lead" card the moment someone writes in for the first time.
• With a gate: insert a If (single rule) or Contact has tag node before creating the card to filter by channel or segment.
• Dual destination: with Run in parallel you can create the card and, at the same time, Create follow-up task in the CRM.

Common mistakes

• Creating a card per message. If you use Message received with no filters, you'll flood the board with duplicates. Filter by keyword or fire on a tag.
• Forgetting the chat link. The Create card from conversation node adds it for you; don't replicate it by hand with Create item, which doesn't know the conversation context.
• Losing the card id. If you slot in another node that also creates something, {{steps.last...}} will point to the last thing created. Order the chain carefully.

Put it to work

Turning chat into actionable work is one of those automations that pays for itself in the first week. In Omnifox the workflow editor is visual and this flow takes minutes to assemble. Try it with a test tag and watch the card build itself.