FlowRunner
PricingContact
Theme
Start Free

Emercury

Email Marketing

Emercury is an email marketing platform with audiences, automations, and autoresponders. Agents import subscribers, manage segments, custom fields, and suppression lists, schedule and send campaigns, and pull reporting.

49 actions Custom auth available
Emercury website Platform Documentation Capability data verified 2026-08-19
A monthly newsletter is due to go to a segmented audience
Agent reads the audience membership and the custom field values behind the segment
Get Suppression Lists confirms which do-not-mail sets apply to this send
Upsert Subscribers refreshes the audience in batches sized to the vendor's per-request limit
Send Campaign Test reaches the account's test group, which is the only address set this route accepts
The rendered preview and the audience count post to the review channel
A deliverability owner releases Add Schedule, which is the call that commits the send

What This Integration Enables

Most platforms in this category treat suppression as a checkbox. Emercury treats it as a product: suppression lists are their own objects, with their own read, their own creation route, a way to add contacts directly, and a bulk import that accepts hashed digests rather than plain addresses, which is how one company shares a do-not-mail list with another without disclosing who is on it. If your sending is governed by lists you did not write and cannot read, this is the connector shaped for that problem.

The second thing worth knowing before building on it is that Emercury separates a campaign from a send. A campaign is the message; a task is one dispatch of it. Recipient-level reporting is keyed to the task, not the campaign, and there is a lookup operation whose entire job is connecting the two. FlowRunner agents import and upsert subscribers, maintain audiences and custom fields, keep suppression current, build and rehearse campaigns, run autoresponders and automations, tag contacts, and pull reporting at the level the results actually live at. The writes that reach real people wait for a person, which is FlowRunner's human-in-the-loop default rather than a setting somebody has to remember to turn on.

Without FlowRunner

Suppression handled by memory The partner's do-not-mail file lives in an inbox and gets applied when somebody remembers
Reporting stops at the campaign Nobody can say which of the four sends of the same campaign produced the complaints
Partial writes read as success A bulk call reports back cleanly while half its rows were rejected inside the response

With FlowRunner

Suppression is a maintained object Do-not-mail sets are read, extended, and confirmed as part of the send flow rather than beside it
Reporting resolves to a send Results are pulled per send, so a repeated campaign is four measurable events rather than one average
Partial writes are visible Every bulk call reports succeeded and failed counts alongside the rows, so a flow checks rather than assumes

Use Case Scenarios

  • The audience is rebuilt before it is mailed

    Ahead of the monthly send, the agent reads the current segment from the warehouse in PostgreSQL and refreshes it in Emercury with Upsert Subscribers, splitting the work into batches the vendor's per-request limit accepts rather than sending one oversized call. Get Custom Fields supplies the variable names the write has to match, and Get Date Formats supplies the identifier that decides how the opt-in dates in the payload are read, which is the kind of setting that misreads every record rather than failing loudly. Get Confirmed Subscribers and Get Disabled Subscribers reconcile the result, and the counts post to Slack before the campaign is built.

  • Reporting that resolves to the actual send

    A campaign has gone out four times this quarter to overlapping audiences, and the revenue team wants to know which version worked. The agent calls Get Report IDs for the campaign, which returns the individual sends, then Get Report Statistics for each of them and Get Task Recipients to pull the recipient-level detail for the ones that stand out, including who unsubscribed from which particular dispatch. Get Campaign Statistics supplies the campaign-level rollup for context. The whole picture appends to Google Sheets, and the answer is about a send rather than an average of four.

  • A lifecycle sequence that starts from the CRM

    A deal stage changes in HubSpot. The agent tags the matching subscriber with Add Subscriber Tags, and where the sequence should begin immediately it calls Start Automation For Contact, which is a send rather than a label and is treated that way by the flow. Add Autoresponder configures the follow-up, with the campaign identifier supplied when the trigger is about a particular campaign and omitted when it is not, because those triggers require different things. Get Subscribers By Tag reads the cohort back so the team can see exactly who is in flight.

Human-in-Loop Highlight

Import Suppression Contacts has a toggle that decides whether the file it is reading holds plain addresses or hashed digests, and that toggle is the most dangerous single field on this connector. Set it wrongly and the import suppresses nobody, answers successfully, and leaves a suppression list that looks populated and protects no one. There is no error, no partial-success marker, and no way to read a hashed list back and check, because not being readable is the entire reason the hashed form exists. The first evidence of the mistake is a complaint from the partner whose list it was.

So the agent does not choose. It inspects the incoming file, reports what it found, and asks: "Suppression file from the affiliate contains 12,400 rows. Every row is a 32-character hex string, which reads as digests rather than addresses. Import as hashed? Importing in the wrong mode will report success and suppress nothing." The deliverability owner confirms the mode, and the agent then runs the import, verifies the list is present with Get Suppression Lists, and reports the count. A machine is better at the import. A person is the only thing that can confirm what the file was supposed to be.

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

49 actions

Audiences and Segments

5
  • Get Audiences Returns the audiences on the account. The starting point for resolving a target by name rather than by a hardcoded identifier.
  • Add Audiences Creates one or more audiences. Reports per-item outcomes with succeeded and failed counts, so a call that partly worked is visible as such.
  • Delete Audiences Removes audiences from the account.
  • Create Filter Defines a segment over an audience, which is how a send is narrowed without maintaining a second list.
  • Get Categories Returns the campaign categories the account uses, which a campaign write has to reference.

Subscribers

9
  • Get Subscribers Reads subscribers from an audience with their field values.
  • Upsert Subscribers Creates or updates a batch of subscribers. Refuses a batch larger than the vendor accepts rather than letting it fail on the far side, and matches existing records on the account's variable names.
  • Delete Subscribers Removes subscribers from an audience. It records no opt-out, so a deleted address can be added back and will receive mail again.
  • Import Subscribers Loads a larger set than the per-request limit allows, for backfills and migrations.
  • Get Date Formats Returns the identifiers that decide how opt-in dates in a write are interpreted. Required by both subscriber write routes, and getting it wrong misreads dates rather than failing.
  • Get Confirmed Subscribers Lists the subscribers who completed confirmation, which is the mailable population rather than the imported one.
  • Get Disabled Subscribers Lists subscribers who are present and not mailable.
  • Unsubscribe Emails Records an opt-out. The route that honors consent, as distinct from removing the record.
  • Get Unsubscribes For Audience Reads the opt-outs recorded against a whole audience, rather than against one particular send.

Custom Fields

2
  • Get Custom Fields Returns the account's field definitions and the variable names that subscriber writes match on.
  • Update Custom Fields Renames a field by its numeric identifier. Renaming changes the variable name that writes match on, so anything already targeting the old name stops matching.

Suppression

4
  • Get Suppression Lists Returns the suppression lists on the account. The confirmation step before a send, and the readback after an import.
  • Add Suppression Lists Creates a suppression list, for example one per partner or per acquisition source.
  • Add Suppression Contacts Adds addresses to a suppression list directly.
  • Import Suppression Contacts Loads a suppression list in bulk, in either plain or hashed form. The mode is the field this page's human gate exists for, because the wrong choice reports success and suppresses nothing.

Campaigns

9
  • Get Campaigns Returns the account's campaigns.
  • Add Campaign Creates a campaign with its audiences, sender details, subject, and body.
  • Update Campaign Replaces a campaign's configuration. The vendor requires the full set of fields, so anything omitted is not preserved and the flow reads before it writes.
  • Send Campaign Sends immediately. The response confirms the campaign is queued rather than delivered.
  • Add Schedule Schedules a campaign, which means committing it to send. Accepts quarter-hour times only, and the connector checks that locally rather than letting the platform refuse it.
  • Get Campaign Schedules Reads what is currently scheduled, which is how a flow checks before it adds another.
  • Get Campaign Preview Renders the campaign so a reviewer sees what recipients will see.
  • Get Test Subscribers Returns the account's test groups, which is where the test route gets its targets.
  • Send Campaign Test Sends a rehearsal to a test group. It takes test group identifiers rather than addresses, so an arbitrary reviewer has to be added to a group first.

Autoresponders and Automations

9
  • Add Autoresponder Creates an autoresponder. Triggers about a particular campaign require the campaign identifier and the others do not, and being enabled is separate from being immediate.
  • Get Automations Returns the automations configured on the account.
  • Add Automation Creates an automation. The platform supports one trigger here, keyed on either the added date or the opt-in date, so anything richer is built in the interface.
  • Add Automation Message Settings Configures the settings for a message inside an automation.
  • Add Automation Message Adds a message to an automation.
  • Get Automation Messages Reads the messages inside an automation, so a flow knows what enrolling somebody sets off.
  • Get Automation Message Statistics Reads how each message in an automation is performing.
  • Update Automation Status Enables or disables an automation. A disabled automation exists and does nothing.
  • Start Automation For Contact Puts one person into an automation, which starts its messages. A send rather than a label.

Reporting

4
  • Get Report IDs Returns the individual sends belonging to a campaign. The lookup that connects a campaign to its dispatches, and the prerequisite for recipient-level reporting.
  • Get Report Statistics Reads results for particular sends rather than for the campaign as a whole.
  • Get Task Recipients Reads recipient-level detail for one send, including who unsubscribed from that specific dispatch.
  • Get Campaign Statistics Reads the campaign-level rollup across all of its sends.

Tags

5
  • Get Tags Returns the tags defined on the account.
  • Get Subscriber Tags Reads the tags carried by one subscriber.
  • Add Subscriber Tags Tags a subscriber, which is how a CRM stage change becomes an audience change.
  • Delete Subscriber Tags Removes tags from a subscriber.
  • Get Subscribers By Tag Reads the cohort carrying a tag, so a team can see who is in flight before anything is sent to them.

Account

2
  • Get Tracking Code Returns the account's tracking code, and can generate one where the account has none. A write dressed as a read, so flows call it deliberately.
  • Get Sender Profiles Returns the confirmed sending identities. A send from an address that is not on this list is refused, so the flow checks first.

Frequently Asked Questions

What can FlowRunner do with Emercury?

FlowRunner agents can run Get Audiences, Add Audiences, and Delete Audiences in Emercury, plus 46 more actions.

Does connecting Emercury to FlowRunner require OAuth?

Emercury uses a custom authentication method to connect to FlowRunner.

Can Emercury trigger a FlowRunner workflow automatically?

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

Start building with Emercury

Free plan, no card required. Connect in minutes.