Workflows

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

​

Triggers and steps

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.
• Steps are the actions that run after the trigger fires, laid out on a canvas. A step can route a lead, write to your CRM, add someone to a sequence, send a Slack message, show a scheduler, branch on a condition, and more.

​

The workflows list

Opening Workflows shows every workflow in your workspace.

• 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), or Active (published and turned on).

​

Create a workflow

​

Add a step

Steps sit on the builder canvas as connected nodes; drag from one step to another to connect them, or branch a step into more than one path. Select Add Node to open the step picker, then choose a step. Steps are grouped by what they do (routing, CRM, notifications, enrichment, and so on). Each step you add starts unconfigured; 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 step, so a CRM field, a Slack message, or a webhook body can carry the lead’s real data. Type {{ in a field to open the data picker (or select the button in the field’s toolbar). It groups values under CRM, Enrichment, AI, Slack, Default Objects (the person and company details every trigger provides), and Workflow (scheduling and meeting details, the trigger data, and any values earlier steps produced). In a Slack message field, type @ instead (or select the @ toolbar button) to open a separate picker for mentioning people: mapped Slack recipients, user groups, and upstream references, such as an account owner, that resolve 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 an Enabled switch, in the builder toolbar and in the workflow’s details panel. 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 the workflow has been published at least once.

​

Test a workflow

Select Test to open the Test Workflow panel, choose the trigger to fire, edit its sample payload, then select Run Test. For a workflow that starts from a CRM record trigger, the payload opens as a record already listing its 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 isn’t available yet for workflows that start from a Meeting Status 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. Once published, the button reads Publish changes when you have unpublished edits, and Up to date when the live version matches your draft.
• 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. While you edit, a banner shows whether you are editing the draft or viewing a published version, with 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, and publish once you are both finished.
• Editing different steps is safe: both sets of changes land. If you both edit the same step, each save writes that step’s whole configuration, so the last save replaces the earlier one. Split the work by step 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

Open the workflow’s details panel and select Version history to see 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, and a banner offers Back to draft.
• 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, so a draft edit that was overwritten before anyone published it was never captured and cannot be restored.
• Restoring replaces the whole draft with that version, so any unpublished changes in the draft are discarded, including your teammates’. Check with them first.
• Restoring does not publish anything and does not change the Enabled switch. Review the restored draft, then publish it when you are ready.

​

Review past runs

Open a workflow’s Logs tab 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.

​

Step references

• 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 steps