Swift Missive
Email MarketingSwift Missive is an email marketing platform for creators and small businesses. Agents manage contacts and segments, maintain templates and sender personas, send email blasts, run campaigns and workflows, record events, and pull reporting.
What This Integration Enables
Swift Missive does not hand you an API key. You sign in, and what comes back is a key plus a map of roughly a dozen AWS gateway hosts, one per subsystem, specific to your account. Contacts go to one host, templates to another, the scheduler to a third, and another account's hosts will not accept your key. That is a platform giving you a slice of its infrastructure rather than a polished front door, and it suits creators and small teams who would rather own the plumbing than be abstracted away from it. FlowRunner's connectors layer signs in once, caches the map for the life of the flow, and routes every call to the right host, so none of that reaches the workflow.
The commitment worth understanding before you build on it is that Swift Missive treats a send as final. You generate an email blast's UUID yourself, and the moment it exists it is enabled for automatic sending. There is no update route. Workflows answer a bodyless 503 to mean the job was queued and is still running. Campaigns can be deleted for reporting while the blasts inside them keep going. Agents can do everything up to the edge of that line at machine speed: build segments from a twenty-five attribute filter vocabulary, maintain templates and sender personas, record events, poll for contact and event updates, and read the eight reporting routes. Crossing the line is a decision, and human-in-the-loop is how it stays one.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
A segment that is inspected before it exists
The team wants everyone who opened the last product announcement but did not click. The agent expresses that in Swift Missive's filter vocabulary and calls Preview Filtered Contacts first, which shows exactly who the rules resolve to without creating anything. If the count looks wrong, the rules change and the preview runs again. Only when the shape is right does Create Segment From Filters commit it. Add Contacts To Segment and Remove Contact From Segment then handle the exceptions a rule cannot express, such as the three accounts under an active support escalation who should sit this one out.
-
Product events from billing, turned into lifecycle mail
Subscription changes in Stripe reach the agent as they happen. It calls Create Events with the plan change, the amount, and the account owner, and the connector checks the nested user object's email against the event's before sending, because Swift Missive requires them to match. Get Event Updates then runs on a schedule as the polling substitute for a webhook, since this API publishes no webhook management surface at all. New events land in Google Sheets for the revenue review, and the workflows keyed to those event names do the mailing.
-
A workflow deployed the way the vendor recommends
An onboarding sequence needs changing. The agent calls Validate Workflow first, which is the vendor's own recommended order, then Create Workflow. A 503 with no body comes back, which here means queued and still running rather than broken, so the agent records it as queued and polls Get Job Log until the outcome is known. When the old sequence is confirmed superseded, Archive Workflow retires it, and the agent posts the job log result to Slack so the person who asked for the change can see it actually landed rather than assuming it did.
Human-in-Loop Highlight
Create Email Blast is the least forgiving operation on this platform, and its unforgiving parts stack. You supply the blast's UUID yourself, so there is no server-generated identifier to compare against. The blast is enabled for automatic sending the instant it exists. There is no update route, so the only remedy for a wrong subject line, a wrong template, or a wrong send time is Disable Email Blast and a complete replacement under a new UUID, which is a repair rather than an edit. And the vendor asks you not to mail contacts whose addresses have not been validated yet, a number the agent can read but not act on for you.
So the agent gets everything ready and then waits. It posts: "Blast ready for the Spring release. Segment resolves to 14,206 contacts, of which 611 are not yet validated. Template renders as attached, test sent to the verified persona at [email protected]. Send At is Tuesday 09:00 in each contact's own timezone. Create the blast, exclude the unvalidated contacts first, or hold?" The marketer answers. Everything before that question is work no person should have to do by hand. The question itself is the only part of this workflow where a mistake costs a rebuild rather than a retry.
Agent Capabilities
53 actionsAccount
4- Get Account Endpoints Shows the per-account map of subsystem hosts returned at sign-in, without exposing the key. Used for diagnostics when a call reaches the wrong subsystem.
- Get Company Users Lists the people with access to the account. Used to resolve the right approver before a workflow pauses for one.
- Create Company User Adds a user to the account. The onboarding half of access management.
- Delete Company User Removes a user from the account. The offboarding half, and the one worth running the day someone leaves.
Domains
2- Register Domain Registers a sending domain against the account, using the company and project names sign-in returned rather than the ones typed at signup.
- Get DKIM Status Reads the DNS records a domain needs and whether they are in place. The check that explains a domain which will not send.
Contacts
8- Get Contacts Reads contacts with paging. The lookup behind matching and audience work.
- Get Contact Count Returns how many contacts the account holds. Used to size before acting.
- Create Contacts Writes contacts in a batch. The response carries results and errors together, so a partly rejected batch is only visible if the errors are read.
- Delete Contacts Removes contacts from the account. Used in cleanup workflows with review.
- Get Email Validation Counts Reports how many addresses have been validated. The vendor asks that unvalidated contacts are not mailed, which makes this the read that runs before a send is approved.
- Get Contact Updates Polls for contact changes since a marker. One of the two routes that stand in for the webhooks this API does not publish.
- Get Contact Upload URL Returns a destination for a CSV of more than ten thousand contacts. It uploads nothing itself, and the file name has to match.
- Get Bulk Upload Status Reports the outcome of a CSV upload by its storage key. The step that turns a queued import into a known result.
Segments
6- Get Segments Lists the account's segments.
- Create Segment Creates a segment directly.
- Create Segment From Filters Builds a segment from the platform's twenty-five attribute filter vocabulary, covering contact fields, dates, and open, send, and click counts.
- Preview Filtered Contacts Shows what a set of filters resolves to without creating anything. The rehearsal that makes a wrong segment cost nothing.
- Add Contacts To Segment Adds specific contacts to a segment. Used for the exceptions a rule cannot express.
- Remove Contact From Segment Removes one contact from a segment. Used to hold someone out of a send without changing the rules.
Templates
5- Get Templates Lists the account's templates.
- Create Template Creates a template. The plain-text body is deprecated on this platform, so the HTML body carries the message.
- Delete Template Removes a template. Blasts referencing it stop resolving, so cleanup checks first.
- Upload Template Image Uploads an image for use in email content. Images are publicly hosted, and SVG is refused because most mail clients will not render it.
- Get Template Image Upload URL Returns a destination for a larger image upload.
Sender Personas
2- Get Sender Personas Lists sender identities and their verification state. The read that confirms a persona is actually usable.
- Create Sender Persona Creates a sender identity and triggers a verification email to it. Success here does not mean the address can send yet.
Email Blasts
4- Get Email Blasts Lists blasts and their state.
- Create Email Blast Creates a blast under a UUID you supply, enabled for automatic sending immediately. There is no update route, which is why this operation waits for a person.
- Disable Email Blast Stops a blast. The only remedy for a blast that should not have been created, and the reason a replacement needs a fresh UUID.
- Send Test Email Sends a template to a verified persona's own inbox for checking. Not a route for campaign mail, and the whole HTML body has to be supplied.
Campaigns
5- Get Campaigns Lists campaigns.
- Create Campaign Creates a campaign as the reporting container the blasts and workflows sit inside.
- Delete Campaign Removes a campaign for reporting only. The blasts, workflows, and templates inside it keep sending.
- Get Campaign Metrics Reads a campaign's performance figures.
- Get Campaign Count Returns how many campaigns exist on the account.
Events
4- Get Events Reads recorded events. Both event inclusion switches are off by default, so an unset query returns nothing and looks like no activity.
- Get Event Count Returns how many events match a query.
- Create Events Records events against contacts. A nested user object's email must match the event's, which the connector checks before sending.
- Get Event Updates Polls for event changes since a marker. The second of the two routes that stand in for webhooks.
Workflows
5- Get Workflows Lists the account's workflows.
- Validate Workflow Checks a workflow definition before it is created. The first step in the vendor's recommended sequence.
- Create Workflow Creates a workflow. A bodyless 503 here means queued and still running rather than failed.
- Archive Workflow Retires a workflow. The connection closes after thirty seconds while the job carries on, so the outcome comes from the job log.
- Get Job Log Reads the outcome of a queued workflow job. The step that turns "accepted" into "finished."
Reporting
8- Get Quick Stats Reads headline figures for an account or a campaign. Accepts the literal string for account-wide totals.
- Get Sends Last 24 Hours Reads sending volume over the last day. The input to a daily volume check.
- Get Sends Last 31 Days Reads sending volume over the last month. The input to trend reporting.
- Get Most Clicked Links Ranks links by click volume. Used to decide what the next campaign leads with.
- Get Recently Clicked Links Lists the most recent link clicks. Used for near-real-time engagement routing.
- Get Most Opened Emails Ranks emails by open volume.
- Get Recently Opened Emails Lists the most recent opens. Used to trigger follow-up while attention is fresh.
- Get Opens By Source Breaks opens down by where they came from. Used to understand which channel actually delivered the audience.
Frequently Asked Questions
What can FlowRunner do with Swift Missive?
FlowRunner agents can run Get Account Endpoints, Get Company Users, and Create Company User in Swift Missive, plus 50 more actions.
Does connecting Swift Missive to FlowRunner require OAuth?
No. Swift Missive connects to FlowRunner with session-based authentication, no OAuth flow required.
Can Swift Missive trigger a FlowRunner workflow automatically?
Swift Missive doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Email Marketing integrations
Start building with Swift Missive
Free plan, no card required. Connect in minutes.