mail2many
Email Marketingmail2many is a German email marketing platform by Atrivio. Agents manage subscribers, groups, and customer fields, set up and send trigger mailings, publish articles and channels, and read tracking data.
What This Integration Enables
mail2many, by Atrivio, is a German platform whose API is shaped around two ideas that are unusual enough to determine how you build on it. The first is that a subscriber's state is a pair of fields rather than one, and only certain combinations exist: ready to receive carries no qualifier at all, not ready to receive carries pending confirmation or no opt-in or transactional, and archived carries unsubscribed or hard bounced or manual. The platform rejects anything else, and the connector checks the pairing before the request leaves so a flow fails naming the field it got wrong. The second is that a mailing is assembled rather than declared: you open a draft, add its receivers in batches, and then schedule it, and only that last call commits anything.
Around those sits a content surface most platforms in this category do not have. Articles are published into channels, and newsletters draw from them, so the same content can reach the mailing and the website without being pasted twice. FlowRunner agents manage subscribers and groups across six different write routes with genuinely different behaviors, publish articles, assemble and send trigger mailings, and poll the tracking feed for opens and clicks, which is the substitute for the webhooks this platform does not publish. The commit at the end of that sequence waits for a person, and that is FlowRunner's human-in-the-loop default rather than a setting.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Choosing the right one of six subscriber writes
Six routes on this connector create or update subscribers, and they fail in different directions. One errors on an address that already exists; another ignores it silently. One errors on a new address; another ignores it silently. Upsert Subscribers is the route that neither errors nor skips, which is why a warehouse sync out of PostgreSQL uses it and a nightly job does not have to reconcile two failure modes. Register Subscriber is the one a sign-up form calls, because it handles the confirmation mail as well as the record. The agent picks per flow rather than picking once, and the choice is visible in the workflow instead of buried in a field.
-
The newsletter assembled from published content
Content is written in WordPress and the agent publishes it into the channel with Create Article, updating it with Update Article when an editor revises it before send day. Get Channels resolves which channel the newsletter belongs to. Create Trigger Mailing opens the draft, Add Trigger Mailing Receivers loads the audience across as many calls as the volume requires, and Get Trigger Mailing reports the state. Nothing has gone anywhere yet. The audience count and the article list post to Slack for review, and the send is committed afterward.
-
Reporting polled rather than pushed
This platform publishes no webhook surface, which the connector establishes rather than assumes, so engagement arrives by polling. On a schedule the agent calls Get Trackings, which carries opens, clicks, the subscriber, the newsletter, the device, and the reference the flow set when it created the mailing, so each row ties back to a record on your side without a lookup table. Get Newsletter Statistics supplies the aggregate and Get Newsletter Subscribers supplies the audience. The whole picture lands in Google Sheets next to the previous week's, and Get Opt-Outs is read alongside it so the list a campaign is measured against is the list it was actually allowed to reach.
Human-in-Loop Highlight
Schedule Trigger Mailing is irreversible in the way that matters: aborting afterward stops what has not gone yet and cannot unsend what has. What makes it a gate rather than just a big red button is that the agent cannot fully verify the thing it is about to commit. Receivers are added a hundred at a time across many calls, and a batch that partly failed still answers successfully with its rejections reported as a counter rather than as a list of names. So the agent's belief about who is on this mailing is arithmetic, not a readback, and the platform does not offer one.
That is exactly the shape of thing a person should see before it goes out. The agent reports the arithmetic honestly instead of rounding it off: "Trigger mailing ready for Thursday 08:00 UTC. Intended audience 24,500. Receivers accepted across 245 calls: 24,338. 162 rejected, and the platform reports the count but not which addresses. Scheduling commits the send and aborting afterward cannot unsend what has already left. Send to the 24,338, or investigate the shortfall first?" A marketer decides whether 162 unexplained rejections matter for this particular mailing. For a weekly newsletter, usually not. For a legally required notice, always. Only a person knows which one this is.
Agent Capabilities
40 actionsAccount and Reference Data
4- Get Account Reads the account a key is bound to. A key belongs to exactly one, so this is the cheapest confirmation that a flow is pointed where it thinks it is.
- Get Channels Returns the channels on the account, which is what articles are published into and what newsletters draw from.
- Get Opt-In Types Returns the opt-in types the account supports.
- Get Trigger Types Returns the trigger types available to a trigger mailing.
Customer Fields
3- Get Customer Fields Returns the field definitions, keyed by numeric identifier, which is what subscriber payloads have to use rather than the display name. Two separate numberings share the answer: what a field is attached to, and what it holds.
- Set Customer Field Default Sets the default value on one account-level field. Anything that is not an account field is skipped silently and still answers successfully, so a flow checks the field type first.
- Set Customer Field Defaults Applies the same treatment to several fields in one call.
Subscriber Groups
5- Get Subscriber Groups Returns the groups on the account.
- Get Subscriber Group Reads one group and its membership.
- Create Subscriber Group Creates a group.
- Update Subscriber Group Changes a group's membership, and two flags decide how: adding the named subscribers, removing them, or replacing the entire membership with only those named. The connector refuses a replace with an empty selection, because that is a legitimate request and an easy accident.
- Delete Subscriber Group Removes a group from the account.
Subscribers
14- Get Subscribers Returns subscribers with paging and, where the platform supports it, filtering passed through as given.
- Get Subscriber Reads one subscriber in full.
- Get Subscriber By Parameter Finds a subscriber by a parameter other than the identifier, which is how a record is resolved from your own key rather than theirs.
- Get Parameter Data Reads the parameter values held against subscribers.
- Get Opt-Outs Returns recorded opt-outs, and is the one route whose filter syntax the vendor actually documents.
- Create Subscriber Creates one subscriber. An address that already exists is an error rather than an update.
- Register Subscriber Creates or updates a subscriber and sends the confirmation mail where one is owed. The route a sign-up form should call.
- Update Subscriber Updates one subscriber. An address that does not exist is an error rather than a creation.
- Delete Subscriber Deletes one subscriber, or archives them instead if they have ever received a newsletter. The response says which happened, so the flow reads it rather than assuming.
- Delete Subscribers Applies the same treatment to a set, with the same split between deletion and archiving.
- Archive Subscribers Archives subscribers explicitly. With no channels named it archives them in every channel they belong to, so the flow names them.
- Create Subscribers Creates a batch. Addresses that already exist are ignored silently rather than reported.
- Update Subscribers Updates a batch. Addresses that do not exist are ignored silently rather than reported.
- Upsert Subscribers Creates or updates a batch. The only subscriber write that neither errors nor skips, which is what makes it the default for a scheduled sync.
Mailings and Trigger Mailings
9- Get Mailings Returns the mailings configured on the account.
- Get Sent Mailings Returns the mailings that have gone out.
- Create Trigger Mailing Opens a draft mailing. Creating one sends nothing, which is what makes the sequence safe to assemble in a workflow.
- Get Trigger Mailing Reads a draft's state and its receiver counts.
- Add Trigger Mailing Receivers Adds receivers to a draft, in batches of the size the platform accepts. A partly rejected batch still answers successfully and reports its rejections as a count rather than as names.
- Schedule Trigger Mailing Commits the mailing to send at a UTC moment. The irreversible step in the sequence, and the operation this page's human gate exists for.
- Abort Trigger Mailing Stops the remainder of a send. What it leaves behind depends on timing, and it cannot unsend anything already delivered.
- Send Trigger Mail Sends one message immediately, skipping the assembly sequence. Returns no message identifier, so the send can only be traced afterward through the tracking feed.
- Send Trigger Mails Sends a batch immediately, reporting sent and unsent counts. A partly rejected batch still answers successfully, so the flow reads the counters.
Articles
2- Create Article Publishes a content block into a channel, which newsletters then draw from.
- Update Article Revises a published article, so the mailing and the site carry the same version.
Reporting
3- Get Newsletter Subscribers Returns the audience a newsletter reached.
- Get Newsletter Statistics Returns aggregate results for a newsletter.
- Get Trackings Returns opens and clicks with the subscriber, the newsletter, the device, and the reference the flow set when the mailing was created. The polling substitute for the webhooks this platform does not publish.
Frequently Asked Questions
What can FlowRunner do with mail2many?
FlowRunner agents can run Get Account, Get Channels, and Get Opt-In Types in mail2many, plus 37 more actions.
Does connecting mail2many to FlowRunner require OAuth?
No. mail2many connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can mail2many trigger a FlowRunner workflow automatically?
mail2many doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Email Marketing integrations
Start building with mail2many
Free plan, no card required. Connect in minutes.