Revenue operations5 nodes$59 setup
CRM synchronisation
Keep CRM contacts, deals and activity in step with the rest of your stack.
The business problem
Duplicate and stale CRM records erode trust in reporting and cause reps to miss follow-ups.
Who it is for
Sales teams running more than one system of record.
What the workflow does
▶
Record changedtrigger
Has a usable email?◇
Has a usable email?condition
true → Upsert CRM contact · false → Flag incomplete record◉
Upsert CRM contactintegration
Flag incomplete record✉
Flag incomplete recordnotify
Done■
Doneend
terminalSetup requirements
Connect a CRM with write access. Configure the field mapping and the de-duplication key (email).
| Integration | Status | Actions used |
|---|---|---|
| HubSpot | Beta | Create contact, Log activity |
Limitations, stated plainly
- Any integration listed as “requires setup” will fail until an adapter is enabled and credentials are stored.
- AI steps without a configured provider produce deterministic simulation output, labelled as such in the run log.
- Steps marked optional record a failure and let the run continue; all other step failures stop the run.
- Approval steps pause the run until an authorised teammate decides.