Hand your MOps backlog to agents.
Agents start from a Slack thread, a Linear ticket, or a schedule and build the work in Conversion. Nothing goes live until you review it.
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+
Veriforce
- Valuation
- $1.2B+
- Employees
- 1,800+
- Replaced
- Pardot & Marketing Cloud
ClickUp
- Valuation
- $4B
- Employees
- 1,200+
ACV Auctions
- Ticker
- NYSE: ACVA
- Employees
- 3,200+
- ARR
- $1B
Productboard
- Valuation
- $1.7B
- Employees
- 500+
- Replaced
- Marketo
AMCS
- Valuation
- €2B
- Employees
- 1,300+
- Replaced
- Pardot
How an agent works.
Pick a template, choose what starts it, and write down how your team works. Every run after that is on record.
Start from a template
Use Weekly Recap or Top Accounts to Target, start from scratch, or describe the agent in chat. Agents made in chat start switched off.
Triggers
Configure events and schedules that trigger this agent.
Choose what starts it
Agents start from a Slack mention, a Linear issue or comment, a daily or weekly schedule, or a webhook from any system that can call one.
Instructions
Provide instructions for this agent to reference when working on your behalf.
Documents
Upload documents for this agent to reference in every session.
Upload a file or paste text
Teach it your playbook
Write instructions once and attach the documents it should follow. Every session also loads your workspace's description and instructions.
Review every run
Each run is a session with its trigger, every tool it used, and what it built. A Slack thread or Linear issue stays one session.
What teams hand to agents.
Start from the Weekly Recap or Top Accounts template, or write instructions for any job your team repeats every week.
Scheduled run
Posted the Sep 14 to Sep 20 recap in #marketing-ops, with the details threaded underneath.
| Last week | Change | |
|---|---|---|
| Click rate | 4.2% | +1.1pp |
| Form submissions | 312 | +18 |
| Complaint rate | 0.52% | +0.14pp |
| Contact sync errors | 38 | New |
Decide what runs without asking.
Every tool an agent can use has its own setting: Automatic, Requires approval, or Disabled. Reads and new drafts run on their own by default, while deletes, imports, and Salesforce links wait for a person.
Rename the Q4 nurture workflow to Q4 nurture v2.
Rename workflow to "Q4 nurture v2"?
Renamed the workflow to Q4 nurture v2.
Work from Claude, ChatGPT, or Cursor.
The same tools run through the Conversion MCP server, and agents can use the other MCP servers your admins connect.
MCP server details
Sign in once with OAuth
Add mcp.conversion.ai/mcp to any MCP client and pick a workspace. Each connection works in that one workspace, as you, within your role.
MCP servers
Connect MCP servers and configure which external tools this agent can use.
Give agents your other tools
Admins add MCP servers for the workspace, and each agent connects on its own. External tools ask for approval until you change them.
Agents run on the rest of Conversion.
They work in the same workspace as your team: the same records, the same assets, and the same review before anything goes live.
Plays work each contact
Agents do work for your team. A Play works on your contacts and accounts, deciding what each person gets and when.
Agents build your workflows
Describe a workflow in Slack or a Linear ticket. It's built with every node configured and stays inactive until you turn it on.
Ready for security review
SAML SSO, SCIM provisioning, and zero data retention on every chat and agent model call. Customer data never trains a model.
Conversion is going to allow me to focus on the thing that I love about marketing, but not at the expense of being able to run what feels like a team of ten ops people, but really just from one person using one tool.
Korey Beaver
Marketing Operations Manager, People Data Labs
129
Tools in a standard workspace, each set to run on its own, wait for approval, or stay off
5
Ways to start an agent: Slack, Linear, a schedule, a webhook, or a prompt
0
Emails sent, forms published, or workflows turned on without someone on your team
Common questions
What marketing ops leaders ask before they let an agent into their workspace.
Whatever you allow. Every tool has a setting per agent: Automatic, Requires approval, or Disabled. By default, reads and new drafts run automatically, deletes, contact imports, and Salesforce links wait for approval, and edits to existing emails, forms, audiences, and campaigns come back as a before-and-after diff for review.
No. Agents build emails, forms, and workflows as drafts, and nothing is sent, published, or activated until someone on your team does it. An agent can post a link to each draft in Slack or on the Linear ticket.
The Slack agent responds to mentions, channel messages, reactions, and direct messages. Other agents start from a Linear issue or comment, a daily or weekly schedule, or a webhook from any system that can send an HTTP request, and you can start one with a prompt from its page. A Slack thread or Linear issue stays one session, so follow-ups land in the same conversation.
The session pauses and waits, with no timeout, and the Slack channel or person you pick gets a link to it. Someone allows or denies the action in Conversion, and the run picks up from there. Always allow switches that tool to Automatic for the agent.
Everything in your Conversion workspace: contacts, companies, opportunities, events, and assets, including the Salesforce and warehouse data synced into it. Every session also gets your business description and workspace instructions, plus the agent's own instructions and documents to reference.
Chat is for asking a question or building something once. Agents run the same tools on their own, started by Slack, Linear, a schedule, or a webhook, with instructions you write once. Plays work on your contacts and accounts, deciding what each person receives and when.
Yes. Add Conversion from ChatGPT's app directory, or connect Claude, Cursor, or any MCP client to mcp.conversion.ai/mcp and sign in with OAuth. Each connection works in one workspace as you, within your role. Confirmations happen in your client, so set it to ask before it makes changes.
No. Conversion doesn't use customer data to train or fine-tune AI models, ours or anyone else's, and chat and agent model calls run with zero data retention.
See an agent work your backlog.
Bring a request your team handles every week, and we'll build an agent for it on your data during the demo.