Mail Komplet

Mail Komplet is a Czech email marketing and transactional platform. Agents manage mailing lists, recipients, and custom columns, run campaigns and distributions, send transactional email and SMS, and handle unsubscribes and sale coupons.

Verified 45 actions API key available

Mail Komplet website Platform Documentation Capability data verified 2026-08-19

An order ships from the warehouse

Agent reads the order, the recipient, and which brand the shipment belongs to

Get Business Units confirms the flow is writing to the mailing unit that brand actually uses

Create Recipient upserts the customer onto that unit's mailing list

Send Transactional Email delivers the dispatch notice and Send Transactional SMS carries the tracking number

Get Transactional Email Bounce Info resolves anything that failed rather than leaving it silent

Before a mailing list is deleted, a person confirms whether the recipients standing on it should survive it

What This Integration Enables

Mail Komplet organizes everything around the mailing unit. Every route carries the unit in its path, one FlowRunner connection is one unit, and an account that runs several of them has several. If your company sends under multiple brands or divisions and wants each one genuinely separated rather than separated by a naming convention, that structure is the reason to look here. It also carries both channels: transactional email and transactional SMS are peer operations on the same connector with the same recipient data behind them, so a dispatch notice and a tracking text are one workflow rather than two integrations.

FlowRunner agents manage mailing lists, recipients, and custom columns, run bulk imports and poll them, build campaigns and read their results through the dispatches those campaigns produce, send transactional email and SMS, maintain unsubscribes, and issue sale coupons. Consent scope is explicit on this platform in a way it usually is not: a campaign's unsubscribe setting decides whether an opt-out reaches that campaign, its lists, or the whole account, and the connector surfaces that as a choice the flow makes rather than a default it inherits. The writes that reach beyond what a flow can undo stop for a person, which is the human-in-the-loop default rather than an option somebody has to switch on.

Without FlowRunner

Brands share one pile Several divisions send from the same account, and a list belonging to one of them is one careless click from another

Email and SMS run separately The dispatch notice and the tracking text are sent by two different tools with two different records

Reports keyed to the wrong thing Someone asks for a campaign's opens and gets nothing back, because the report wants the dispatch

With FlowRunner

One connection, one mailing unit Each brand's automation writes to its own unit, and moving between them is deliberate

Both channels, one flow The notice and the text leave from the same step with the same recipient data behind them

Reports resolved through the dispatch The flow reads the distributions first and pulls results against those, so the numbers arrive

Use Case Scenarios

Shipment notices across two brands, kept apart

An order ships from Shopify under one brand and from PrestaShop under another. Each brand's flow holds its own connection and therefore its own mailing unit, so there is no path by which one brand's automation writes into the other's recipient database. Create Recipient upserts the customer, because an existing address is updated rather than rejected on this route. Send Transactional Email delivers the dispatch notice with the campaign identifier attached so the body does not have to be repeated on every send, and Send Transactional SMS carries the tracking number for the customers who chose that. Get Transactional Email Bounce Info resolves the failures the next morning rather than leaving them to be discovered later.
A campaign report that actually returns numbers

Marketing wants last month's results. The agent lists the campaigns, then calls List Distributions to get the individual dispatches, because on this platform every marketing report is keyed to a dispatch rather than to the campaign that produced it, and passing a campaign identifier to a report returns nothing useful. List Marketing Emails, List Marketing Email Opens, and List Marketing Email Clicks are pulled for each dispatch and appended to Google Sheets. Get Recipient Activity answers the individual questions that follow, one customer at a time, without anybody opening the platform.
A promotion with real coupon codes behind it

Ahead of a sale, the agent calls Create Coupon Group and then Create Coupons to load the batch, leaving validity unset for the codes that should not expire. The campaign is built with its unsubscribe scope chosen deliberately, because the widest setting means one click removes the person from everything the account sends, and its dispatcher named, since that is the verified sending domain. The audience size and the coupon count post to Slack before anything is committed. After the sale, List Coupons reports what was actually used, and Delete Coupon Group retires the batch under review rather than on a schedule.

Human-in-Loop Highlight

Delete Mailing Lists takes a flag whose two settings differ by one word in the documentation and by an entire recipient database in effect. Set one way, the lists are deleted and the people on them stay in the system. Set the other way, the lists are deleted and every recipient standing on them is deleted too. The connector makes that flag required and refuses to guess, which is the right engineering answer and still leaves somebody having to choose. Its smaller sibling behaves the same way: deleting recipients with a mailing list named removes them from that list, and deleting them without one removes them from the system entirely.

So the agent measures and asks. Before any list deletion it counts the members, checks how many of them appear on no other list in the unit, and posts: "Deleting Vánoce 2024 and Vánoce 2025. Together they hold 9,700 recipients, of whom 2,140 are on no other list in this unit. Keeping recipients removes the lists only. Removing recipients deletes those 2,140 from the database and they are not recoverable through the API. Which?" The list owner answers in one word, and the agent carries it out across both lists in one pass. The counting is the machine's job. Deciding that two thousand people should stop existing is not.

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

45 actions

Account and Mailing Units

Get Business Units Returns the other mailing units on the account. One connection addresses one unit, so this is how a flow discovers what else exists without being able to write to it.

Mailing Lists

List Mailing Lists Returns the unit's mailing lists. Passing a contact or campaign identifier does not filter the result; it annotates every row with availability instead.
Create Mailing List Creates a mailing list in this unit.
Update Mailing List Updates a list. A true partial update, so properties absent from the body are left alone.
Delete Mailing Lists Deletes one or more lists. A required flag decides whether the recipients standing on them survive or are deleted with them, and it is the operation this page's human gate exists for.

Recipients

List Recipients Returns recipients with paging. The email filter is a partial match, so a domain fragment returns everyone at that domain.
Create Recipient Creates a recipient, or updates one that already exists. An upsert rather than a rejection, which is what makes it safe in an order flow.
Update Recipient Updates a recipient's fields.
Delete Recipients Removes recipients. With a mailing list named it removes them from that list; without one it deletes them from the system.
Bulk Import Recipients Starts an asynchronous import and returns an operation identifier. Two required switches decide what happens to existing data and whether values are merged or overwritten, and the connector refuses to choose either.
Get Bulk Import Info Polls a bulk import to completion.
Get Recipient Activity Reads what one recipient has received, opened, and clicked. The operation that answers a support question directly.
Create Subscribe Request Starts a double opt-in for an address. Requires a dispatcher, which is why the sending domain list is a prerequisite for sign-up flows.

Campaigns and Distributions

List Campaigns Returns the unit's campaigns.
Get Campaign Reads one campaign's configuration.
Create Campaign Creates a campaign. Its unsubscribe scope is required and decides how far an opt-out reaches, up to and including everything the account sends.
Update Campaign Updates a campaign's settings.
Delete Campaign Removes a campaign from the unit.
List Templates Returns the templates available to campaigns.
List Dispatchers Returns the verified sending domains. Optional on a campaign and required on a sign-up request, so flows read it early.
List Distributions Returns the individual dispatches a campaign produced. Every marketing report is keyed to one of these rather than to the campaign, so this is the lookup that makes reporting work.

Marketing Reports

List Marketing Emails Lists the messages sent in one dispatch.
List Marketing Email Opens Lists open events for a dispatch.
List Marketing Email Clicks Lists click events for a dispatch.

Transactional Email

Send Transactional Email Sends a transactional message. Passing a campaign identifier lets a flow create the shell once and avoid repeating the whole body on every send, and per-recipient variables win over the shared set.
List Transactional Emails Lists transactional messages, with a partial-match email filter.
List Transactional Email Opens Lists opens on transactional mail.
List Transactional Email Clicks Lists clicks on transactional mail.
Get Transactional Email Bounce Info Returns why a transactional message failed, which is what turns a silent non-delivery into something a flow can act on.

Transactional SMS

Send Transactional SMS Sends a text message to one or more numbers. A peer of the email route rather than a separate product, so a notice and a tracking text come out of the same step.
List Transactional SMS Lists sent text messages with their outcomes.

Custom Columns

List Custom Columns Returns the unit's custom recipient fields.
Create Custom Column Defines a new custom field.
Update Custom Column Updates a custom field. A true partial update.
Delete Custom Column Removes a custom field. The connector calls the correct route and does not fall back to the one the vendor's documentation names, because that one deletes recipients.

Unsubscribes

List Unsubscribed Returns the recorded opt-outs for the unit.
Unsubscribe Recipient Records an opt-out. With no list and no campaign named it applies globally, which the flow states deliberately rather than reaching by omission.
Delete Unsubscribe Record Removes a recorded opt-out, which makes the person contactable again. Used for a correction rather than for cleanup, and always with evidence behind it.

Coupons

List Coupon Groups Returns the coupon groups defined in the unit.
Create Coupon Group Creates a group to hold a batch of codes.
Update Coupon Group Updates a group. It shares a route and a verb with creation, and including the identifier is what makes it an update.
Delete Coupon Group Removes a coupon group and the batch it holds.
List Coupons Returns the codes in a group and what has happened to them.
Create Coupons Loads codes into a group. A code with no validity date never expires.
Delete Coupon Removes a single code, which stops it working for anyone holding it.

Frequently Asked Questions

What can FlowRunner do with Mail Komplet?

FlowRunner agents can run Get Business Units, List Mailing Lists, and Create Mailing List in Mail Komplet, plus 42 more actions.

Does connecting Mail Komplet to FlowRunner require OAuth?

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

Can Mail Komplet trigger a FlowRunner workflow automatically?

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

Start building with Mail Komplet

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us