UniOne

UniOne is a transactional email API with data centers in the EU and US. Agents send mail from templates, validate addresses, manage suppressions and unsubscribes, configure domains and webhooks, and pull event dumps for reporting.

Verified 36 actions API key available

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

A lifecycle event fires for a customer in the product database

Agent gathers the recipient and the substitutions that personalize their copy

Check Unsubscribed and Get Suppression read both consent lists, because either one drops the message silently

List Domains confirms the sending domain has passed its DKIM and ownership checks

Send Email renders the stored template with every consent bypass flag left off

Create Event Dump reconciles the run and the summary posts to the team channel

A person authorizes any change to a project, including the deletion that would take its suppression list with it

What This Integration Enables

UniOne models two things most transactional email APIs blur together. Consent is kept as two separate lists, because an unsubscribe is the recipient's own decision recorded through the unsubscribe page while a suppression can also be a bounce or a complaint, and either one drops a message silently rather than bouncing it. And the project, not the account, is the isolation boundary: each one has its own API key, its own suppression list, and its own sending settings, with data centers in the EU and the US. That combination is what makes this platform a reasonable choice for a team that has to keep a customer's mail, a test environment, and a partner's sending genuinely separate.

FlowRunner agents send from stored templates with per recipient substitutions, validate an address before spending a bounce on it, keep suppressions and unsubscribes in step with your own database, verify domains, and pull event exports for reconciliation when webhooks are not the right shape. The platform also ships flags that can override an opt out. FlowRunner's position on those is not subtle: agents leave them off, and the decisions that touch a consent record reach a person first. That is what FlowRunner's human-in-the-loop design is for, and this connector gives it something specific to protect.

Without FlowRunner

Consent recorded in one place An opt out lives in the sending platform and the customer database never hears about it

Environments sharing a reputation A test run and a production campaign send from the same settings, so a mistake in one is felt by the other

Reconciliation by webhook only If the receiver was down, the record of what happened is whatever survived the retries

With FlowRunner

Consent synchronized both ways Unsubscribes flow back into your own systems and opt outs made in your interface are recorded here

Environments isolated by project Each project carries its own key, its own suppression list, and its own sending settings

Reconciliation on demand An event export covers a whole range after the fact, independent of whether any endpoint was listening

Use Case Scenarios

A lifecycle send that reads consent before it reads the template

An event lands from the product database in PostgreSQL or Supabase. Before composing anything, the agent calls Check Unsubscribed and Get Suppression, because the two lists answer different questions and a message dropped by either one leaves no bounce to notice. If both are clear, it calls List Domains to confirm the sending domain still passes its checks, then Send Email with the stored template and the recipient's own substitutions, every bypass flag off. At signup the same workflow calls Send Subscribe Confirmation instead, so a later campaign has a documented consent behind it rather than an assumption.
Reconciliation that does not depend on a listener

Webhooks are the right tool when the receiver is healthy and the wrong one when it was not. On a schedule, the agent calls Create Event Dump for the previous day filtered by domain and campaign, then Download Event Dump, which folds the poll and the fetch into one call and pulls the finished file into FlowRunner file storage when it is ready. The rows append to a sheet in Google Sheets or load into Snowflake for the weekly deliverability review. List Event Dumps finds an export a previous run started, and Delete Event Dump clears the file once the rows are safely landed.
Opt outs that stop being a one system fact

Someone unsubscribes through the account settings in your own product rather than through an emailed link. The agent calls Set Unsubscribed so the decision is recorded in the same place UniOne's own unsubscribe page writes to, and the reverse sweep runs nightly: List Unsubscribed since yesterday, then write each address back to its record in HubSpot so no other tool mails them either. When a campaign misbehaves, Update Project with sending disabled is a digital andon cord the agent may pull on its own authority, because stopping the line is always the safe direction to move.

Human-in-Loop Highlight

Delete Project is the most destructive call on this connector, and not because of the sending it stops. A project owns its suppression list, so deleting one destroys the record of who asked not to be emailed, and consent decisions kept only there are gone with no way to reconstruct them. Its API key also stops working immediately, so anything still holding that key fails from the next call. An agent doing environment cleanup can see that a project is idle. It cannot see whether that project's suppression list is the only surviving record of a complaint someone filed two years ago. So the cleanup agent exports first and asks second: it runs List Suppressions and List Unsubscribed for the project, writes both to storage, and posts the summary to the marketing owner. "Project partner-eu-2024 has sent nothing in ninety days. It holds 812 suppressions and 3,190 unsubscribes, exported and attached. Which project should those be merged into before it is deleted?" The export is the agent's job. Deciding that a consent record is safe to destroy 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

36 actions

Sending

Send Email Sends a transactional message with per recipient substitutions so one call produces personalized copy for every recipient. Bodies can be HTML, plain text, or a stored template, and the flags that would override an opt out stay off by default.
Send Subscribe Confirmation Sends UniOne's own double opt in confirmation and records the recipient's answer against the account. Used at signup so a later send rests on a documented consent.
Validate Email Checks one address before sending to it and returns the verdict with the checks behind it. Cheaper than a bounce, and it protects the sending reputation every other recipient on the domain shares.

Templates

List Templates Returns the stored templates on the project, which is where a send gets its template identifier.
Get Template Reads one template including its body, subject, and default sender, so a workflow can inspect what will be rendered before sending against it.
Save Template Creates a template, or updates an existing one when an identifier is supplied. It replaces rather than merges, so workflows read the current version first and pass back everything worth keeping.
Delete Template Permanently removes a stored template. Any send naming that identifier afterwards fails.

Suppressions and Unsubscribes

List Suppressions Returns suppressed addresses filterable by cause, by who added them, and by date, walked with a cursor. The read behind consent exports and migration audits.
Get Suppression Looks up one address and reports whether it is suppressed and why. It checks only the current project unless the all projects flag is set.
Add Suppression Adds an address to the suppression list with its cause recorded. Used to import an existing opt out list at migration so decisions made elsewhere are honored from the first send.
Delete Suppression Removes an address so delivery resumes. Workflows examine why it was suppressed first, because re-mailing a complaint or a hard bounce costs reputation shared by every other recipient.
Check Unsubscribed Reports whether an address has unsubscribed. A different list from suppressions, and both have to be read to know whether a message will actually be delivered.
List Unsubscribed Returns addresses that have unsubscribed since a given date. The feed to sync back into your own database so an opt out is honored everywhere rather than only here.
Set Unsubscribed Marks an address as unsubscribed, writing to the same place the emailed unsubscribe link writes to. Used when someone opts out through your own interface.

Domains

List Domains Returns the sending domains on the project with their verification state. The first read when a send is refused for a From address that looks correct.
Get Domain DNS Records Returns the DNS records a domain needs, which is what gets published at the DNS provider.
Validate Domain DKIM Asks UniOne to re-check a domain's DKIM record. DKIM is what lets a receiving server prove the mail really came from you, so a domain without it is far likelier to land in spam.
Validate Domain Ownership Asks UniOne to re-check the ownership verification record. A separate check from DKIM, so a domain can pass one and fail the other.
Delete Domain Removes a sending domain from the project. Anything still sending from an address at that domain fails from the next call onward.

Webhooks

List Webhooks Returns the webhook endpoints on the project with the events each subscribes to and its current state.
Get Webhook Reads one webhook by its URL, which is how UniOne addresses them: the URL is the key rather than a separate identifier.
Save Webhook Registers a webhook or updates the one already at that URL. It replaces rather than merges, so the full event list has to be passed each time.
Delete Webhook Removes a webhook. Events stop immediately and are not queued, so a temporarily unavailable receiver is better paused by saving it inactive.

Event Dumps

Create Event Dump Starts a background export of delivery events over a range, filtered by job, status, address, sender, domain, or campaign. The bulk alternative to webhooks for reconciling what happened after the fact.
Get Event Dump Reads an export's state and, once finished, the URL to download it from.
Download Event Dump Reads an export and, when it is ready, downloads the file into FlowRunner file storage. Still running returns the state instead, so a workflow can poll one operation rather than pairing a check with a fetch.
List Event Dumps Returns the exports on the project with their state, so a workflow can find one an earlier run started without having kept the identifier.
Delete Event Dump Removes an export and its file. Anything worth keeping is downloaded first, because the file is not recoverable afterwards.

Projects and Tags

List Projects Returns the projects on the account. A project is the isolation boundary, which is why so many other operations behave differently depending on which key is in use.
Create Project Creates a project with its own API key, suppression list, and sending settings. One per environment or per customer keeps a mistake in one from spending or damaging another.
Update Project Changes a project's settings, including its monthly email counter limit and whether sending is enabled at all. Disabling sending stops every message on that project immediately, which is the fastest way to halt a runaway workflow.
Delete Project Removes a project. Its API key stops working immediately and its suppression list goes with it, which is why this operation sits behind the human gate above.
List Tags Returns the tags used on the account with the identifiers the event dump filters refer to. Tags are created implicitly by using them, so this is the only place to see the whole set.
Delete Tag Removes a tag from the account. Messages already sent keep what was recorded against them; this only stops the tag being offered and reported on.

System

Get System Info Returns account and system information for the key in use, including which project it belongs to. Used to confirm a key points where a workflow expects before it starts sending.
Ping Checks that the API is reachable and the key is accepted without touching any data. The right thing to put in front of a workflow that is about to do something expensive.

Frequently Asked Questions

What can FlowRunner do with UniOne?

FlowRunner agents can run Send Email, Send Subscribe Confirmation, and Validate Email in UniOne, plus 33 more actions.

Does connecting UniOne to FlowRunner require OAuth?

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

Can UniOne trigger a FlowRunner workflow automatically?

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

Start building with UniOne

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us