BigMailer

BigMailer is a multi-brand email marketing platform that sends through your own Amazon SES or other delivery connection. Agents manage brands, contacts, lists, fields, and segments, build bulk, RSS, and transactional campaigns, and maintain suppression lists.

Verified 80 actions API key available

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

A signup arrives for one of the brands the account runs

List Brands resolves which brand's contact pool, sending identity and unsubscribe page the signup belongs to

List Fields supplies the merge tags and the declared type of each field in that brand

Create Or Update Contact writes the contact into the brand and onto the list it joined

Get Contact reads the stored record back, because writes return an identifier and never the record

The brand owner receives the day's additions for their brand alone

A person approves any change to a brand's field definitions before it is applied

What This Integration Enables

BigMailer is built for running several sending identities at once on delivery infrastructure you own. A brand is the top level container, and contacts, lists, fields, message types, segments, templates, senders, suppression lists and every campaign belong to one, with identifiers that are only meaningful inside it. Above the brand sit just the connections, which is where the platform's real position shows: campaigns go out through your own Amazon SES or equivalent connection, so deliverability and cost stay yours rather than being bundled into a per contact price.

That shape suits agencies, portfolio companies and anyone whose brands must not share a reputation. It also creates a lot of per brand bookkeeping, which is where FlowRunner agents earn their place. An agent can stand a new brand up end to end, keep contacts and segments current, poll a batch import to completion and report the rows that failed, watch a sender's verification state, and hold a campaign as a draft until the checks pass. Writes on this API return an identifier and never the stored record, so an agent that cares about the result reads it back. The human-in-the-loop gate on this page sits on the one class of change whose blast radius covers a whole brand at once.

Without FlowRunner

One inbox for every brand Separate clients or product lines share a sending identity, and one brand's complaints hurt the others

Imports that look clean A bulk load reports success while individual addresses inside it were rejected

Field changes made hopefully A custom field is edited in place, and nobody checks which templates read it

With FlowRunner

Brands kept genuinely separate Contacts, lists, senders, suppression and bounce thresholds all live inside the brand they belong to

Imports checked row by row Every batch is polled to completion and the rejected rows are matched back to the source row

Field changes reviewed first A change that would destroy stored values or empty a merge tag is put in front of a person

Use Case Scenarios

Standing up a brand without a checklist

A new client or product line arrives. The agent calls Create Brand with its sending identity, unsubscribe page and the bounce thresholds that pause a running campaign automatically, then Create Sender for the domain or address it will send from and Get Sender to read back the DNS records that have to be published. Once those records are live, Verify Sender re-checks them and reports whether they resolved. Create Bounce Domain adds the subdomain that makes bounces come back to a domain the client controls, and Verify Bounce Domain confirms it. Create List, Create Message Type and Create Brand Property finish the scaffolding, and Create Template loads the reusable HTML. List Connections confirms which delivery service the brand will actually send through. What used to be a page of manual steps becomes one run, with List Brands and Get Brand available afterwards to prove the state.
A bulk import that reports its own failures

A list arrives from Google Sheets or from a client's own export. The agent chunks it and calls Upload Contact Batch, which queues the contacts and returns only a batch identifier, then polls Get Contact Batch until the run reports complete. This is the step most imports get wrong: the response is a success even when individual entries inside it were rejected, so the agent reads the per entry results, matches each rejection back to its source row through the identifier it set on the entry, and posts the failures to Slack rather than recording a clean import. Ahead of a send, Upload Suppression List builds a per campaign exclusion from addresses the client has asked to leave alone, and List Suppression Lists and Get Suppression List keep track of what was attached to which campaign.
Campaigns that stay drafts until the checks pass

Create Bulk Campaign builds a newsletter as a draft, because nothing is scheduled until the campaign is marked ready. The agent resolves the audience through List Lists and List Segments, calls Send Test Campaign to put a proof in front of the reviewer with merge tags filled from each field's sample value, and only then calls Update Bulk Campaign to release it. For a blog, Create RSS Campaign turns a feed from WordPress into a standing rule that mails an issue whenever there are new items, with Pause RSS Campaign and Unpause RSS Campaign available when a launch week needs quiet. Because the parent campaign carries no delivery statistics of its own, List RSS Campaign Issues and Get RSS Campaign Issue are where the opens and clicks actually live. Transactional messages follow the same draft pattern: Create Transactional Campaign defines the reusable body, and Send Transactional Email fires it at one address at a time once the campaign is ready.

Human-in-Loop Highlight

Custom fields in BigMailer have a type that is fixed at creation. Update Field will change a name, a merge tag or a sample value, but it will not change the type, because the vendor does not accept one on that route. So the only way to correct a field that was declared as text when it should have been a date is to delete it and create it again. Delete Field permanently removes the field and the values stored against it on every contact in the brand, and any template that still references its merge tag renders the tag with no value at all rather than failing, which means the damage shows up as a blank space in a delivered email rather than as an error anybody sees. Templates and segments built on that field are affected the same way. The agent therefore never deletes a field on its own initiative. It gathers the evidence first: how many contacts hold a value for that field, which templates reference its merge tag, and which segment conditions test it. Then it asks: "Correcting this field's type means deleting it, which destroys the stored values across the whole brand and empties the merge tag in the templates listed below. Proceed, or create a second field alongside it and migrate?" The brand owner decides, and the usual answer is to migrate, which the agent can then carry out contact by contact. The inventory and the migration are machine work. Destroying a brand's stored data to fix a declaration is not.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

80 actions

Brands

List Brands Lists the brands in the account with the contact count and aggregate engagement of each. A brand is the top level container that everything else belongs to.
Get Brand Reads one brand in full, including its default sender details, its contact count and limit, and the bounce thresholds that pause a running campaign automatically.
Create Brand Creates a brand with its own sending identity, unsubscribe page and contact pool.
Update Brand Updates a brand. Only the fields supplied change, and the response carries the identifier rather than the stored record, so the brand is read back when the values matter.

Brand Properties

List Brand Properties Lists a brand's properties. A property is a fixed value substituted into templates through its merge tag, such as a company address or a support address.
Get Brand Property Reads one brand property, including the merge tag templates reference it by and whether its value is treated as HTML.
Create Brand Property Creates a brand property. The merge tag name is how templates reference the value.
Update Brand Property Updates a brand property. Only the fields supplied change.
Delete Brand Property Permanently deletes a brand property. Templates that still reference its merge tag render the tag with no value.

Connections

List Connections Lists the sending connections on the account. A connection is the delivery service campaigns actually go out through, and it sits above the brand rather than inside it.
Get Connection Reads one sending connection, including which delivery service it uses.

Contacts

List Contacts Lists contacts in a brand, optionally narrowed to one list. Each carries its field values, list memberships and the message types it has unsubscribed from.
Get Contact Reads one contact by identifier or by address, with its field values, memberships, unsubscribe state and bounce counts.
Create Contact Adds a contact to a brand and, optionally, to lists within it. Fails on an address that already exists in the brand.
Create Or Update Contact Creates a contact, or updates the existing one when the address is already in the brand. The safe choice for a signup flow, because it cannot fail on a duplicate.
Update Contact Updates a contact by identifier or address. Three mode parameters decide whether the values sent replace what is stored or add to it, and the vendor's default is to replace.
Delete Contact Permanently deletes a contact from a brand and every list in it. Deleting does not suppress the address, so an opt out is recorded rather than acted on this way.
Upload Contact Batch Queues a batch of contacts to be created or updated in one asynchronous job and returns the batch identifier. Nothing is stored by the time it returns.
Get Contact Batch Reads the progress of an uploaded batch, with counts for created, updated and rejected. Individual entries can be rejected inside an otherwise successful response, so the entries are read rather than the status alone.

Lists

List Lists Lists the contact lists in a brand. Every brand also has a system list holding every contact in it, which cannot be deleted.
Get List Reads one list, including its contact count and how many of its contacts have opened or clicked at least one email.
Create List Creates an empty contact list in a brand.
Update List Renames a list.
Delete List Deletes a list. The contacts on it are not deleted; they lose that membership and remain in the brand.

Fields

List Fields Lists the custom contact fields defined in a brand, with the merge tag each is referenced by and the sample value used when sending a test campaign.
Get Field Reads one custom field. The stored type decides how a contact's value must be sent, so this is read before a write that carries field values.
Create Field Creates a custom contact field in a brand. The type is fixed once created and decides how contact values must be sent, so it is chosen deliberately.
Update Field Updates a custom field's name, merge tag or sample value. The type is not updatable on this route.
Delete Field Permanently deletes a custom field and the values stored against it on every contact in the brand. Templates referencing its merge tag render the tag with no value. The operation this page's human gate exists for.

Message Types

List Message Types Lists the message types in a brand. A message type is the unit a contact unsubscribes from, so leaving your product announcements does not stop your billing mail.
Get Message Type Reads one message type, including whether it is defined on the brand, shared across the account, or applies to all.
Create Message Type Creates a message type in a brand, giving contacts a category they can unsubscribe from on its own.
Update Message Type Renames a message type. Contacts already unsubscribed stay unsubscribed, because the unsubscribe is stored against the identifier rather than the name.
Delete Message Type Deletes a message type from a brand. Campaigns that referenced it lose that categorization.

Segments

List Segments Lists the segments in a brand. A segment is a saved set of conditions evaluated when a campaign is sent, so it always reflects the contacts as they are at that moment.
Get Segment Reads one segment with its full condition set and whether all conditions must match or any one of them.
Create Segment Creates a segment from a set of conditions.
Update Segment Updates a segment's name, operator or conditions. Conditions replace the stored set rather than adding to it, so the complete list is sent every time.
Delete Segment Deletes a segment. The contacts it matched are untouched, and campaigns that referenced it lose their filter.

Templates

List Templates Lists the templates in a brand. A template holds reusable HTML for either an email or a landing page, and may be shared across every brand on the account.
Get Template Reads one template with its full body, its type and whether it is shared.
Create Template Creates a template from HTML. The type decides where it can be used, and merge tags in the body are substituted at send time.
Update Template Updates a template. Sending HTML replaces the whole body rather than patching it, and campaigns already built from the template keep the HTML they were created with.
Delete Template Permanently deletes a template. Campaigns already built from it are unaffected, since the HTML is copied into the campaign at creation.

Senders and Domains

List Senders Lists the sending identities of a brand. A campaign can only go out from a verified one.
Get Sender Reads one sender, including the DNS records that have to be published to verify it and the records for its bounce domain.
Create Sender Registers a sending identity for a brand, either a whole domain or one specific address. Creating it does not make it usable.
Update Sender Changes whether a sender is shared with every brand on the account. The identity itself cannot be edited, so a wrong domain is replaced rather than corrected.
Delete Sender Deletes a sending identity from a brand. Campaigns configured to send from it fail until another verified sender covers the address.
Verify Sender Asks BigMailer to re-check the DNS records for a sender and returns whether they resolved. Publish the records first, because this reports an unverified state rather than failing.
Create Bounce Domain Adds a bounce subdomain to a sender, which is what makes bounces come back to a domain you control instead of to the sending service.
Verify Bounce Domain Asks BigMailer to re-check the DNS records for a sender's bounce domain and returns whether they resolved.

Suppression Lists

List Suppression Lists Lists the campaign suppression lists uploaded to a brand, with the file name and size of each.
Get Suppression List Reads one campaign suppression list. Only its metadata comes back, because the vendor does not serve the addresses it contains.
Upload Suppression List Uploads a campaign suppression list from a set of addresses and returns its identifier, which is then attached to a bulk or RSS campaign. It is per campaign rather than account wide.

Bulk Campaigns

List Bulk Campaigns Lists the newsletter and broadcast campaigns in a brand, each with its status and its delivery counts.
Get Bulk Campaign Reads one bulk campaign in full, including its content, its audience, its schedule and its live statistics.
Create Bulk Campaign Creates a bulk campaign as a draft. Nothing is sent or even scheduled until the campaign is marked ready.
Update Bulk Campaign Updates a bulk campaign, and is also how a draft is released. A campaign that has already gone out cannot be changed.

RSS Campaigns

List RSS Campaigns Lists the RSS campaigns in a brand. An RSS campaign watches a feed on a schedule and is a standing rule rather than a single send.
Get RSS Campaign Reads one RSS campaign, including the feed it watches, how often it is checked, its audience and its content.
Create RSS Campaign Creates a campaign that watches a feed and mails an issue when it has new items. Nothing is checked or sent until the campaign is marked ready.
Update RSS Campaign Updates an RSS campaign's feed, schedule, audience or content. Supplying any part of the schedule rebuilds the whole frequency, so it is sent complete.
Pause RSS Campaign Stops an RSS campaign from checking its feed and sending further issues. Issues already sent are unaffected.
Unpause RSS Campaign Resumes a paused RSS campaign so its feed is checked again on its own schedule.
List RSS Campaign Issues Lists the individual issues an RSS campaign has sent. Each issue is its own record with its own statistics, which is where the opens and clicks actually live.
Get RSS Campaign Issue Reads one issue sent by an RSS campaign, with the content as it went out and that issue's statistics.

Transactional Campaigns

List Transactional Campaigns Lists the transactional campaigns in a brand. A transactional campaign is a reusable message that is then fired at one address at a time.
Get Transactional Campaign Reads one transactional campaign with its content and its cumulative statistics across every send made from it.
Create Transactional Campaign Creates a transactional campaign: the reusable body, subject and sender. It cannot be sent from until it is marked ready, and a campaign left as a draft looks normal and fails at send time.
Update Transactional Campaign Updates a transactional campaign's content or settings, and is also where a draft is made ready. Changes apply to every later send from it.
Send Transactional Email Sends one email to one address through an existing transactional campaign, which supplies the subject, body and sender. Field values are stored on the contact, while variables exist for that one message only.

Test Campaigns

List Test Campaigns Lists the test sends made in a brand, each with its recipients. A useful audit of what was previewed before a real campaign went out.
Get Test Campaign Reads one test send, including the exact content that went out, the addresses it reached and its status.
Send Test Campaign Sends a proof of some content to a short list of addresses without touching any contact list. Merge tags are filled from each field's sample value rather than from a real contact.

Users

List Users Lists the users on the account with the role of each and whether they have accepted their invitation. Roles below account level are scoped to specific brands.
Get User Reads one user, including their role, the brands they may access and whether they have activated their account.
Create User Invites a user to the account with a role and emails them an invitation they must follow before the account is active.
Update User Changes a user's role, address or brand access. The allowed brands list replaces the stored set rather than adding to it, so the full list is sent.
Delete User Removes a user from the account. The account owner cannot be deleted.

Frequently Asked Questions

What can FlowRunner do with BigMailer?

FlowRunner agents can run List Brands, Get Brand, and Create Brand in BigMailer, plus 77 more actions.

Does connecting BigMailer to FlowRunner require OAuth?

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

Can BigMailer trigger a FlowRunner workflow automatically?

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

Start building with BigMailer

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us