ActionMode, connected

Your next customer.
Already in your tools.

Bring the enquiry, the CRM contact and the conversation together. Give your AI go-to-market team the context to prepare the next move.

Preview — built, not open yet. API and webhook access is still disabled. Explore the workflows below and tell us what you want to connect.

Explore 10 use cases ↓Tell us your workflow
From trigger to next move

How a connected workflow works

  1. 01

    Something happens

    A new prospect, a form submission or a reply reaches your workflow.

  2. 02

    The team gets to work

    Send context into ActionMode. Request an opener or record the conversation.

  3. 03

    Your tools hear back

    A signed webhook tells your workflow what happened. Drafts wait for your approval.

Make it work for you

Start with a real job.

These recipes show what the bridge can do once enabled, using HTTP steps in your automation platform. Native CRM sign-in and two-way sync are still to come.

10 use cases shown
Preview workflow

A new CRM lead. A proper first move.

When: A contact enters your prospecting list.

  1. Your workflow sends the contact to ActionMode.
  2. Use the returned lead ID to request an opener with a clear brief.
  3. The draft lands in Comms for your approval.

Your CRM becomes the starting point for a conversation you can actually send.

HubSpot, Pipedrive or Salesforce → n8n / Make → ActionMode

How to wire it up +

Trigger on an opted-in CRM list or stage. Map contact ID, name, company and email. Wait for the intake receipt to succeed, then use result.lead_id in a second event. Keep the CRM as the owner of its lifecycle fields.

lead.upsert → outreach.requested → outreach.draft_ready

Preview workflow

Turn an enquiry into a prepared follow-up.

When: Someone submits your website or event form.

  1. Create or match the lead using a stable submission or contact ID.
  2. Attach their answers as a note.
  3. Request a draft that responds to their actual enquiry.

Less copying between tabs; the enquiry arrives with context attached.

Typeform, Tally or your website → automation → ActionMode

How to wire it up +

Send the lead first, poll its status_url, then attach answers using result.lead_id. Use a separate persistent request UUID for each note and draft. Put the relevant enquiry context in the draft brief.

lead.upsert → note.add → outreach.requested

Preview workflow

They replied. Stop chasing.

When: Your connected inbox workflow detects a real reply.

  1. Match it to an ActionMode outreach ID.
  2. Send the reply body and the sender address.
  3. ActionMode records it and stops the lead’s active follow-up runs.

Replies reach the same conversation record and follow-up stopping logic as the app.

Inbox / CRM reply trigger → ActionMode → Slack / CRM

How to wire it up +

Requires sent ActionMode outreach and a sender matching the lead. Store the ActionMode outreach ID in your workflow. Ignore automatic replies in the source trigger. Use the original email Message-ID when available.

reply.received → outgoing reply.received

Preview workflow

Tell the right person when a draft is ready.

When: The Writer finishes an outreach draft.

  1. A signed webhook reaches your automation.
  2. Fetch the draft with the connection’s read permission.
  3. Your workflow posts a notification with a link to Comms.

Approvals become visible where your team already works.

ActionMode → n8n / Make / Zapier → Slack or Teams

How to wire it up +

Subscribe to outreach.draft_ready. Verify the signature and deduplicate the event ID. Fetch the draft using a data.read key, then format a team notification. Review and approve in ActionMode.

outreach.draft_ready → GET /outreach/{id}

Preview workflow

Keep the call context with the lead.

When: A meeting summary is approved in your notes tool.

  1. Find the ActionMode lead or use a stored ID.
  2. Attach the agreed summary, objections and next steps.
  3. Draft the follow-up with the relevant context in its brief.

The next message starts from the conversation you just had.

Meeting notes or CRM → automation → ActionMode

How to wire it up +

Map to an existing lead ID. Send only the summary you want stored, then request a draft with an explicit brief. Automatic meeting booking and opportunity-stage changes are future adapters.

note.add → outreach.requested

Preview workflow

Give every client a separate pipeline feed.

When: An agency imports a client’s campaign leads.

  1. Create a connection for that client’s project.
  2. Route their CRM or spreadsheet rows through that key.
  3. Send draft-ready and reply notifications to their workflow.

Repeat the same recipe for each client, with separate project credentials and activity.

Client CRM / Google Sheets → workflow → client project

How to wire it up +

Use one project and connection per client. Keep keys in the automation platform’s credential store. Scope each workflow to the permissions it needs; never share a connection between clients.

Project-scoped keys + lead.upsert + subscribed events

Preview workflow

Make the spreadsheet a useful intake tray.

When: A row is marked ready in your prospecting sheet.

  1. Send validated rows with stable external IDs.
  2. Save each returned ActionMode lead ID back to the sheet.
  3. Use receipt status to flag failed imports for attention.

A repeatable import with an answer for every row.

Google Sheets / Airtable → automation → ActionMode

How to wire it up +

Use a persistent row or contact identifier, not a row number that changes when sorted. Existing nonempty ActionMode fields are preserved. This is intake, not continuous two-way sync.

lead.upsert → GET /events/{id}

Preview workflow

Catch a failed run before work goes quiet.

When: An ActionMode run changes to failed.

  1. Receive a signed run.failed event.
  2. Fetch the run’s current status.
  3. Open an internal task or notify the owner.

Your operations workflow can surface work that needs attention.

ActionMode → workflow → ClickUp, Linear, Slack or Teams

How to wire it up +

Subscribe to run.failed with data.read. Deduplicate webhook IDs and link to ActionMode. A notification does not retry paid work automatically.

run.failed → GET /runs/{id}

Next on the roadmap

A payment becomes an onboarding handover.

When: Stripe or your invoicing tool confirms a payment.

  1. Match the payment to the right customer and opportunity.
  2. Record the confirmed commercial outcome.
  3. Create the agreed onboarding work.

A proposed adapter connecting confirmed revenue to delivery.

Stripe / invoicing → ActionMode → project tools

What this needs +

Not supported by this API release. It needs payment identity, currency, refunds and corrections mapped into the existing commercial outcome commands.

Planned: commercial outcome adapter

Next on the roadmap

Let a specialist agent bring its tools.

When: An agent needs research or a specialist system during a task.

  1. Discover an approved external MCP server.
  2. Use only the tools and data allowed for this project.
  3. Return evidence and a recorded result to the workflow.

A proposed way to expand the team’s capabilities without building every adapter ourselves.

ActionMode → approved external MCP tools / specialist agents

What this needs +

ActionMode already exposes its own MCP tools to compatible clients. Calling other MCP servers from ActionMode is a separate future capability. Grok or another model can also use the HTTP bridge when its host supports tool calls.

Planned: outbound MCP client + per-tool permissions

Before you connect

The possibilities. And where we are today.

Can I connect my CRM today?

The API and webhook bridge is built and deployed, but access is still disabled. You can explore the recipes and setup guide today. Connection setup opens after activation; we have not announced a date. Native sign-in for HubSpot, Pipedrive or Salesforce and automatic two-way sync are planned. These examples describe workflows you configure through an automation platform.

What does a webhook actually do for me?

It tells another tool that something happened. When ActionMode finishes a draft, a webhook can tell your automation to post a Slack notification or add a draft link to your CRM. You choose that next step. The message still waits for review in Comms.

How is this different from MCP?

ActionMode’s existing MCP connection lets a compatible AI assistant work with your ActionMode team. The new API lets your software request work, and webhooks report what happened. Giving ActionMode agents access to your own external MCP tools is a future phase.

Will a connected workflow send messages or add AI costs?

A draft request prepares work for your approval; it does not grant permission to send. Importing leads, storing notes and delivering webhooks do not call an AI model. Drafts use the existing Writer and project budget. Your automation provider and hosting can have their own charges; no separate integration price has been announced.

API: ask it to do work

Send an event with a project key and a unique request ID. Check the saved receipt to see the result.

Webhooks: hear what happened

Receive lead, reply, draft and run events. Use them to start the next step in your workflow.

MCP: talk to your team

Connect a compatible AI client to ActionMode’s existing tools. External MCP tools inside ActionMode are a later step.

Read the API guideExplore MCP