Workflows for every handoff, follow-up, and alert.
Start from a form fill, a page visit, a product event, or a Salesforce change, then branch on any field and see every step each contact takes.
Used by MOps teams replacing Marketo, Pardot, and HubSpot.
ClickHouse
- Valuation
- $15B
- Employees
- 500+
- Replaced
- Marketo
Plaid
- Valuation
- $8B
- Employees
- 1,500+
- Replaced
- Marketo
Webflow
- Valuation
- $4B
- Employees
- 1,500+
- Replaced
- Iterable
Profound
- Valuation
- $1.8B
- Employees
- 300+
Productboard
- Valuation
- $1.7B
- Employees
- 500+
- Replaced
- Marketo
BuildOps
- Valuation
- $1B
- Employees
- 600+
- Replaced
- HubSpot
ACV Auctions
- Ticker
- NYSE: ACVA
- Employees
- 3,200+
- ARR
- $1B
Veriforce
- Valuation
- $1.2B+
- Employees
- 1,800+
- Replaced
- Pardot & Marketing Cloud
AMCS
- Valuation
- €2B
- Employees
- 1,300+
- Replaced
- Pardot
How a workflow runs.
Pick the signal that starts it, branch on whatever you know about the contact, and act on every channel. Each run is recorded step by step.
Criteria
Activity
Contacts
Salesforce
Start from any signal
Trigger on a form, a page visit, an email, a field change, a Salesforce opportunity, a schedule, or your own events through the API.
Branch on any data
Split on contact, company, and opportunity fields, custom objects, and engagement, or describe the filter in plain English and let Conversion write it.
Act on every channel
Send email, post to Slack, create Salesforce tasks, update audiences and campaigns, assign owners, or call any API from a step.
Completed
Errored actions
In progress
Avg. duration
Every run on record
Open any contact's run to replay their path on the canvas, with when they entered and left each step and what every step returned.
What teams run on workflows.
The programs that used to need a developer, a spreadsheet, and a Friday afternoon, each built on the canvas in one sitting.
Put AI in any step.
Write a prompt and pick the field it fills. Conversion runs it for each contact the moment they reach the step, so a workflow can classify personas, read call notes, or draft an opening line on its own.
Workflows plug into the rest of Conversion.
Plays, agents, and your Salesforce sync run on the same records your workflows read and write.
Plays decide for one person at a time
Workflows send everyone down the same path. A Play works on top of them and picks the moment, or skips the email, for each contact.
Agents build workflows from a brief
Describe the workflow in chat or a Slack thread. Conversion drafts it inactive, with every node configured, for you to review and turn on.
Salesforce stays in step
Workflow steps create Salesforce tasks, add campaign members, and assign lead queues, and each change reaches Salesforce in about ten seconds.
Every node in this flow earns its place against the clock. If a step can't keep up with our speed to lead, it doesn't make the cut. Conversion kept up.
Jasen Henderson
CX Operations Lead, MyOutDesk
27
Triggers across CRM, web, email, campaigns, and your own events
~10s
For a change made in a workflow to reach Salesforce
Every
Run recorded step by step, with the path each contact took
Common questions
What marketing ops teams ask before they move their automation over.
A contact meeting criteria you define, a form submission, a page visit, a custom event from your product or the API, email activity (sent, delivered, opened, clicked, bounced), subscription changes, a new contact, a field change, audience and campaign membership changes, Salesforce opportunity and lead conversion events, a schedule, or another workflow.
Anything in Conversion's data model: contact, company, and opportunity fields, custom objects and their relationships, audience and campaign membership, email and form engagement, page visits, and custom events. Warehouse data joins the same model through scheduled syncs, so every condition can use it.
Form fills, page visits, email activity, and API events start workflows as they arrive. Salesforce changes sync in every few minutes, and warehouse data arrives on the schedule you set for each sync. Changes a workflow makes reach Salesforce in about ten seconds.
It runs a prompt for each contact as they reach the step and writes the answer to a contact or company field. You can limit the answer to a set of output values, turn on web search, and choose whether it overwrites existing values. Preview it on real contacts before you turn the workflow on.
Yes. The Runs tab lists every contact who entered the workflow. Open a run to see their path highlighted on the canvas, when they entered and left each step, and the output or error from every step.
Yes. Daily, weekly, and monthly communication limits, subscription status, and topic preferences apply to every email a workflow sends. Emails set as operational, like event logistics, go out regardless.
Yes. Describe what you want in a chat or to an agent and it builds the workflow with its trigger, branches, and steps configured. New workflows are created inactive, so nothing runs until you review it and turn it on.
See your workflows run on Conversion.
Bring a workflow you run today, and we'll rebuild it on your own data during the demo.