CRM and record triggers: deal won, lost and no activity

Automate your pipeline with the semantic deal triggers and the generic record triggers shared by CRM and Projects.

Jun 26, 2026

Watch this step in the video · CRM: triggers and nodes

What CRM and record triggers are

Omnifox's Workflows engine is unified: the same editor automates chat, CRM, Projects and Boards. For the CRM there are two families of triggers under the Records category:

  • Semantic deal triggers: direct shortcuts like Deal won. You pick the business idea, not a technical condition.
  • Generic record triggers: they work over any object (deal, task, board item) by filtering on Record type.

The semantic ones are sugar over the generic ones: when a deal moves to a stage with a won status, Omnifox also fires Deal won so you don't have to hand-build a stage + status condition.

Semantic deal triggers

  • Deal won (deal.won): the deal entered a stage marked as won.
  • Deal lost (deal.lost): it entered a stage marked as lost.
  • Deal with no activity (cold) (deal.no_activity): an open deal that logged no activity for N days. A daily detector feeds it; it exposes $trigger.days_inactive and $trigger.last_activity_at.
  • Deal created (deal.created) and Deal stage changed (deal.stage_changed): for follow-up cadences.

All of them accept the Specific pipeline filter (leave empty for any pipeline) and expose the deal's variables plus the linked contact ($contact.name, $contact.phone).

Generic record triggers

  • Record created / updated / completed / overdue.
  • Stage / status changed (record.stage_changed): exposes $trigger.column_old and $trigger.column_new.

Filter with Record type (deal, task, item) when you want a workflow that applies to a single object type.

Requirements

  • Available on all plans (from Lite), with a monthly quota of workflow runs based on your plan.
  • Actions on Projects (for example, creating a project card from a deal) need Projects, available from the Conecta plan.
  • At least one CRM pipeline configured under Contacts & CRM.

Steps

  1. Go to Settings → Workflows and click Create workflow.
  2. In the palette, open the Records category and drag, for example, Deal won.
  3. (Optional) In the inspector, set Specific pipeline to limit firing to one funnel.
  4. Connect CRM actions: Create project card from deal (great for onboarding on a win), Log activity, Change stage, or notify with Post to Team / Send email.
  5. Personalize the message with Insert variable using deal and contact data.
  6. Flip the switch to activate and Save.

Star recipe: win to onboarding

Trigger Deal won to action Create project card from deal. The card is born with the customer's data and a link back to the deal, so Sales hands off to Operations without copying anything by hand.

How to verify

Move a test deal into the won/lost stage and check the workflow's run history. For Deal with no activity, remember it depends on the daily detector, so the firing is not instant.

If it doesn't work

  • Deal won doesn't fire: confirm the target stage is flagged with a won status in the pipeline settings; the trigger relies on that status, not the stage name.
  • It fires on the wrong pipeline: check the Specific pipeline filter.
  • deal.no_activity is slow: the detector threshold is global (7 days by default). The node's Days inactive filter narrows it per workflow but doesn't speed up the sweep.

Tips

  • Use Deal with no activity to re-engage cold leads with an automatic message before marking them lost.
  • If the semantic triggers don't cover your case, drop down to Stage / status changed with a deal type filter and compare $trigger.column_new.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp