Workflows: build the follow-up once and let it run
on every account

Overview

Most post-sales follow-up is a pattern you already know by heart. Health drops, you email the owner, you wait a few days, and if nobody replies you nudge someone in Slack. The problem is that the pattern lives in your head, so it only runs when you remember it. Workflows let you write it down once and have Sonora run it on every account that matches.

Describe it, then tune it on the canvas

Start a workflow by describing it in plain language, picking a template, or building step by step. Kit proposes the steps as a diff you can review, and nothing changes until you accept it.

From there, the builder draws your workflow as a top-down graph:

• Action steps send an email, create a cue in Actions, or post to Slack, and can branch on the reply.
• Enrich steps run an enrichment on the record, then branch on the result.
• Condition steps branch on the account’s own data.
• Waits and reply paths read as a timeline, so “wait five days, then” is visible right on the step.

A connector “+” inserts a step in sequence, and a ghost “+” beside a step adds a parallel branch. Preview shows you exactly who the workflow would enroll before it does anything.

Four ways to start a run

A workflow can be triggered:

• Manually, for the accounts you pick.
• On a condition, like a health score dropping or a usage metric crossing a line. Sonora enrolls accounts when their data changes and sweeps hourly for accounts that already match.
• On a schedule, daily, weekly, monthly or quarterly.
• From the API, with one call that starts a workflow for up to 100 accounts.

Safe by default

A new workflow is a draft. It enrolls no one until you activate it, and activating shows you who it will enroll, biggest ARR first. Emails land as review drafts unless you turn on Send automatically, and nothing built by AI can switch that on for you. Pausing or dismissing a workflow stops its mail.

See every run

The Runs tab shows how a workflow is performing: emails sent, opened, responded to, and runs waiting on your review. Open any run and the trace draws it on the same canvas as the builder, with the steps it visited marked and the branches it didn’t take still visible. The trace shows the config that run actually used, so editing the workflow later never rewrites history.

Get started

Open Workflows in the sidebar and create your first one. To feed a workflow with your own signals, trigger it from an enrichment result.