MailBluster

MailBluster is a bulk email platform that sends through your own Amazon SES account. Agents create and update leads by email, manage custom fields and tags, and sync products and orders for targeted campaigns.

Verified 18 actions API key available

MailBluster website Platform Documentation Capability data verified 2026-08-19

An order is paid in the storefront and reaches the agent

Agent reads the buyer, the line items, and the store's own product IDs

Create Product writes any catalog item MailBluster has not seen yet

Create Order files the purchase against the buyer's address

Update Lead adds the segment tags the next campaign will select on

Agent compares the tag set it is about to remove against what the lead already carries

The lifecycle owner confirms any tag removal that would drop a lead out of an active audience

What This Integration Enables

MailBluster is an unusual thing to automate, because its Developer API is deliberately not a sending API. Campaigns are built and sent in the MailBluster interface, through your own Amazon SES account. What the API owns is the data those campaigns run on: leads and their custom fields, and the products and orders that drive revenue attribution. That split is the whole reason this connector is useful. The people who chose MailBluster already own their sending infrastructure and did not want an ESP telling them how to send. What they usually still do by hand is keep the audience honest.

FlowRunner agents take that half. They create and update leads keyed on the email address, maintain the custom field definitions campaigns select on, and keep products and orders in step with the store so that per-campaign revenue reporting reflects what actually happened. The connector hashes the address for you on every lead route, so a flow passes plain text and never handles the MD5 form the vendor's URLs require. Where the work turns consequential, human-in-the-loop steps hold the decision: an agent that can tag ten thousand leads in a pass is also an agent that can detach the wrong tag from all ten thousand.

Without FlowRunner

Audience data edited by hand Segment tags get updated in the interface, one lead at a time, when someone remembers

Purchase history stranded in the store Campaign attribution depends on a periodic export that is stale the day it is made

Custom fields drift from the templates A merge tag gets renamed for tidiness and the templates that referenced it quietly break

With FlowRunner

Audience data maintained as a running process Every paid order updates the lead, the product, and the order record in the same pass

Purchase history arrives with the order Products and orders land under your own store IDs, so revenue reporting lines up without a mapping table

Field changes reviewed before they land The agent reads the merge tag mapping first and stops before renaming anything content depends on

Use Case Scenarios

The store keeps the audience current

A paid order lands from Shopify or WooCommerce. The agent calls Create Product for any catalog item MailBluster has not recorded, using the store's own product IDs so nothing needs a translation layer, then calls Create Order against the buyer's address. Create Lead runs with Override Existing on, so a returning customer is refreshed rather than refused. Update Lead adds the tags the next campaign will select on: first purchase, category bought, order value band. Nobody exports anything, and the segment a marketer picks in the MailBluster interface reflects this morning's orders rather than last month's.
Custom fields that survive a rename

Custom field values are stored against a merge tag, not against the label a person sees, and templates reference the merge tag too. A quarterly audit agent calls List Fields, pulls the label and merge tag pairs, and compares them against the merge tags actually used across the team's templates and its own flow definitions. Where a field exists with no content referencing it, the agent posts the candidates for removal to Slack. Where a label and its merge tag have drifted apart, it proposes the label change through Update Field and leaves the merge tag alone, because renaming that is not cosmetic.
A refund that does not keep selling

A refund posts in Stripe. The agent calls Get Order to read what the customer originally bought, then Update Order to replace the line item set with what the customer actually kept. Because Update Order replaces rather than merges, the agent builds the complete final line set before it calls, rather than sending the delta. Update Lead then removes the high-value-buyer tag the original order added. That last step is the one that goes to a person, because removing a tag also removes the lead from any audience built on it.

Human-in-Loop Highlight

Delete Lead is where MailBluster's shape stops being convenient and starts mattering. Leads have no list route. The vendor publishes create, view, update, and delete, and nothing else, so an agent can only read a lead when it already knows the address. That means a suppression sweep cannot be audited after the fact: there is no call that enumerates what is left, and no call that shows what went. So the sweep agent gathers its evidence first and then stops. It posts: "412 leads matched the dormant rule. 38 of them have an order in the last 90 days under a different address on the same domain. Delete all 412, delete 374, or export first?" The lifecycle owner answers in Slack. The agent then runs the deletions it was told to run, and writes the full address list to a sheet before it starts, because the API will not give it back afterward.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

18 actions

Leads

Create Lead Adds a lead by email address. Override Existing decides whether an address the account already holds is refused or updated, and Double Opt In decides whether the lead is subscribed as stated or has to confirm first. Used at the top of any signup or purchase flow.
Get Lead Reads one lead by address. The connector hashes the address before the call, so a flow passes plain text. Used to check current tags and field values before deciding what to change.
Update Lead Changes a lead's fields, subscription state, and tags. Add Tags and Remove Tags are applied in that order, so naming the same tag in both leaves it detached. Used for segment maintenance driven by behavior elsewhere.
Delete Lead Removes a lead permanently. Used in suppression and retention workflows, and the one operation on this connector that should not run without a person having seen the list.

Custom Fields

List Fields Returns every custom field with its label and its merge tag. Used once at the start of any flow that writes custom field values, because values are keyed on the merge tag rather than the label.
Create Field Defines a new custom field. Used when a new data point starts arriving from the store or the CRM and campaigns need to select on it.
Update Field Changes a field's label or merge tag. Both are required even when only one is changing. Used for content maintenance, with care, because leads store their values against the merge tag.
Delete Field Removes a custom field definition. Used in cleanup workflows after confirming no template references it.

Products

List Products Returns the catalog MailBluster holds, paged. Used to reconcile against the store before a sync run.
Get Product Reads one product by the ID your store assigned it. Used to check whether a catalog change has already landed.
Create Product Adds a product using your own identifier. Used at the front of a catalog sync so that order line items resolve without a mapping table.
Update Product Changes an existing product's details. Used when pricing, naming, or categorization changes in the store of record.
Delete Product Removes a product. Used when an item is discontinued and should stop appearing in revenue reporting.

Orders

List Orders Returns orders, paged. Used for reconciliation between the store's ledger and what MailBluster is attributing.
Get Order Reads one order and its line items. Used before an amendment, so the agent can build the replacement line set correctly.
Create Order Files a purchase against a lead, with your own order ID. Customer tags on an order merge with the tags the customer already carries rather than replacing them. Used to drive per-campaign revenue attribution.
Update Order Replaces an order's whole line item set rather than merging into it. Used for refunds, partial returns, and corrections, always with the complete final set.
Delete Order Removes an order record. Used when a transaction is voided and should not count toward attribution.

Frequently Asked Questions

What can FlowRunner do with MailBluster?

FlowRunner agents can run Create Lead, Get Lead, and Update Lead in MailBluster, plus 15 more actions.

Does connecting MailBluster to FlowRunner require OAuth?

No. MailBluster connects to FlowRunner with an API key, no OAuth flow required.

Can MailBluster trigger a FlowRunner workflow automatically?

MailBluster doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with MailBluster

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us