--- title: "Maileroo Integration" description: "Maileroo is an SMTP relay and email delivery platform. Agents send single, templated, bulk, and scheduled email, read logs and suppressions, manage templates, domains, sending keys, and webhooks, and pull delivery statistics." url: https://flowrunner.ai/integrations/maileroo date_modified: 2026-09-04T14:51:36-07:00 --- # Maileroo [Email](https://flowrunner.ai/integrations/category/email-marketing) Maileroo is an SMTP relay and email delivery platform. Agents send single, templated, bulk, and scheduled email, read logs and suppressions, manage templates, domains, sending keys, and webhooks, and pull delivery statistics. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 37 actions · API key · available [Maileroo website](https://maileroo.com/) · [Platform Documentation](https://maileroo.com/) · Capability data verified 2026-08-19 1. A client approves next week's campaign in the project tracker 2. Agent resolves the client's sending domain, template, and recipient set 3. Get Domain confirms the domain's DNS records are in place before anything is queued 4. Send Bulk Emails schedules the run with a Reference ID so it stays cancelable 5. List Scheduled Emails confirms the queue holds exactly what the agent intended 6. The account team gets the scheduled time and the reference in their channel 7. The account lead confirms or cancels before the send window opens ## What This Integration Enables Maileroo is the connector to reach for when the thing you are managing is not a message but a sending estate. Domains, applications, and per domain sending keys are first class objects here, statistics resolve per domain and per application rather than only per account, and every management call carries a scope that says what the key holding it is allowed to touch. That shape matters most to a team sending on behalf of several clients or brands, because it is the difference between "our bounce rate went up" and "this client's welcome sequence went up." FlowRunner agents work that estate end to end. They compose and template messages, schedule them with a reference that keeps them cancelable, search the logs when a recipient says nothing arrived, render what was actually delivered, and manage the domains, templates, webhooks, and keys underneath. The [connectors](https://flowrunner.ai/concepts/connectors) do the reaching; the discipline that decides which of those calls a person has to authorize is FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) design, and on this platform it lands on the operations that cannot be taken back. ### Without FlowRunner **One estate, no attribution**: Several brands send through one account and nobody can say which one is carrying the bounce rate **Scheduled sends with no handle**: A queued message has no reference to address it by, so pulling it back means asking support **Guesswork about what shipped**: A client asks what their customer received and the answer is reconstructed from the template, not the message ### With FlowRunner **Volume attributed per sender**: Statistics resolve per domain and per application, so a deliverability problem has an owner **Scheduled sends that can be pulled**: Every scheduled message carries a Reference ID, which is the only way to cancel it before it leaves **The rendered message on file**: Render Email Log returns what the recipient actually received, so a support answer is evidence rather than inference ## Use Case Scenarios ### A client campaign that stays cancelable until it leaves Approval lands as a status change in [Asana](https://flowrunner.ai/integrations/asana) or [ClickUp](https://flowrunner.ai/integrations/clickup). The agent resolves the client's sending domain, confirms with Get Domain that the DNS records are still in place, and calls Send Bulk Emails with the shared template supplied once and each recipient's own data supplied per entry, scheduled for the agreed window and stamped with a Reference ID. It then calls List Scheduled Emails and posts the queue back to the account channel in [Slack](https://flowrunner.ai/integrations/slack). Because the reference exists, Cancel Scheduled Email is a real option right up to the send. Without one, a scheduled message has nothing to address it by. ### Deliverability forensics that answers the client's actual question A client reports that a customer never received their confirmation. The agent runs Search Email Logs filtered on the recipient and the date range, pulls the message with Get Email Log, and reads the event timeline. If the message was suppressed, List Suppressions says so, because a suppressed address fails silently rather than bouncing. If it was delivered, Render Email Log returns the content the recipient actually received after templating, which is usually where the misunderstanding lives. The agent appends the finding to the client's record in [HubSpot](https://flowrunner.ai/integrations/hubspot) and posts a summary the account manager can send without rewriting. ### The monthly key and template audit On a schedule, the agent walks List Applications and List Sending Keys for each domain, then joins that roster against Get Application Statistics and Get Domain Analytics to see which credentials are actually carrying traffic. Keys with no volume and an old last used timestamp go into a review list. Template changes get the same treatment: because Replace Template Content rewrites what every future send renders, including messages already scheduled against that template, the agent stages the new content, sends a single test through Send Templated Email, and posts the rendered result before anything is replaced. The audit ends where the next section begins. ## Human-in-Loop Highlight Delete Sending Key takes effect immediately and there is no undo. What makes it a decision rather than a chore is what the connector cannot see: List Sending Keys returns a key's name, its domain, and when it was last used, but nothing anywhere says which deployed integration is holding the value, and the value itself was shown once at creation and can never be read back. An agent that revokes the wrong one has silently broken a client's transactional mail with no way to restore the credential. So the audit agent assembles the case and stops. It posts the roster to the operations lead: "Key `wl-legacy-2` on `mail.clientco.com` last sent eleven days ago, no volume in Get Application Statistics since. Nothing in our register claims it. Revoke, or leave it and re-check the last used timestamp next month?" The evidence gathering is machine work. Deciding to cut a credential nobody can hand back is not. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 37 actions ### Sending 5 - **Send Email** Sends one message built from scratch, with an HTML body, a plain text body, or both, plus attachments, custom headers, tags for later filtering, and optional scheduling. - **Send Templated Email** Sends a message rendered from a template stored in Maileroo, with the placeholder values supplied as template data. Nested objects and arrays mean a receipt with a line item list is a single call. - **Send Bulk Emails** Sends many personalized messages in one request, with the shared subject, template, and settings given once and each entry carrying its own recipients and data. The right shape for a campaign. - **List Scheduled Emails** Returns messages queued for a future send with their recipients, subject, tags, and scheduled time. Used to prove the queue holds what a workflow intended before the window opens. - **Cancel Scheduled Email** Cancels a message that has not been sent yet, addressed by the Reference ID it was created with. A scheduled message sent without a reference cannot be canceled at all. ### Logs and Delivery Forensics 4 - **Search Email Logs** Searches the account's logs across every domain by message or reference identifier, sender, recipient, subject, tags, type, and date range, returning each message with its event timeline. - **Get Email Log** Reads one message from the logs with its recipients, tags, sending address, and full event timeline. Used when a flow needs the detail behind a single message rather than a page of them. - **Render Email Log** Returns the rendered content of a logged message, which is what the recipient actually received after templating. The operation that turns a support answer into evidence. - **Resend Email** Sends a logged message again exactly as it was. This delivers real mail and spends real quota, so workflows use it deliberately rather than as a retry. ### Suppressions 3 - **List Suppressions** Returns the addresses Maileroo will not deliver to, paginated and searchable. The first place to look when one recipient reports never receiving anything, because a suppressed address fails silently. - **Add Suppression** Adds an address to the suppression list with an optional free text note recording why. Workflows write a note a person will still understand months later. - **Remove Suppression** Removes a suppression so delivery resumes to that address. Used only when the reason for the original suppression has been examined, because re-mailing a hard bounce or a complaint costs reputation shared by every other recipient on the domain. ### Templates 6 - **List Templates** Returns the templates on the account with their identifiers, which is what a templated send needs. - **Get Template** Reads one template including its content, so a workflow can inspect what will be rendered before sending against it. - **Create Template** Creates a template from raw HTML, from a URL Maileroo fetches, from a base64 zip archive, or as an empty editor template. - **Update Template** Changes a template's metadata, most usefully its name. A partial update, so anything left empty is untouched rather than cleared. - **Replace Template Content** Replaces what a template renders. This changes every future send that uses it, including messages already scheduled against it, so workflows treat it as a deployment rather than an edit. - **Delete Template** Permanently removes a template. Anything that sends against that identifier afterwards fails, scheduled messages included. ### Domains 5 - **List Domains** Returns the sending domains on the account with their verification state. The first read when a send is refused for a From address that looks correct. - **Get Domain** Reads one sending domain in detail, including the DNS records it needs and whether each is in place. - **Create Domain** Adds a sending domain, either a custom domain proven with DNS records or a Maileroo hosted sub domain that needs no DNS work. - **Scan Domain DNS** Asks Maileroo to re-check a domain's DNS records and returns the state of each one, right after the records are published. - **Delete Domain** Removes a sending domain from the account. Every sending key issued for that domain stops working with it. ### Sending Keys 4 - **List Sending Keys** Returns the sending keys issued for a domain with their names and last used timestamps. The audit surface for which integrations can send as a domain. - **Create Sending Key** Issues a new sending key for a domain and returns it. The value appears on this response only and cannot be read back afterwards. - **Rotate Sending Key** Replaces a key's secret with a new one. The old value stops working immediately, so workflows rotate, deploy, then verify in that order. - **Delete Sending Key** Revokes a sending key permanently. The operation this page's human gate exists for. ### Webhooks 4 - **List Webhooks** Returns the webhook endpoints registered on the account with the domains and event types each is scoped to. - **Create Webhook** Registers an endpoint to receive event notifications, scoped to particular domains and event types. Naming the events a flow acts on keeps a busy account's traffic manageable. - **Update Webhook** Changes a webhook's destination, event types, or domain scope. A partial update, so omitted fields are left alone. - **Delete Webhook** Removes a webhook endpoint so Maileroo stops posting events to it. ### Statistics 4 - **Get Domain Analytics** Returns sending analytics for one domain, which is how to see which of several sending domains is carrying a deliverability problem. - **Get Statistics Summary** Returns aggregate sending statistics for the current calendar month, including per country open and click data. The window resets on the first rather than rolling. - **Get Statistics Timeline** Returns daily statistics for the last month, one point per day. Used to find the day a bounce rate started climbing rather than only the month's total. - **Get Application Statistics** Returns statistics for one application, which is how volume and engagement get attributed to a particular integration rather than to a domain. ### Account 2 - **Get Account** Returns the account the Account API Key belongs to. Used as a cheap check that a key is valid and points where a workflow expects before it changes anything. - **List Applications** Returns the applications on the account. An application is a sending identity that can span several domains, which is where to look when a key is scoped to one rather than to a domain. ## Frequently Asked Questions ### What can FlowRunner do with Maileroo? FlowRunner agents can run Send Email, Send Templated Email, and Send Bulk Emails in Maileroo, plus 34 more actions. ### Does connecting Maileroo to FlowRunner require OAuth? No. Maileroo connects to FlowRunner with an API key, no OAuth flow required. ### Can Maileroo trigger a FlowRunner workflow automatically? Maileroo doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Maileroo?** This integration exposes Maileroo to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/maileroo. Site index: https://flowrunner.ai/llms.txt