Workflows

Workflows automate what happens after something occurs in your workspace. A workflow starts from a trigger and then runs a series of nodes. A trigger can be a form submission, an incoming webhook, a meeting status change, a new CRM record, and more. Nodes route the lead, enrich it, update your CRM, send a notification, book a meeting, or call an outside system.

​

Triggers and nodes

Every workflow has two kinds of building block:

• A trigger starts the workflow. Each workflow begins with exactly one. See Triggers for the full list.
• Nodes are the actions that run after the trigger fires, laid out on a canvas. A node can route a lead, write to your CRM, or add someone to a sequence. It can also send a Slack message, show a scheduler, branch on a condition, and more.

​

The workflows list

Opening Workflows shows every workflow in your workspace. The home page shows your workflows as cards under folder tabs, or as one table. If your home page shows cards, the list below applies:

• Folders: tabs across the top group your workflows. All Workflows shows everything, and Unfiled shows workflows with no folder.
• Folders you create appear alongside them. Use the folder menu to rename, reorder, or delete a folder.
• Filter by: narrows the list. Under Status, choose Active, Draft, or both.
• Under Trigger, choose one or more trigger types to show only workflows that start that way.
• Created by: a separate dropdown to show workflows from All creators, Created by you, or a specific teammate.

Each workflow’s card shows a status badge:

• Draft: never published.
• Paused: published, but turned off.
• Active: published and turned on.

​

Create a workflow

​

Add a node

Nodes sit on the builder canvas as connected nodes. Drag from one node to another to connect them, or branch a node into more than one path. Select Add Node to open the node picker. Choose a node to add it to the canvas. The picker groups nodes into sections: Logic, Actions, AI, Records, Notifications & Reminders, Enrichment, and Sequencing. Nodes that create, match, or update CRM records are in the Records section. A section appears only when it holds nodes your workspace can use. Each node you add starts unconfigured, so open it to set it up.

​

Insert data from earlier in the workflow

Most fields accept values pulled from the trigger or from an earlier node. This lets a CRM field, a Slack message, or a webhook body carry the lead’s real data. Type {{ in a field to open the data picker. You can also select the button in the field’s toolbar. The picker groups values under CRM, Enrichment, AI, Slack, Default Objects, and Workflow. Default Objects holds the person and company details every trigger provides. Workflow holds scheduling and meeting details, the trigger data, and any values earlier nodes produced. In a Slack message field, type @ instead, or select the @ toolbar button. This opens a separate picker for mentioning people. The mention picker offers mapped Slack recipients, user groups, and upstream references, such as an account owner. An upstream reference resolves to a real Slack user when the message sends. Outside Slack message fields, @ has no special meaning. Use {{ there.

​

The Enabled switch

Each workflow has a deployment control in the builder’s top Context Bar. Turn it on to let the published version run for live traffic. Turn it off to pause the workflow without deleting anything. The switch stays off until you publish the workflow at least once.

​

Test a workflow

For a workflow that starts from a CRM record trigger, the payload opens as a record. It already lists the record’s identifying field, for example email or domain, and any fields your trigger’s condition checks. Every listed field starts blank. Fill in real values before you run the test. Testing is not available yet for workflows that start from a Meeting Status or an Extension trigger.

​

Publish a workflow

Your edits save to a draft automatically. The draft does not run for live traffic until you publish it.

• Select Publish to make the current draft live. The button reads Publish whenever you have unpublished edits.
• When the live version matches your draft, a status label replaces the button. It reads Published plus the live version number, for example Published v3.
• Each publish creates a new version, so you can see what was live and when.

Each workflow has one draft, shared by everyone in your workspace. Publishing takes the whole draft live, including any unpublished changes your teammates made. The version control in the top Context Bar shows whether you are editing the draft or viewing a published version, including a count of unpublished changes.

​

If more than one person is editing

Everyone works on the same draft, so there is no separate copy per person and nothing to merge.

• Publishing publishes everything in the draft, yours and your teammates’. If someone is still part-way through a change, publishing takes that unfinished change live too.
• Agree on who publishes. Publish once you are both finished.
• Editing different nodes is safe: both sets of changes land.
• If you both edit the same node, the last save replaces the earlier one. Each save writes that node’s whole configuration.
• Split the work by node to avoid this.
• The builder does not show who else is in the workflow with you, and it does not update live as they work. Reload the page to pick up their latest changes before you publish.
• The workflow’s details panel shows Modified: who changed the workflow last, and when.

​

Version history

Select the version control in the top Context Bar. The list shows every published version, newest first, with who published it and when. Current Version at the top is the draft you are editing.

• Select a version to view it on the canvas. Past versions are read-only; select Draft in the same control to return to editing.
• Select Restore to draft to bring a version back for editing. Use this to undo an unwanted publish, or to recover a change captured in an earlier published version.
• Version history holds published versions only. If a draft edit was overwritten before anyone published, no version captured it and you cannot restore it.
• Restoring replaces the whole draft with that version, and discards any unpublished changes in the draft, including your teammates’. Check with them first.
• Restoring does not publish anything and does not change the Enabled switch. Review the restored draft before you publish it.

​

Review past runs

Select Runs in the top Context Bar to see every past run: the version that ran, the record it processed, the trigger, and whether it succeeded. See Run logs for a full walkthrough. Select Canvas in the same bar to return to the workflow graph.

​

Node references

See the Node reference for every node, how it works, when to use it, and which CRM provider versions it supports.

• Actions: Send to Webhook, Redirect, Date Transformer, Create Variable
• CRM: create, match, and update records and activities, create associations, and convert a Salesforce lead
• Sequencing: add people to Apollo, Outreach, Salesloft, Amplemarket, Gong, HubSpot, and Smartlead
• Notifications: Slack messages and channels, internal email
• Enrichment: enrich people and companies, geolocation
• Routing and scheduling: round-robin assignment, show a scheduler
• Logic and timing: branch on conditions, split traffic for an experiment, and add a delay
• AI: prompt a model and use its response in later nodes