From won deal to automatic onboarding project in Omnifox

You closed the sale. Now the part that actually retains the customer begins: onboarding. If that kickoff depends on someone remembering to create the project, alert the team and greet the customer, sooner or later it falls through. The fix is a workflow that fires by itself the moment you win the deal. In Omnifox workflows the Deal won (deal.won) trigger lets you turn every sale into a live onboarding project in seconds. Let's build it.

The trigger: Deal won (deal.won)

Every workflow has a single trigger. Here we use Deal won (deal.won), which fires the moment a deal moves to the "Won" stage in your CRM. It does not matter who moves it or from where: the event starts the flow.

From the trigger you already have deal data as variables: {{$trigger.title}} (the deal name), {{$trigger.amount}} (the value) and {{$trigger.stage_name}} (the stage). You will reuse them across the following nodes.

Step 1: create the onboarding project

The heart of this flow is the Create project from deal node. It is built exactly for this: it takes a won deal and generates an onboarding card or project, copying the deal data and leaving a link back to the original deal. That way the implementation team sees where it came from, how much it is worth and who the customer is without hunting for anything.

This node exposes the id of the created item so you can chain it: {{steps.last.created_item_id}}. You will use it if you want to, say, move that card between groups or assign it later.

Step 2: seed the first tasks

An empty project does not start itself. Add one or more Create follow-up task nodes for the typical onboarding actions: schedule the kickoff call, send the contract, set up the account. If your process lives on boards, you can use Create item and then Move to group to drop it into the "To start" column.

It is also a good moment to Assign deal owner or hand the card to an onboarding lead with round-robin routing, so the work never ends up orphaned.

Step 3: alert the internal team

The implementation team has to hear about it. The Post to Team node drops a message in the right Space with the new customer's details: {{$trigger.title}}, {{$trigger.amount}} and a link. If you prefer something more direct, use Send DM to the owner, or Create reminder for the kickoff.

The order so far:

1. Deal won (deal.won) (trigger)
2. Create project from deal (spins up the onboarding)
3. Create follow-up task (kickoff, contract, setup)
4. Assign deal owner (onboarding lead)
5. Post to Team (internal alert)

Step 4: welcome the customer

The customer who just bought should feel the gear change. If you are inside the conversation's 24-hour window, use Send message with a warm greeting and the next steps. If the trigger came from the CRM and not a recent chat, it is safer to use Send WhatsApp template with an approved welcome template, injecting {{$contact.first_name}} and the name of their manager.

You can cap it off with the Book appointment node to reserve the kickoff call directly, or Send email to customer if your onboarding starts by email with a checklist.

Full example flow

Deal won (deal.won) -> Create project from deal -> Create follow-up task (x3) -> Assign deal owner -> Post to Team -> Send WhatsApp template (welcome) -> Book appointment (kickoff)

Common mistakes

• Duplicate projects. If several stages count as "won", you may fire twice. Tie the trigger to one stage or add a Condition on {{$trigger.stage_name}}.
• Greeting out of window with a free message. If there is no recent chat, use Send WhatsApp template, not Send message.
• Not using the chained id. If you plan to move or assign the created card, remember {{steps.last.created_item_id}} right after the node that creates it.

Variants

• Add Log activity/note on the deal to record the handoff to onboarding, including who sold it and the closed amount.
• Fire a second workflow with Call another workflow for the first-week email sequence, keeping welcome logic separate from nurturing.
• Use Update contact to switch the lifecycle stage to "Customer" so your funnel reports stay clean.
• Add Add tag (for example onboarding-active) so support and customer success can see at a glance what phase each new account is in.
• Schedule the first check-in with Schedule message for a week out, so it happens whether or not anyone remembers.

Automating onboarding from the CRM is one of those things that feel bad when missing and go unnoticed when they work: every won deal starts itself, with a project, tasks, a team alert and a welcome. Build it in the visual editor in Omnifox and never let a new customer fall through the cracks again.