Elastic Email
EmailSend transactional and bulk email through Elastic Email. Agents deliver receipts and password resets, send marketing email with HTML and plain text content, manage contacts and lists, and read account level statistics on delivery, opens, clicks, and bounces.
What This Integration Enables
Elastic Email draws the line every email platform should: transactional messages that a user's own action earned, and bulk messages that your calendar decided. The API keeps the two on separate paths, and FlowRunner keeps them on separate rules. Agents send receipts, resets, and confirmations the instant the triggering event happens, with no human in the way, because the user is waiting. Bulk sends run the opposite discipline: the agent builds the audience and drafts the send, and a person owns the moment it leaves. - Send transactional email from workflow events, exempt from bulk suppression rules - Send bulk and marketing email with HTML and plain text content, saved templates, and CC/BCC - Add, update, look up, and remove contacts, and organize them into lists with unsubscribe control - Enumerate campaigns and templates so sends reference maintained content instead of hardcoded HTML - Track account-level delivery, opens, clicks, bounces, and unsubscribes as a scheduled feed
Without FlowRunner
With FlowRunner
Use Case Scenarios
The welcome path that never waits
A signup arrives from a [Typeform](/integrations/typeform) response. The agent calls Get Contact to check for an existing record, Add Contact to create the subscriber on the onboarding list, and Send Transactional Email to deliver the welcome message with the account details merged into the saved template. Because transactional sends bypass bulk suppression rules, the message arrives while the signup still has the product open. The contact's status and source are set at creation, so the marketing audience stays segmented from day one.
Audience hygiene that runs on CRM truth
Lead records change in [Airtable](/integrations/airtable) all week: new captures, role changes, opt-outs recorded by sales. A nightly agent reads the changed rows and reconciles Elastic Email against them: Add Contact for new leads with the right list assignment, Update Contact for name and status changes, and a flagged queue for records marked as opt-outs. The Unsubscribed status gets set immediately; any request to fully delete a contact record goes to a person first. The list you send to on Thursday reflects what sales knew on Wednesday night.
Deliverability as a dashboard someone actually sees
Every morning, the agent calls Get Account Statistics scoped to the trailing day and appends the numbers to [Google Sheets](/integrations/google-sheets): sent, delivered, opened, clicked, bounced, unsubscribed. It compares bounce and unsubscribe rates against the trailing month's baseline, and when either breaks threshold, it posts to [Slack](/integrations/slack) with the trend attached. When a stale segment starts bouncing, the team finds out the morning after the send, pauses the next campaign, and cleans the list before the sender reputation pays for a second bad blast.
Human-in-Loop Highlight
Send Email is a bulk operation aimed at every address in its recipient set, and email has no undo. The cost of a bad send is paid twice: once in the inboxes of the people who got the wrong message, and again in the account's sender reputation, where the resulting bounces, unsubscribes, and abuse reports linger in the statistics long after the apology. So bulk sends in FlowRunner run gated. The agent assembles everything: audience from the list, template by name, subject, and schedule. Then it stops: "Campaign draft: March product update, template product-update-v3, 18,400 recipients on the Engaged list. Send?" A person catches that the audience should have excluded last week's trial expirations, trims the segment, and approves. Send Transactional Email needs no such gate; the user asked for that message by acting. The distinction between the two is the whole discipline.
Agent Capabilities
12 actionsSending
2- Send Email Sends a bulk marketing or standard email to one or more recipients from a verified sender address, with subject, HTML and/or plain-text content, optional saved template, and CC/BCC. Returns a transaction and message identifier. The bulk path this page's human gate exists for.
- Send Transactional Email Sends a single transactional email such as a receipt, password reset, or order confirmation, exempt from bulk-sending suppression rules. Provide a verified sender, subject, and content, with optional template and CC/BCC. The path for messages a user's action earned.
Contacts
5- List Contacts Retrieves a paginated list of contacts with each contact's email, name fields, status, and activity statistics. The audit step behind reconciliation sweeps.
- Get Contact Retrieves a single contact by email address, including name fields, status, source, consent details, and engagement statistics. Used to check consent and history before adding or messaging.
- Add Contact Adds a new contact, optionally assigned to one or more existing lists, with email, name fields, and status. The step that turns a signup into an audience member.
- Update Contact Updates an existing contact identified by email address, changing any of first name, last name, or status while leaving omitted fields untouched. The workhorse of nightly reconciliation.
- Delete Contact Permanently deletes a contact by email address. This action cannot be undone, so cleanup workflows route it through review.
Lists
2- List Lists Retrieves the contact lists in the account, including each list's name, unsubscribe setting, and creation date. Used to resolve list targets before assignment.
- Create List Creates a new contact list, optionally seeded with existing contacts and configured for whether recipients may unsubscribe. The step that turns a query result into a sendable segment.
Campaigns and Templates
2- List Campaigns Retrieves the email campaigns in the account with each campaign's name, status, and configuration, paginated. Used for campaign inventory and reporting.
- List Templates Retrieves saved email templates, filterable by type and scope, returning each template's name, subject, and metadata. The picker behind template-based sends.
Reporting
1- Get Account Statistics Retrieves aggregate account statistics including sent, delivered, opened, clicked, bounced, and unsubscribed counts, optionally scoped to a date range. The feed behind deliverability monitoring.
Frequently Asked Questions
What can FlowRunner do with Elastic Email?
FlowRunner agents can run Send Email, Send Transactional Email, and List Contacts in Elastic Email, plus 9 more actions.
Does connecting Elastic Email to FlowRunner require OAuth?
No. Elastic Email connects to FlowRunner with an API key, no OAuth flow required.
Can Elastic Email trigger a FlowRunner workflow automatically?
Elastic Email doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Elastic Email
$100 in credits. No card required. Connect in minutes.