Mautic
Manage Mautic contacts, segments, companies, campaigns and email sends.
About
Mautic ships in the w6w first-party pack. It declares 28 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.mautic- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Marketing · Email · Customer Relationship Management
Overview
Mautic is self-hosted open-source marketing automation, and this app puts the daily loop of running one — contacts, segments, companies, campaigns, tags and email sends — behind a workflow, whichever instance an organisation happens to run.
Contact management is the core of it: create and edit contacts, adjust their lead score, add or remove them from the Do Not Contact list per channel, and move them between segments and campaigns without touching Mautic’s UI. Companies round out the picture with the same add/remove-contact primitives, and a segment or a specific email can be triggered to send from a workflow step — the same send Mautic’s own campaign builder would fire, available as an action.
Deleting a contact is here as well, deliberately made harder to trigger by accident than everything else, because a self-hosted instance has no trash to recover it from. Administrative surfaces — the campaign builder itself, forms, landing pages, dynamic content, themes, plugins and Mautic’s own user management — stay out of scope in favor of the actions a marketing workflow touches day to day.
Build with Mautic
Three routes to the same 28 actions. The Workflow tab is generated from Mautic's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Add a contact to Do Not Contact
contact-dnc-add Suppress a contact on a channel — unsubscribe, bounce or a manual entry.
Remove a contact from Do Not Contact
contact-dnc-remove Re-enable a channel for a contact that was previously suppressed.
Subtract points from a contact
contact-points-subtract Decrease a contact's lead score by a fixed amount.
Send an email to its segments
email-send-to-segment Send an email to the contacts in its assigned segments, or to specific segment IDs.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Mautic's real ids.
{
"manifestVersion": "2",
"name": "mautic-example",
"steps": [
{
"id": "campaign-contact-add",
"uses": {
"app": "io.w6w.mautic",
"action": "campaign-contact-add",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"campaignId": "<campaignId>",
"contactId": "<contactId>"
}
}
]
}Here are some of the things you can do
-
Add a contact to a campaign
performcampaign-contact-add -
Get a campaign
readcampaign-get -
List campaigns
readcampaign-list -
Add a contact to a company
performcompany-contact-add -
Create a company
performcompany-create
+23 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Mautic, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Mautic. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "campaign-contact-add",
payload: {
campaignId: "<value>",
contactId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action campaign-contact-add --payload '{"campaignId":"<value>","contactId":"<value>"}'Give an AI agent Mautic — without giving it Mautic's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.mautic#campaign-contact-add",
"input": {
"campaignId": "<campaignId>",
"contactId": "<contactId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Mautic connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Mautic's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Mautic itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Mautic declares its own checks, so its health is a property of the app rather than something the host guesses at.
Mautic instance reachable
This connection's own server, probed unsigned against /api/contacts. A structured Mautic auth-error body proves the REST API is enabled and answering — no credential is sent, so an expired API Credential must not make the server look down.