Mailvio

Mailvio is an email marketing and deliverability platform whose own control panel runs on its API. Agents manage subscribers, groups, tags and custom fields, build and send campaigns, run deliverability tests, send transactional mail, and react to webhook events.

1 trigger 89 actions API key available

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

A client's monthly campaign is approved in the delivery board

Switch Account Master points the connection at that client's account master

Get Account Masters confirms which account the token is now reading and writing

Count Campaign Recipients resolves how many subscribers the campaign would reach

Check Campaign Sending Limit confirms the plan allows a send of that size

Content Check Template runs the spam and content check over the creative

The account name, the recipient count, and the check result go to the delivery lead

The delivery lead confirms which client account is about to send before Start Campaign runs

What This Integration Enables

Mailvio's own control panel is built on this API, which is a more useful fact than it sounds. It means an agent is not working a reduced integration surface bolted onto the side of the product. It is working the same surface the staff use, including the parts a marketing platform usually keeps for itself: the account users and their roles, the API keys and their write permissions, the segment preview that evaluates a query before it is saved, the content check that scores a template for spam signals, and the inbox placement test that puts the creative in front of seed mailboxes and reports where it landed. Deliverability is treated here as something you do before a send rather than something you read about afterward.

The second thing that shapes work on this connector is the account master. One signed-in user can belong to several of them, and a token points at exactly one at a time. Switching moves the token, and every later call in the flow then reads and writes that account. For an agency running client programs under one login, that is both the reason Mailvio works and the thing to be careful about, because the write target is a piece of state rather than a parameter. FlowRunner agents make it explicit, naming the account they switched to before anything consequential happens, and holding the send itself behind a human-in-the-loop step.

Without FlowRunner

The active client account is implicit Whoever logged in last decides which account the next action lands in

Deliverability checked after the fact The spam score and the inbox placement get looked at once the numbers come back bad

Send limits discovered at send time A campaign over the plan's allowance fails when it starts, not when it was planned

With FlowRunner

The active account stated out loud The flow names the account master it switched to, and a person confirms it before the send

Deliverability checked before the send The content check and the placement test run as steps, not as a post mortem

Allowance confirmed while it still matters The plan check runs during assembly, so a shortfall is a scheduling question rather than a failure

Use Case Scenarios

A client campaign assembled end to end, then held

A campaign brief moves to Ready in ClickUp. The agent switches the token to that client's account master, creates the campaign with Create Campaign from the approved template, and builds the audience out of include-and-exclude pairs so that the newsletter group goes out minus the recent-purchasers segment. Count Campaign Recipients resolves the number, Check Campaign Sending Limit confirms the plan covers it, and Content Check Template scores the creative. All of it posts to the delivery lead in Slack with the client's account name in the first line. Start Campaign is the only step that waits.
Store behavior that reaches Mailvio without a nightly export

An order completes in Shopify. The agent calls Add Subscriber against the customer group, writing custom field values keyed on the merge tags the client's templates already use. Set Subscriber Tags then replaces the subscriber's tag set with the recalculated one, which is why the agent reads the current tags first and sends the complete intended set rather than the additions. For a customer who was browsing before they bought, Send Site Tracking Event attaches the session to the contact, using the identifier the client's own tracking script generated rather than one the agent invented.
A junk complaint that becomes a standing check

After each send, the agent reads Get Campaign Junk Reports alongside the opens and clicks, because a complaint rate is what damages a sending reputation while an open rate only describes it. Where complaints cross the agency's internal threshold, the agent pauses the next scheduled campaign for that client with Cancel Campaign, exports the campaign statistics through Start Campaign Statistics Export, and files a summary in Asana for the account team. The pattern that produced the complaints, usually an audience built without the exclusion, is named in the ticket rather than left for someone to find.

Human-in-Loop Highlight

Start Campaign is the operation with the shortest window and the widest blast radius, and the account master model is what makes it dangerous rather than merely consequential. The token points at one account master at a time. A flow that switched masters partway through, or that resumed after a wait during which another branch switched it, will start the campaign in whichever account the token is pointing at now. Cancel Campaign only stops a campaign that has not started. Once sending has begun the lever is Pause Campaign, which stops what has not gone out and does nothing at all about the messages already delivered to the wrong client's list.

So the send agent states the target and stops. It posts: "Ready to start Spring Promo. Token is currently on account master Northfield Retail, switched at 09:14. Audience resolves to 22,480 recipients: Newsletter group minus the Recent Buyers segment. Sending limit check passed. Content check flagged two spam signals in the subject line, listed below. Start in Northfield Retail?" The delivery lead confirms the account, not just the campaign. Building the audience, resolving the exclusions, and scoring the creative are all things an agent should do unattended. Naming which client is about to receive twenty-two thousand emails is a decision with a person's name on it.

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

89 actions

Account and Users

Get Account Reads the account master the token currently points at, with its name, address, and billing details. Used to confirm the active account before anything is written.
Update Account Changes the account master's name and postal details. Used when a client's registered details change and the footer has to follow.
Get Account Usage Reads sending usage against the plan. Used before a large campaign, and as the input to a capacity report across client accounts.
Get Account Masters Lists every account master the signed-in user belongs to. A token points at one of them at a time. Used to enumerate client accounts and to confirm which one a switch landed on.
Switch Account Master Points the token at a different account master, after which every later call reads and writes that account. Used at the top of any client-scoped flow, and always named explicitly in what the flow reports.
Get Account Users Lists the people who can sign in to this account master, with their roles. Used for access reviews.
Get Account User Reads one account user's profile and preferences. Used to check a role before changing it.
Create Account User Invites a person into the account master. Omitting the role adds them as a standard user, which is the platform's default rather than the least privileged option. Used in onboarding flows, with the role always stated.
Update Account User Changes an account user's profile and interface preferences. Used for routine account maintenance.
Set Account User Role Changes an account user's role, which is what controls what they may do in the platform. Used when someone's responsibilities change, and a good candidate for an approval step.
Delete Account User Removes a person's access to the account master. Their subscribers and campaigns stay; only the login goes. Used in offboarding.

API Keys

Get API Keys Lists the account's API keys with their names, write permission, and expiry. Used for periodic credential audits.
Create API Key Creates an API key and returns it. The write permission decides whether the key may change anything, and a read-only key is the safer default for a flow that only reports. Used when provisioning a new integration.
Update API Key Changes a key's name, whether it is enabled, whether it may write, and when it expires. Disabling is how access is revoked without deleting the key. Used for incident response and rotation.
Delete API Key Deletes an API key, after which anything using it stops working immediately. Used in cleanup after a rotation has been confirmed.

Groups

Get Groups Lists the account's subscriber groups with their default sender details. Used for discovery at the start of a client flow.
Count Groups Returns how many groups the account holds. Used in reporting and in health checks across accounts.
Get Group Reads one group with its defaults and notification settings. Used before a send to confirm the sender identity attached to the audience.
Create Group Creates a subscriber group. The public flag decides whether other users of the account can see it at all, so a private group needs an explicit shared-users list. The signup reminder text is what subscribers are shown to remind them where they signed up, which is worth filling in for deliverability. Used when provisioning a new audience.
Update Group Changes a group's name and defaults. Leaving a notification address empty means leave it alone; clearing one requires sending an explicit blank. Used for routine maintenance.
Delete Group Deletes a group. Subscribers who belong to other groups survive; the membership is what goes. Used in cleanup after a program ends.

Subscribers

Get Subscribers Reads the account's subscribers across every group. Used for exports and reconciliation.
Count Subscribers Returns how many subscribers the account holds, optionally narrowed by the same search the read takes. Used to size an audience cheaply before pulling it.
Get Subscriber Reads one subscriber with their custom field values and status flags. Used before any conditional write and for support lookups.
Get Subscriber Statistics Reads one subscriber's engagement history: what they were sent, opened, and clicked. Used when a person asks why they received something.
Download Subscriber Data Returns everything held about one subscriber, which is the operation for a data access request. Used in privacy workflows.
Get Group Subscribers Reads the subscribers in one group. Used to build and verify an audience.
Add Subscriber Adds a subscriber to a group, or updates the existing one with that address. Custom field values may be keyed by merge tag or by numeric ID. Blacklisting an address here stops it being sent to anywhere in the account rather than only in this group. Used for signup and purchase flows.
Update Subscriber Changes one subscriber's address, status flags, or custom field values. Used to write behavior from other systems back onto the record.
Bulk Upsert Subscribers Adds or updates many subscribers in one call, which is the route for an import rather than looping the single-record operation. Used for periodic synchronization.
Change Subscriber Status In Group Moves subscribers in one group to a new status: active, inactive, unsubscribed, bounce, or blacklisted. Used for group-scoped lifecycle changes.
Bulk Change Subscriber Status Moves subscribers to a new status across the whole account rather than within one group, and accepts only three of the five statuses. Used for account-wide hygiene actions such as marking a bounce cohort.
Unsubscribe Subscriber Unsubscribes an address and blacklists it, which blocks it account wide rather than removing it from one group. Used to honor an opt out, and never as a way to tidy a single group.
Copy Subscribers To Group Copies subscribers into another group, or moves them when the move switch is on. The source filter narrows which of the selected subscribers actually travel by their status, so a copy scoped to active silently leaves the unsubscribed ones behind. Used for audience restructuring.
Remove Subscribers From Group Removes subscribers from one group. The all switch removes every subscriber in the group and ignores the IDs given, which is how a group is emptied. It is also the only route that can clear the account-wide blacklist flag. Used for group cleanup, and for reinstating an address that was blacklisted in error.
Delete Subscribers Deletes subscribers from the whole account rather than from one group. Used for erasure requests.

Tags and Custom Fields

Get Tags Lists the account's tags. Used to resolve identifiers before an audience is built.
Create Tag Creates a tag for assigning to subscribers. Used when a new segmentation dimension is introduced.
Update Tag Renames a tag. Subscribers carrying it keep it. Used for taxonomy maintenance.
Delete Tag Deletes a tag and removes it from every subscriber carrying it. Used in cleanup, after checking which audiences depend on it.
Set Subscriber Tags Replaces a subscriber's tags with the set given, so a tag left out is removed. The subscriber may be addressed by email rather than by ID. Used for lifecycle stage synchronization, always with the complete intended set.
Get Custom Fields Lists the account's custom fields with their merge tags and types. Used before writing custom field values.
Create Custom Field Creates a custom field, where the field name becomes the merge tag used in email content and the description is what people see in the interface. Used when a new data point starts arriving from the client's systems.
Update Custom Field Changes a custom field. Renaming it changes the merge tag, so content using the old tag stops resolving. Used with care, and usually alongside a content audit.
Delete Custom Field Deletes a custom field and the values stored in it. Used in cleanup after confirming no template references the merge tag.

Campaigns

Get Campaigns Lists the account's campaigns. Used for discovery and reporting.
Get Campaign Reads one campaign with its content, sender details, and audience. Used to inspect what is about to send.
Get Recent Campaign Statistics Reads the headline numbers for recent campaigns in one call, which is the cheapest way to build a dashboard. Used for weekly reporting across client accounts.
Count Campaign Recipients Returns how many subscribers a campaign would reach given its groups and segments. Used before starting one, and as the number a person is shown at the approval step.
Check Campaign Sending Limit Reports whether the plan allows this campaign to be sent. A campaign over the allowance fails at send time rather than at creation, so this runs during assembly. Used as a pre-send guard.
Create Campaign Creates a campaign. It does not send. Groups and segments are include-or-exclude pairs, which is how an audience is built by subtraction. The resend-after option re-sends the campaign to everyone who did not open it a set number of days later, which is a second send nobody explicitly triggers. Used to assemble a campaign from content that lives elsewhere.
Update Campaign Changes a campaign. The batch size, delay, and unit together throttle the send, and a batch size set without a delay does nothing useful. Used for corrections before the send starts.
Copy Campaign Copies a campaign. Without a name given, the copy carries the original name with a suffix appended, which is easy to leave in place by accident. Used to build a recurring send from last month's.
Start Campaign Starts a campaign, which sends it. An optional start date overrides whatever schedule the campaign carries. Used as the send step, and the operation this connector holds behind an approval.
Cancel Campaign Cancels a scheduled campaign so it never starts. This is not the same as pausing one already going out. Used as the stop lever between scheduling and sending.
Pause Campaign Stops a campaign that is currently sending. Messages already delivered stay delivered. Used when a problem is spotted mid-send.
Resume Campaign Restarts a paused campaign, which resumes sending to the recipients it had not reached. Used after the reason for the pause has been resolved.
Delete Campaign Deletes a campaign, and its statistics go with it. Used in cleanup, after any report that depends on those numbers has been exported.

Statistics

Get Campaign Statistics Reads a campaign's headline numbers. Used for the standard post-send summary.
Get Campaign Recipients Lists who a campaign was sent to. Used for audits and for answering client questions about reach.
Get Campaign Opens Lists who opened a campaign. Used to build engaged-audience follow-ups.
Get Campaign Clicks Reads which links in a campaign were clicked, and how often. Used to judge which call to action carried the message.
Get Campaign Junk Reports Lists the recipients who marked a campaign as junk. This is the number that damages a sending reputation, so it is the one to watch above the rest. Used as a standing check after every send.
Start Campaign Statistics Export Starts an export of a campaign's statistics and returns a job to poll. Used to move results into a warehouse or a client report.
Get Campaign Statistics Export Reads an export job and its file once ready. Used to complete the export path.

Segments

Get Segments Lists the account's saved segments. Used for discovery when building an audience.
Get Segment Results Reads the subscribers a saved segment currently selects. Used to verify an audience before a send.
Preview Segment Evaluates a query without saving it, which is how a segment is checked before it is created. Used to iterate on audience logic safely.
Create Segment Creates a segment from a query. A temporary segment does not appear in the interface and exists only to scope one campaign, so it cannot be found or reused afterward. Used to build audiences from criteria held in another system.
Update Segment Replaces a segment's name and query. The query is not merged, so the segment is read first when only one condition is changing. Used to keep an audience definition current.
Delete Segment Deletes a segment. Campaigns that referenced it lose that part of their audience. Used in cleanup, with the references checked first.

Templates and Deliverability

Create Template Creates an email template. The editor choice is durable: a template created for the code editor cannot be edited in the drag and drop one. Used to publish a design system's output into the platform.
Update Template Changes a template. The drag and drop editor keeps its own representation alongside the HTML, and changing one without the other leaves them out of step until the editor overwrites your changes. Used for content maintenance, with both kept in sync.
Content Check Template Runs a spam and content check over a template. Used before a campaign is built on it, which is the point at which the result can still change what gets sent.
Start Inbox Test Runs an inbox placement test, which sends the campaign's content to seed mailboxes. Used as the deliverability proof step ahead of a large send.
Get Inbox Test Results Reads where an inbox placement test's messages landed, per provider. Used to decide whether a send goes ahead as built.

Transactional and Tracking

Send Transactional Email Sends one email immediately, or at a given date. The reply address domain must be authenticated on the platform or belong to a free provider. The send fails if the recipient is unsubscribed, blacklisted, or has hard bounced before, which is the opposite of how transactional behaves elsewhere and means an operational message needs a fallback path for suppressed addresses. Used for receipts, notices, and account mail.
Send Site Tracking Event Records a website visit or a custom event against a contact, feeding site tracking from your own back end. The identifier has to be one the platform's client-side script generated. Supplying an address for an unknown contact creates one. Used to join server-side behavior to the email profile.

Reports and Exports

Create Report Starts building a report and returns a job to poll. Used for scheduled client reporting.
Get Report Reads a report job and how far along it is. Used to poll rather than guess.
Get Report File Returns a finished report's file. Asking before the job completes returns nothing useful rather than waiting. Used to deliver the finished artifact.
Start Subscriber Export Starts exporting subscribers and returns a job to poll. A group and a segment cannot both be given, and leaving the status empty exports every status including blacklisted addresses. Used for migrations and audits.
Get Subscriber Export Reads a subscriber export job and how far along it is. Used to poll the export.
Get Subscriber Export File Returns a finished subscriber export's file. Used to move the result into storage or a warehouse.

Webhooks

Get Webhooks Lists the account's webhooks with the event each one listens for. Used to audit what is subscribed.
Get Webhook Reads one webhook. Used to verify configuration during a deployment.
Create Webhook Registers a webhook so the platform calls a URL of yours when an event happens. A group filter narrows it to one group's subscribers; without it the webhook fires for the whole account. Used to drive systems that are not managed by this flow.
Update Webhook Changes a webhook's URL, event, or group. Used when the receiving endpoint changes.
Delete Webhook Deletes a webhook so the callback stops. Used in cleanup.

Triggers

1 triggers

Event Triggers

On Mailvio Event Fires when the chosen Mailvio event happens: a campaign send, open, click, unsubscribe, bounce, or junk report, or a subscriber being updated or deleted. Every payload carries the event type, the subscriber, the address, and the account master it belongs to, campaign events add the campaign identity, and a link click also carries the link that was followed. The trigger registers its webhook when the flow is enabled and removes it when the flow is disabled, so there is no orphaned callback left behind. Used to react to engagement the moment it happens: routing a click to the account team, opening a ticket on a junk report, or propagating an unsubscribe to the systems that do not learn about it any other way.

Frequently Asked Questions

What can FlowRunner do with Mailvio?

FlowRunner agents can run Get Account, Update Account, and Get Account Usage in Mailvio, plus 86 more actions.

Does connecting Mailvio to FlowRunner require OAuth?

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

Can Mailvio trigger a FlowRunner workflow automatically?

Yes. Mailvio supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Mailvio

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us