Maileon

Maileon is the email marketing and automation platform from XQueue. Agents manage contacts, fields, filters, and target groups, build and send mailings, schedule dispatchings and quality checks, maintain blocklists, and push transactions and data extensions.

159 actions Basic auth available

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

A regular mailing is prepared for release from the content system

Set Mailing Content writes the subject, the HTML, and the preview text onto the mailing

Count Active Contacts By Filter ID reports how many of the target group can actually be sent to

Start Quality Check runs the spam, link, image, and personalization checks

Get Quality Check Result reads the findings once the checks have completed

The sendable count, the gap against the plain count, and the findings go to the mailing owner

The owner approves before Create Mailing Schedule is called, because content cannot change after

What This Integration Enables

Maileon is XQueue's email marketing and automation platform, and it models consent with more precision than most senders. Permission is a level rather than a boolean, and it only ever strengthens: a weaker permission written over a contact who already holds double opt in is discarded. The unsubscription marker is a separate record from the permission value, so a contact can look subscribed and still be marked. Unsubscription reasons arrive through their own operation, because in practice the reason is collected on a page shown after the opt out has already been recorded. Preferences are grouped into categories so a person can leave one topic without leaving everything. Deleting a contact is explicitly not unsubscribing, since the address can be re-imported and mailed the next day. None of that is decoration. It is what a European sender needs when someone asks what you were permitted to send and when.

FlowRunner agents work all of it: contacts and their fields and preferences, contact filters and the target groups built on them, mailings and their content, settings, attachments, schedules, dispatchings and quality checks, blocklists at both scopes, transactions, data extensions, reports, the media library, webhooks, and automation programs. The connector absorbs the platform's own conventions so a flow never handles them, parsing the XML into plain objects, turning the platform's explicit null into a real null so a flow can tell "never set" from "set to nothing", and normalizing single records into arrays so a one-element list does not change the shape of the answer. Where the platform hands an agent a switch with legal consequences, a human-in-the-loop step holds it.

Without FlowRunner

Audience size means the wrong thing The target group count is read as the reach, and it includes people who cannot lawfully be mailed

Consent stored as a single flag Permission, the unsubscription marker, and preference choices get flattened into subscribed or not

Pre-send checks run when someone remembers The spam score and the broken link are found by a recipient rather than by the check that exists for it

With FlowRunner

Sendable count separated from group size The number a person approves is the number of contacts the platform will actually deliver to

Consent read as the structure it is Permission level, marker, and per topic preference are handled as the three different records they are

Checks run as a step in the flow Quality checks start automatically and their findings reach a person before the schedule is set

Use Case Scenarios

A newsletter release that proves itself before it is scheduled

Approved content reaches the agent from the content system. It calls Create Mailing from the account defaults, writes the subject, HTML, and preview text with Set Mailing Content, and checks Is Mailing Sealed first, because a sealed mailing refuses content writes and that is the usual cause of an otherwise valid write being rejected. Refresh Contact Filter Contacts re-evaluates the audience, since filter membership is computed rather than stored and can be stale right after an import. Set Contact Filter Lock State then freezes the membership so the send reaches exactly the contacts selected at that moment. Start Quality Check runs the spam scoring, link validity, and personalization checks. Only when the findings have been read by a person does Create Mailing Schedule get called, and it is called last, because a content change after the schedule is set means the mailing does not go out at all.
Order confirmations driven by transactions rather than by exports

An order completes in Shopify and the agent records it with Create Transactions against a transaction type whose attributes the trigger mailing's template already references. Because a transaction cannot be delivered to a contact who does not exist, the agent runs Synchronize Contacts first with the full record rather than relying on the platform's on-the-fly creation, which stores only the address and the external identifier. It also turns off the ignore-invalid switch, because that switch defaults to dropping bad rows silently while still reporting success. Failures come back as a per contact validation report, which the agent posts to Slack with the offending attribute named.
A preference center that other systems can actually see

A customer updates their topic choices on the website. The agent writes them through the preference operations, which store each choice against a named preference inside a category rather than as a single subscribed flag. The same values are mirrored into the warehouse in Snowflake so the analytics team can segment on them, and into HubSpot so a salesperson can see what the customer asked to hear about before they call. When the customer opts out entirely, the agent uses the unsubscribe route rather than the delete route, and follows it with Add Unsubscription Reasons once the reason page has been submitted, because the reason cannot travel with the opt out itself.

Human-in-Loop Highlight

Set Mailing Setting carries a switch called ignore permission, and turning it on sends the mailing to contacts who never gave permission. Maileon does not hide what that means: it is only lawful for genuinely transactional content, and the platform has no way to judge whether your content qualifies. What makes this a good gate rather than a vague warning is that the agent can compute the exact population at stake. Count Contacts By Filter ID returns everyone the filter selects. Count Active Contacts By Filter ID returns only those the platform will actually deliver to. The difference between those two numbers is precisely the group that only an ignore-permission send would reach.

So when a flow is asked to send an operational notice through a marketing mailing, the agent works out the gap and stops. It posts: "Mailing Service Migration Notice is addressed to target group All Account Holders. The filter selects 61,400 contacts; 48,900 are sendable. Turning on ignore permission would additionally reach 12,500 contacts, of whom 3,100 carry a recorded unsubscription and 9,400 hold no permission at all. Send to the 48,900, or turn on ignore permission for all 61,400?" Legal or the marketing owner answers. Counting the gap is arithmetic and the agent owns it. Deciding that a message is transactional enough to reach people who said no is a legal judgment, and it belongs to a person who can defend it.

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

159 actions

Account

Ping Checks that the API key is accepted and the account is reachable. The verb is a parameter, because a key can be allowed one verb and refused another, so privileges can be tested one at a time.
Get Account Information Reads the account's own settings and identity, which is the quickest way to confirm which account a key belongs to. Used at the top of a flow that spans accounts.
Get Account Mailing Domains Lists the sending domains configured on the account. A mailing's sender address has to sit on one of these. Used as the first check when a send is refused for an unverified domain.
Get Account Placeholders Lists the account-wide placeholders that templates reference, typically the imprint lines and other text identical in every mailing. Used before changing any of them.
Set Account Placeholders Replaces the account's whole placeholder list with the one given, so a placeholder left out is removed. Used only for a deliberate full rewrite.
Add Or Update Account Placeholders Adds the placeholders that do not exist and updates the ones that do, leaving the rest untouched. This is the merging counterpart, and the right default for routine updates.
Remove Account Placeholder Removes one placeholder by name. Templates that still reference it render it empty rather than failing, so the templates are worth checking first.

Contacts

Get Contacts Reads a page of contacts. Standard and custom fields are omitted unless named, and preferences are omitted unless a category is named, so a bare read returns only identifiers and timestamps. Used for exports and reconciliation, always with the fields stated.
Get Contact By Email Reads the single contact holding an address. Used where the account is known to hold unique addresses.
Get Contacts By Email Reads every contact holding an address, as a list. Preferred where duplicates are possible, because the singular route hides the others.
Get Contacts By External ID Reads every contact carrying an external identifier. External identifiers are not enforced unique either, which is why this answers a list.
Get Contact By Maileon ID Reads one contact by its platform identifier, which is the only one guaranteed unique. Preferred whenever duplicates may exist.
Get Contacts By Filter ID Reads a page of the contacts a filter currently selects. Membership is evaluated rather than stored, so a refresh belongs first when the underlying data has just changed.
Get Blocked Contacts Reads the contacts the platform will not send to. Used when a mailing reached fewer people than the target group holds and the gap needs explaining.
Count Contacts Returns how many contacts the account holds. Used for capacity and reporting.
Count Contacts By Filter ID Returns how many contacts a filter selects, without reading them. Used to size an audience cheaply.
Count Active Contacts By Filter ID Returns how many of a filter's contacts are actually sendable, excluding those without permission and those who unsubscribed. This is the number that matters before a send, and the one a person should be shown.
Create Contact Creates a contact from its address, or updates it depending on the sync mode. The default mode ignores an existing contact, so calling this on a known address changes nothing unless the mode says otherwise. Permission is only the initial permission, and a weaker one is discarded against an existing double opt in. Used at signup.
Create Contact By External ID Creates or updates a contact keyed on your own identifier rather than the address. Answers a conflict when more than one contact carries that identifier, because it can no longer tell which is meant. Used where your system owns the key.
Update Contact By Email Updates a contact found by address. Writing an external identifier through this route can attach it to the wrong record, since the route does not identify contacts by that field. Used for address-keyed updates only.
Update Contact By External ID Updates a contact found by your own identifier, which is the right route when your system rather than the platform owns the key.
Update Contact By Maileon ID Updates a contact by its platform identifier. The safest of the three update routes, because that identifier is the only unique one.
Synchronize Contacts Updates a large set of contacts in one call and returns a per contact validation report. Duplicates within one call are ignored rather than refused. The ignore-invalid switch changes the failure mode: with it off, one bad contact fails the whole call. Used as the bulk path from a system of record.
Delete Contact By Email Deletes every contact holding an address. Deleting is not unsubscribing: the address can be added again and will receive mail. Used for genuine data errors, not for consent.
Delete Contact By External ID Deletes every contact carrying an external identifier. Records no opt out.
Delete Contact By Maileon ID Deletes exactly one contact by its platform identifier. Records no opt out.
Delete All Contacts Deletes every contact in the account, with no filter and no undo. The confirmation word is checked by the connector before the call is made, so a misconfigured flow cannot fire it by accident.
Unsubscribe Contact By Email Records an opt out for every contact holding an address, optionally with the reasons given. This is the route that honors consent.
Unsubscribe Contact By External ID Records an opt out for every contact carrying an external identifier, optionally with reasons.
Unsubscribe Contact By Maileon ID Records an opt out for exactly one contact, optionally with reasons. The precise route where duplicates exist.
Add Unsubscription Reasons Attaches reasons to a contact who has already unsubscribed. Exists because the reason is usually collected on a page shown after the opt out was recorded. Used to complete the consent record.
Get Unsubscription Marker Reads whether a contact carries the unsubscription marker, which is a separate record from the permission value. Used before any send decision on a previously suppressed contact.
Set Unsubscription Marker Sets the marker on a contact. Used to propagate a suppression recorded in another system.
Delete Unsubscription Marker Removes the marker. Removing it is not the same as regaining consent, so the permission value is what to check before mailing again.

Contact Fields and Preferences

Get Custom Fields Lists the account's custom contact fields with their data types. Field names are case sensitive throughout this API, so this is worth reading before writing to one.
Create Custom Field Creates a custom field with a name and a type. The type cannot be changed afterward and values must match it. Used when a new data point starts arriving.
Rename Custom Field Renames a field. Templates, contact filters, and transaction types referencing the old name are not rewritten, so a search comes first.
Delete Custom Field Deletes a field and every value stored in it across all contacts. Used in cleanup after confirming nothing references it.
Delete Custom Field Values Clears a custom field's value on every contact while keeping the field itself. Used to reset a derived attribute before a recalculation.
Delete Standard Field Values Clears a standard field's value on every contact. Standard fields cannot be deleted, only emptied.
Get Preference Categories Lists the preference categories, the groupings that hold the individual opt-in choices a contact can make. Used to build a preference center.
Get Preference Category Reads one category by name. Used before changing it.
Create Preference Category Creates a category. Preferences live inside one, so this comes first. Used when a new topic family is introduced.
Update Preference Category Renames a category or changes its description. Used for taxonomy maintenance.
Delete Preference Category Deletes a category together with the preferences inside it, and contacts lose the choices recorded against them. Used in cleanup, with the consequences understood.
Get Category Preferences Lists the preferences defined inside one category. Used to render a preference center from the platform's own definitions.
Get Preference Reads one preference inside a category. Used before changing it.
Create Preference Creates a preference inside a category, which contacts can then carry a value for. Used when a new topic is added.
Update Preference Renames a preference or changes its description. Used for maintenance.
Delete Preference Deletes a preference and the choices contacts recorded against it. Used in cleanup.

Contact Filters and Target Groups

Get Contact Filters Lists the account's contact filters, the saved rule sets that select contacts. Usually the first thing to read when preparing a send.
Count Contact Filters Returns how many filters the account holds. Used in audits.
Get Contact Filter Reads one filter with its properties. Used before editing or before building a target group on it.
Create Contact Filter Creates a filter from a rule definition, optionally creating a target group on it in the same call. The rule definition is a nested document with its own schema, passed through unchanged. Used to provision audiences programmatically.
Update Contact Filter Updates a filter's own properties, such as its name. Used for maintenance.
Delete Contact Filter Deletes a filter. A target group built on it is left behind and stops selecting anyone, so the target groups are worth checking first.
Refresh Contact Filter Contacts Re-evaluates which contacts a filter selects. Membership is not recomputed on every read, so this runs first when the underlying data has just changed.
Get Contact Filter Lock State Reads whether a filter's result set is locked. A locked filter keeps the membership it had at the moment of locking. Used to confirm reproducibility before a send.
Set Contact Filter Lock State Locks or unlocks a filter's result set, which is how a send is kept to exactly the contacts selected at that moment. Used immediately before a scheduled send.
Get Target Groups Lists the account's target groups with their contact counts and evaluation state. A target group is what a mailing is actually sent to.
Count Target Groups Returns how many target groups the account holds. Used in audits.
Get Target Group Reads one target group. Its state says whether the membership is current or has not been re-evaluated since its filter's data changed.
Create Target Group Creates a target group on top of an existing filter. The name must be unique and within the platform's own character rules. The permanent type is always included in a send, and the approval type is used by approval workflows.
Update Target Group Changes a target group's name, type, or underlying filter. Used when an audience definition moves.
Delete Target Group Deletes a target group, leaving the contact filter it was built on in place. Used in cleanup.

Mailings

Create Mailing Creates a mailing and returns its identifier, starting from the account's defaults for template, target group, and sender, with the optional parameters overriding them so a whole mailing can be prepared in one call. Used at the head of any content-driven send.
Copy Mailing Copies a mailing with its content and settings. Used to make a proven mailing the starting point for the next one.
Delete Mailing Deletes a mailing. A sent mailing carries its reporting with it, so deleting one removes the history a report was drawing on. Used in cleanup, after any export.
Get Mailing ID By Name Finds a mailing's identifier from its name. Used when a flow was configured with the name a person gave rather than a number.
Get Mailings Lists mailings, narrowed by state, type, keywords, subject, creator, or schedule window. Only identifiers come back unless the fields are named, and leaving the trash filter empty returns both live and trashed mailings. Used for discovery and reporting.
Get Mailing State Reads a mailing's state through its whole lifecycle, from draft to sending to archived. This is what to poll after a send starts.
Get Mailing Type Reads whether a mailing is regular, a double opt-in mailing, or a trigger mailing. The type decides which of the scheduling operations apply. Used before any scheduling work.
Is Mailing Sealed Reads whether a mailing is sealed. A sealed mailing refuses content and attachment changes, which is the usual reason an otherwise valid write is rejected. Used as the first check before any content write.
Get Mailing Name Reads a mailing's name. Used for reporting and for confirming the right mailing is in hand.
Set Mailing Name Renames a mailing, with the name staying unique in the account. Used when a flow generates names from a naming convention.
Get Mailing Content Reads one piece of a mailing's content: subject, HTML, plain text, sender address, sender alias, recipient alias, or preview text. Used to inspect what will go out.
Set Mailing Content Writes one piece of a mailing's content. A sealed mailing refuses it, and changing content after a schedule has been set means the mailing will not be sent, so the schedule is always called last. Used to render content from a system of record into the mailing.
Get Mailing Setting Reads one of a mailing's settings, from locale and speed level through to tracking strategy, archival duration, the ignore-permission and cleanup switches, the reply-to address, and the platform-reported size limits. Used before a send and before an attachment upload.
Set Mailing Setting Writes one of a mailing's settings. The platform-reported size limits are read only and the connector refuses them locally rather than sending a call the vendor ignores. Turning on the ignore-permission switch sends the mailing to contacts who have not given permission, which is only lawful for genuinely transactional content.
Get Mailing Target Group ID Reads the target group a regular mailing is addressed to. Used to confirm the audience before approval.
Set Mailing Target Group ID Points a regular mailing at a target group. Only regular mailings have one; a trigger mailing selects recipients through its dispatching instead.
Get Mailing Template Reads which template a mailing is built on. Used in audits of what design a send used.
Set Mailing Template Points a mailing at a template, replacing its content structure. A content reset follows if the mailing should also take the template's default content.
Reset Mailing Contents Puts a mailing's content back to what its template defines, discarding everything written since. Used deliberately, when a mailing needs to start over.
Get Mailing Preview Renders a mailing as it would reach a recipient. Giving a contact matters: without one the preview falls back to the account's default personalization contact and hides exactly the personalization errors you are looking for.
Get Mailing Archive URL Reads the public web archive URL, the link that shows the message in a browser. Used in social posts and support replies.
Get Mailing Report URL Reads the URL of a mailing's report inside the platform. Used to link a person straight to the numbers from an approval message.
Get Mailing Thumbnail URL Reads the URL of a mailing's rendered thumbnail, which is what to embed in an approval message or a dashboard.
Get Mailing Domain Reads which of the account's sending domains a mailing will go out on. Used as a pre-send guard.

Sending, Scheduling and Checks

Send Mailing Now Sends the mailing immediately to its target group. There is no confirmation step and no undo. The mailing state is what to poll afterward to follow the send.
Send Test Mail Sends one test copy to an address. If the address is not a contact, the message is personalized from the account's default personalization contact, so a test can look correct while the real send fails on missing data. Used as the proof step, with a real contact given.
Get Mailing Schedule Reads a regular mailing's schedule: when it goes out and how the dispatch is spread over time. Used to confirm what is queued.
Create Mailing Schedule Schedules a regular mailing, which means it will be sent. This is called last, because changing content after the schedule is set means the mailing will not go out. The dispatch options spread the send over a window rather than firing it all at once.
Update Mailing Schedule Changes an existing schedule. The same warning applies: any content change after this point means the mailing will not be sent.
Delete Mailing Schedule Removes a schedule, which stops the mailing from being sent. Used as the stop lever between scheduling and sending.
Get Mailing Dispatching Reads a trigger mailing's plan: what starts it, how often it runs, and who it selects. Used to audit an automated send.
Create Mailing Dispatching Sets a trigger mailing's plan, which has to exist before the trigger can be activated. Single sends the moment a transaction event arrives; the interval form draws recipients from an event, a filter, or a feed. Trigger mailings only.
Delete Mailing Dispatching Removes a trigger mailing's plan, which stops it firing. Used to retire an automated send.
Start Quality Check Starts one of the platform's pre-send checks: spam scoring, link validity, image availability, message size, personalization, bounce simulation, an approval sendout, or a test sendout. Checks run asynchronously. Used as a standing step before any release.
Get Quality Check Result Reads the outcome of a quality check. A check never run and a check that found nothing look similar, so the check is started first and given time. Used to put findings in front of a person before the schedule is set.
Disable Quality Checks Turns the platform's pre-send checks off for a mailing, which removes the net that catches broken links, missing personalization, and oversized messages. Used rarely, and never as a way past a failing check.

Attachments

Get Mailing Attachments Lists a mailing's attachments with names, types, and sizes. Used before adding or replacing one.
Count Mailing Attachments Returns how many attachments a mailing carries, against the platform's limit of ten. Used as a guard before an upload.
Get Mailing Attachment Reads one attachment's metadata. Used in audits.
Add Mailing Attachment Attaches a file to a mailing. The mailing must not be sealed, the total must stay within the platform's limit, the file must fit the account's maximum attachment size, and the MIME type is given explicitly rather than guessed from the filename.
Copy Mailing Attachments Copies every attachment from one mailing to another, which saves re-uploading them when a mailing was built by hand. Used in recurring-send flows.
Delete Mailing Attachment Removes one attachment from a mailing. Used for corrections.
Delete Mailing Attachments Removes every attachment from a mailing at once. Used when a mailing is being rebuilt.

Mailing Properties and Content Automation

Get Mailing Properties Lists a mailing's custom properties, the key and value pairs a flow can attach to carry its own bookkeeping alongside the platform's. Used to link a mailing back to the record that produced it.
Add Mailing Property Adds a custom property to a mailing. Used to stamp a mailing with its source ticket, campaign code, or approval reference.
Update Mailing Property Changes the value of a custom property. Used to advance a mailing's own workflow state.
Remove Mailing Property Removes a custom property from a mailing. Used in cleanup.
Enable Target Group Update Tells a mailing to re-evaluate its target group just before sending, so a filter whose membership has moved since preparation is picked up. Used for sends prepared well in advance.
Fill RSS Smart Mailing Tags Pulls a feed's current items into a mailing's smart tags, which is how a feed-driven newsletter gets its content filled in before it goes out. Used in recurring content sends.

Blocklists

Get Mailing Blocklists Lists the account's mailing blocklists. A mailing blocklist holds address expressions a mailing must not reach, and it applies per mailing rather than account wide.
Get Mailing Blocklist Reads one mailing blocklist. Used before editing it.
Create Mailing Blocklist Creates a mailing blocklist, which then has to be attached to a mailing before it does anything. Used to provision exclusions for a campaign.
Update Mailing Blocklist Renames a mailing blocklist. Used for maintenance.
Delete Mailing Blocklist Deletes a mailing blocklist, and mailings it was attached to stop excluding its expressions. Used in cleanup, with the attachments checked first.
Get Mailing Blocklist Expressions Lists the expressions a blocklist holds, which may be whole addresses or wildcards on either side of the at sign. Used to audit what a campaign is excluding.
Add Mailing Blocklist Expressions Adds expressions to a mailing blocklist. A wildcard on the domain side excludes a whole company, so the blast radius is worth stating before it is applied.
Get Blocklists For Mailing Lists the blocklists attached to one mailing. Used as a pre-send check on what will be excluded.
Add Blocklist To Mailing Attaches a blocklist to a mailing so its expressions are excluded from that send. Used when a campaign must avoid a named set of recipients.
Remove Blocklist From Mailing Detaches a blocklist from a mailing, leaving the blocklist itself in place. Used when an exclusion no longer applies.
Get Account Blocklists Lists the account-wide blocklists, which apply everywhere rather than to one mailing. Used in compliance audits.
Get Account Blocklist Reads one account-wide blocklist with its entries. Used before adding to it.
Add Account Blocklist Entries Adds addresses or wildcard expressions to an account-wide blocklist. The import name is shown in the platform only and is not returned by any read, so it cannot be used to find these entries again. Used for permanent, account-level suppression.

Transactions

Get Transaction Types Lists the account's transaction types, the schemas describing what a transactional event carries. A transaction cannot be created until its type exists.
Count Transaction Types Returns how many transaction types the account holds. Used in audits.
Get Transaction Type Reads one type with its attribute definitions, which is what to check when a transaction is rejected for a bad value.
Create Transaction Type Creates a type and its attributes, within the platform's own naming rules. The store-only option raises the string limit sharply but makes the attributes unusable in contact filters, which is a permanent trade for that type.
Update Transaction Type Changes a type's description, archiving duration, or attribute list. Removing an attribute a trigger mailing's template references leaves that mailing unable to render.
Delete Transaction Type Deletes a type together with its stored events, and trigger mailings driven by it stop firing. Used in cleanup, with the dependent mailings retired first.
Create Transactions Records transactional events, which is what drives trigger mailings such as an order confirmation. The contact must already exist for the message to be delivered. The ignore-invalid switch defaults to dropping bad rows silently while still reporting success, so it is turned off where the rows matter.
Get Transaction Reads one recorded transaction by its type and identifier. Used for support and audit.
Delete Transaction Deletes one recorded transaction. Used for corrections.
Delete Transactions Before Date Deletes recorded transactions older than a date, optionally limited to one type. Reporting that drew on those events, and links in mailings that rendered from them, stop working once they are gone.

Data Extensions

Get Data Extension Data Types Lists the types a data extension field can take, which is the platform's own list rather than a general one. Used before designing an extension.
Get Data Extension Reads an extension's definition: its fields, their types, and its retention policy. Used before writing to it.
Create Data Extension Creates a data extension, a table of your own data that mailings and contact filters can draw on. At least one field must be marked as a unique identifier. The retention policy decides when rows disappear. Used to bring product, loyalty, or entitlement data into reach of a mailing.
Update Data Extension Changes an extension's own settings, such as its name, description, or retention policy. Used for maintenance.
Delete Data Extension Deletes an extension and every record in it. Used in cleanup, after confirming no mailing or filter draws on it.
Get Data Extension Records Reads a page of an extension's records. Used for reconciliation against the source system.
Manage Data Extension Records Inserts, updates, upserts, or deletes records in one call. The payload is column oriented: the column names travel once and each record is a values array in the same order, so the connector refuses a record whose value count does not match rather than letting values land in the wrong columns. The answer carries its own success flag alongside the affected and skipped counts, so the report is what to read rather than the status.
Delete Data Extension Records Removes every record from an extension while leaving the extension itself in place. Used before a full reload.

Reports

Get Mailing Summaries Reads the headline numbers for one or more mailings in a single call: recipients, opens, clicks, bounces, unsubscriptions, and replies, with the unique counts alongside the totals. The cheapest way to compare mailings.
Get Report Events Reads a page of recipient-level events of one kind, covering opens, clicks, bounces, blocks, conversions, recipients, replies, unsubscriptions, subscribers, and filtered contacts. Dates travel as millisecond timestamps, anonymous events are excluded unless asked for, and contact fields are only returned when named.
Count Report Events Returns how many events of one kind match a filter, without reading them. The same date and anonymous-exclusion rules apply, so a count and a page length can disagree if the filters differ.
Get Unsubscription Reasons Reads the reasons recipients gave when they opted out, which is the report that turns an opt-out number into something actionable.
Get Conversion Revenue Reads the revenue recorded against conversions, so a campaign can be measured in money rather than in clicks.

Media and Templates

Get Media Articles Lists the articles in the account's media library, the reusable content blocks mailings pull from. Used to assemble a mailing from approved components.
Get Media Article Reads one media article's metadata. The identifier is not numeric, which matters when a flow stores it. Used before referencing a block in content.
Get Mailing Templates Lists the templates available to the account, which is where a template identifier for mailing creation comes from. Used when provisioning mailings programmatically.

Webhooks and Automation

Get Webhooks Lists the account's webhooks with the event each listens for and the fields it forwards. Used to audit what is subscribed.
Get Webhook Reads one webhook. Used to verify configuration during a deployment.
Create Webhook Creates a webhook so the platform calls a URL of yours when an event happens. Custom contact fields are not yet handled properly on this path, so the payload is built from standard and event fields. The contact field change event fires only on a profile update link, so it is not a general change feed.
Update Webhook Replaces a webhook's URL, event, and field selection. This is a replacement rather than a merge, so an empty field list clears the fields the callback used to carry.
Delete Webhook Deletes a webhook so the callback stops. Used in cleanup.
Start Marketing Automation Program Starts an automation program for a set of contacts. Each contact must already exist and hold a permission other than none, and the program itself must be active. Used to enroll a cohort from an event that happened outside the platform.

Frequently Asked Questions

What can FlowRunner do with Maileon?

FlowRunner agents can run Ping, Get Account Information, and Get Account Mailing Domains in Maileon, plus 156 more actions.

Does connecting Maileon to FlowRunner require OAuth?

No. Maileon connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Maileon trigger a FlowRunner workflow automatically?

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

Start building with Maileon

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us