SMTP2GO
EmailSend transactional email through SMTP2GO from AI agents, with CC, BCC, reply-to, and custom headers. Agents audit delivery activity, pull deliverability stats, and manage the suppression list to protect sender reputation.
What This Integration Enables
SMTP2GO is the email channel most companies treat as plumbing, and that is exactly the mistake this connector fixes. Transactional email is where receipts, password resets, and order confirmations either arrive or quietly do not, and sender reputation is a slow-to-earn, fast-to-lose asset. FlowRunner agents send through the relay, verify delivery in the activity log, watch aggregate deliverability stats, and manage the suppression list as an audited process instead of a forgotten spreadsheet. - Send receipts, notifications, and resets from any flow, with CC, BCC, reply-to, and custom headers - Confirm delivery of critical messages by searching the activity log instead of assuming - Track sent, delivered, bounced, rejected, opened, and clicked counts over any date range - Diagnose list-hygiene problems with bounce breakdowns by type and cause - Keep the suppression list accurate with agent-proposed, human-approved changes The orchestration angle matters here because email is rarely a workflow's whole job; it is the last step of many workflows at once. Order flows, billing flows, and onboarding flows all end in a send, and when they share one SMTP2GO account they share one sender reputation. FlowRunner coordinates that shared resource: every flow sends through the same governed connector, every critical send gets its delivery verified, and the suppression list is maintained as one process instead of five teams' partial spreadsheets. When something threatens the reputation all those workflows depend on, the [human-in-the-loop](/concepts/human-in-the-loop) gate puts a person in front of the decision.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The order confirmation that proves itself
A new order fires from [Shopify](/integrations/shopify). The agent assembles line items and tracking details, calls Send Email with both HTML and plain-text bodies, and records the returned email ID. Thirty minutes later a second step calls Search Activity scoped to that recipient and window. Delivered means done. A bounce or rejection posts to [Slack](/integrations/slack) with the failure reason so support reaches out through another channel before the customer wonders where the receipt went.
Deliverability reporting nobody has to remember
Every Monday an agent calls Get Email Summary Stats for the prior week and appends the numbers to [Google Sheets](/integrations/google-sheets): sent, delivered, soft and hard bounces, spam complaints, opens, clicks, unsubscribes. When hard bounces or complaints cross the team's threshold, Get Bounce Stats pulls the breakdown by cause and the agent posts a digest to the deliverability owner naming the likely source, a stale list segment or a misconfigured sender. The team sees reputation drift as a trendline, not a crisis.
A suppression list that stays clean in both directions
When a recipient unsubscribes through the marketing platform or a complaint shows up in the activity log, the agent drafts a suppression request with the evidence attached. Once approved, Add Suppressions blocks the address. The reverse flow is gated too: when a customer re-subscribes or writes in that they stopped getting receipts, the agent calls View Suppressions to confirm the address is actually on the list, presents the original suppression reason to a person, and only calls Remove Suppressions after sign-off. Nobody silently re-enables an address that complained.
Human-in-Loop Highlight
Remove Suppressions re-opens the door to an inbox that was closed for a reason, and getting that wrong is how spam complaints happen twice. An address usually lands on the suppression list because it hard-bounced, unsubscribed, or reported the sender, so the agent never clears one on its own judgment. It presents the case: "[email protected] was suppressed on June 3 after a spam complaint. The contact emailed support yesterday asking why invoices stopped arriving. Restore delivery?" The deliverability owner weighs a genuine re-subscribe against a spoofed request, answers, and only then does the agent remove the entry. Send Email gets the same discipline when the audience is a list rather than a single recipient: a person confirms the segment before the relay does something no one can unsend.
Agent Capabilities
7 actionsSending
1- Send Email Sends a transactional email through the SMTP2GO relay from a verified sender, with plain-text and HTML bodies, CC, BCC, reply-to, and custom headers. Returns succeeded and failed counts plus the assigned email ID, which downstream steps use to verify delivery.
Delivery Auditing
3- Search Activity Searches the activity log for messages sent within a date range, filtering by recipient, subject, or sender. The step that turns "we sent it" into "it was delivered," and the evidence source when it was not.
- Get Email Summary Stats Returns aggregate counts of sent, delivered, bounced, rejected, spam-complained, opened, clicked, and unsubscribed emails over a date range. The backbone of scheduled deliverability reporting.
- Get Bounce Stats Returns bounce statistics broken down by hard versus soft type and, where available, by cause. The diagnostic step when summary stats show something moving in the wrong direction.
Suppression Management
3- View Suppressions Lists suppressed addresses on the account. Used to audit the list and to verify state before any add or remove operation.
- Add Suppressions Adds one or more addresses to the suppression list so future sends skip them. How agents honor unsubscribes and block problem recipients the moment evidence appears.
- Remove Suppressions Removes addresses from the suppression list, allowing delivery again. The operation this page's human gate exists for.
Frequently Asked Questions
What can FlowRunner do with SMTP2GO?
FlowRunner agents can run Send Email, Search Activity, and Get Email Summary Stats in SMTP2GO, plus 4 more actions.
Does connecting SMTP2GO to FlowRunner require OAuth?
No. SMTP2GO connects to FlowRunner with an API key, no OAuth flow required.
Can SMTP2GO trigger a FlowRunner workflow automatically?
SMTP2GO doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SMTP2GO
$100 in credits. No card required. Connect in minutes.