Mixmax
Sales OutreachDrive Mixmax sales engagement from AI agents: enroll leads into sequences, keep contacts in sync with your system of record, send tracked emails on behalf of the authenticated user, and look up sequences for routing.
What This Integration Enables
Mixmax lives inside the rep's inbox, which is exactly why feeding it by hand is the bottleneck: the person doing the selling is also the person doing the data entry. This connector splits those jobs. FlowRunner agents keep the Mixmax address book in sync with the system of record, resolve the right sequence by ID rather than guesswork, enroll recipients with the merge variables their templates expect, and send tracked one-off emails when a sequence is the wrong tool. Everything this connector does happens on behalf of the authenticated Mixmax user. That is its power and its risk in the same sentence: emails leave from a real person's account, tracked like anything they sent themselves. FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) discipline exists for precisely this shape of operation. - Enroll leads from CRMs, sheets, and forms into sequences with personalization data attached - Sync contacts from an external system of record into the Mixmax address book - Send tracked, on-behalf-of-user emails as workflow steps, with review before send - Look up the authenticated user and sequence library to route enrollments correctly
Without FlowRunner
With FlowRunner
Use Case Scenarios
The sheet of prospects that enrolls itself
An SDR team keeps target accounts in [Google Sheets](/integrations/google-sheets). On a schedule, the agent reads new rows, calls Create Contact for each, and matches the row's segment column to a sequence via List Sequences. Get Sequence confirms which merge variables the templates use, and the agent maps sheet columns to those exact keys. The staged batch goes to the sequence owner with every variable rendered as it will send. Approved rows enroll through Add Recipient to Sequence; rows with missing personalization data go back to the sheet flagged, not enrolled half-blank.
CRM lead to nurture sequence without the swivel chair
A new contact lands in [HubSpot](/integrations/hubspot) from a demo request. The agent checks the contact's lifecycle stage, picks the nurture sequence that matches, and stages the enrollment with company and first name as merge variables. For hot leads, it drafts an immediate personal follow-up instead and holds it for the rep: Send Message will deliver it from the rep's own account, so the rep reads the draft in [Slack](/integrations/slack) and approves or edits before it goes. Fast lane and slow lane, both fed automatically, both leaving in a human's name only with that human's consent.
Mirroring engagement stacks during a migration
A team running both Mixmax and Salesloft needs them consistent while territories transition. The agent pages through List Contacts, mirrors each person into [Salesloft](/integrations/salesloft), and logs the mapping to a sheet. When the reverse direction matters, CRM-sourced contacts flow into Mixmax through Create Contact on the same schedule. Neither address book rots while the org decides, and no rep spends an afternoon exporting CSVs.
Human-in-Loop Highlight
Send Message delivers from the authenticated user's actual email account, indistinguishable from something they typed, and once delivered it cannot be recalled from a prospect's inbox. The same stakes apply to Add Recipient to Sequence, which commits a person to a schedule of emails in the rep's name. FlowRunner's answer is a draft-first pattern: the agent assembles the recipient list, resolves the sequence, and renders every merge variable exactly as it will appear, then routes the result to the account owner in Slack or email. The rep whose signature is on the line approves, edits, or strikes. Agents move the data at machine speed; nothing leaves an inbox that its owner has not seen.
Agent Capabilities
7 actionsUsers
1- Get Me Returns the profile of the authenticated Mixmax user behind the API token: name, email, and account identifiers. The first call in most workflows, because it establishes whose name every subsequent send and enrollment carries.
Sequences
3- List Sequences Returns a paginated list of the user's sequences with names, identifiers, and status. The routing table for enrollment workflows; its IDs feed Get Sequence and Add Recipient to Sequence.
- Get Sequence Retrieves a single sequence's full details by ID, including its name, stages, and configuration. Used to confirm what merge variables the templates expect before anyone is enrolled.
- Add Recipient to Sequence Adds a recipient to a sequence so they begin receiving its scheduled emails. Takes the recipient's email, optional first and last name, and custom merge variables as a key/value object merged into the recipient's personalization data. The enrollment step this page's human gate reviews.
Contacts
2- List Contacts Returns a paginated list of contacts from the user's Mixmax address book with names and email addresses. Used for audits, mirroring, and sync comparisons.
- Create Contact Creates a new contact in the address book with name and email. The sync write that keeps Mixmax consistent with an external system of record.
Messages
1- Send Message Sends an email through Mixmax on behalf of the authenticated user: recipients, subject, HTML body. The message leaves from the connected user's own email account and is tracked in Mixmax like any message they sent themselves.
Frequently Asked Questions
What can FlowRunner do with Mixmax?
FlowRunner agents can run Get Me, List Sequences, and Get Sequence in Mixmax, plus 4 more actions.
Does connecting Mixmax to FlowRunner require OAuth?
No. Mixmax connects to FlowRunner with an API key, no OAuth flow required.
Can Mixmax trigger a FlowRunner workflow automatically?
Mixmax doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Mixmax
$100 in credits. No card required. Connect in minutes.