SparkPost
EmailSend transactional and template-based email through SparkPost. Agents deliver transmissions with per-recipient substitution data, manage reusable templates, maintain the suppression list to honor opt-outs, and audit sending domains and transmission history.
What This Integration Enables
SparkPost is sending infrastructure, and infrastructure earns trust by what it refuses to do: deliver to people who opted out, send from unverified domains, fail silently. FlowRunner agents operate all three refusal points as workflow steps. They deliver transactional email with per-recipient substitution data, keep the suppression list current from every channel where an opt-out can arrive, verify sending domains before campaigns depend on them, and read transmission history so delivery is a recorded fact rather than an assumption. - Send order confirmations, password resets, and alerts from stored templates with per-recipient substitution - Honor opt-outs by writing suppression entries the hour the request arrives, scoped to transactional, marketing, or both - Verify DKIM and ownership status on sending domains before a workflow trusts them - Manage templates as reviewed, versioned assets rather than live-edited production content - Route delivery exceptions to a person instead of letting them evaporate - Tag sends by campaign so transmission history answers reporting questions later
Without FlowRunner
With FlowRunner
Use Case Scenarios
The order confirmation with a pre-flight check
A new order row arrives from [Google Sheets](/integrations/google-sheets). Before sending, the agent checks the recipient against Search Suppression List and the sender against List Sending Domains. Clean, so Send Transmission fires the stored template with the customer's name, items, and delivery window as substitution data, and Get Transmission logs the generated state against the order. The one address that bounces repeatedly gets flagged to support in [Slack](/integrations/slack) instead of silently never receiving another confirmation.
The opt-out that took effect the same hour
Unsubscribe requests arrive through a [Typeform](/integrations/typeform) preferences form. An agent processes each response hourly: Add to Suppression List writes the entry scoped to what the customer actually declined, marketing only, or everything, and the decision logs to the audit sheet with the form timestamp. The gap between "customer opted out" and "system stopped sending" drops from a weekly batch to the same hour, which is the gap regulators and spam filters both measure.
The template release that went through review
A lifecycle marketer revises the password-reset email. The workflow calls Create Template as a draft, renders the review copy to the team, and publishes only after approval. When a question comes up two months later, Get Template retrieves exactly what the published version says, and List Transmissions shows which sends used it. Production email gets the same release discipline as production code.
Human-in-Loop Highlight
Remove from Suppression List re-opens a door a person closed. Every entry on that list is a recipient who opted out, bounced hard, or complained, and deleting the entry re-enables delivery of every message type it covered. An agent that removes entries on a fuzzy match, say, cleaning up what looks like a stale test address that is actually a customer's real one, converts a compliance record into a future spam complaint, and complaints are the currency your sender reputation is priced in. SparkPost itself refuses to remove compliance-added entries; FlowRunner extends that caution to the rest of the list. Removal requests always carry evidence, who is asking, why, and the entry's original suppression type and date from Search Suppression List, and a person approves each one before the call runs. Additions flow automatically, because suppressing too eagerly costs a send. Removing wrongly costs the domain.
Agent Capabilities
10 actionsSending
3- Send Transmission Sends an email transmission to one or more recipients, with raw HTML and text content or a stored template by ID. Supports CC, BCC, reply-to, campaign tagging, open and click tracking, sandbox mode, and scheduled delivery.
- List Transmissions Retrieves transmissions filtered by campaign or template ID, with each transmission's ID, state, and campaign. The audit view of what actually went out.
- Get Transmission Retrieves one transmission's detail: recipient counts, generation timestamps, state, and content reference. The read that turns "we sent it" into a recorded fact.
Templates
3- List Templates Retrieves all stored templates with ID, name, description, and publish status. The inventory step for template governance.
- Get Template Retrieves a template's full content, from, subject, HTML, and text, defaulting to the published version. The answer to "what does this email actually say right now."
- Create Template Creates a reusable stored template with ID, name, sender, subject, and HTML, publishable immediately or saved as a draft. Draft-first is how this page's review flow works.
Suppression
3- Search Suppression List Searches suppressed recipients by suppression type and last-updated date range, paginated. The pre-send check and the evidence source for gated removals.
- Add to Suppression List Adds or updates a recipient's suppression entry, scoped to transactional messages, non-transactional messages, or both. The operation that makes opt-outs take effect.
- Remove from Suppression List Removes a recipient's suppression entry entirely, re-enabling all message types. Compliance-added entries cannot be removed, and every other removal passes this page's human gate.
Domains
1- List Sending Domains Retrieves all configured sending domains with DKIM and ownership verification status. The pre-flight check that keeps workflows from sending on a broken domain.
Frequently Asked Questions
What can FlowRunner do with SparkPost?
FlowRunner agents can run Send Transmission, List Transmissions, and Get Transmission in SparkPost, plus 7 more actions.
Does connecting SparkPost to FlowRunner require OAuth?
No. SparkPost connects to FlowRunner with an API key, no OAuth flow required.
Can SparkPost trigger a FlowRunner workflow automatically?
SparkPost doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SparkPost
$100 in credits. No card required. Connect in minutes.