FunnelKit Automations

New in 3.19.0 (Pro). Two dispatcher tools drive FunnelKit Automations (formerly Autonami) through its own REST controllers:

Tool	Default	Purpose
funnelkit-automations-read	On	Automations and stats, contacts, tags, lists, fields, audiences, broadcasts, templates, form feeds, link triggers, carts, email reports, allowlisted settings
funnelkit-automations-write	Off	Create and change all of the above, send broadcasts

FunnelKit Automations must be active and the connected user needs manage_options. Broadcasts, templates, form feeds, link triggers, audiences and bulk actions need Automations Pro.

Automations

1. list-events and list-actions show what can start an automation and what a step can do.
2. create-automation with a title. It starts off.
3. update-automation with the event (for example wc_new_order) and its settings, in the shape get-automation returns.
4. add-step per step (wait, action, conditional, split), then update-step with the step’s data and the flow (steps, links, count).
5. toggle-automation with state: 1 turns it on. Undo turns it off again; messages it sent meanwhile are not recalled.

Contacts, tags and lists

• list-contacts answers compact rows: id, email, tags and lists. Use get-contact for one contact in full.
• create-contact never creates a WordPress user.
• Tags and lists are assigned by existing ID. Create them first with create-tags (one request per name) or create-list, then assign-tags or assign-lists. Adding a tag or list can start automations that listen for it.

Broadcasts

1. create-broadcast (draft), then update-broadcast with step 1 (details), 2 (audience) and 3 (content and sender).
2. send-broadcast with dry_run: true reports how many contacts would receive it.
3. Only after the site owner agrees, send-broadcast (or schedule-broadcast) with confirm: true.

Safety and undo

• Anything that deletes or sends needs confirm: true; creates and updates accept dry_run: true.
• Every write is recorded in EMCP Tools → History. Not undoable, and recorded with the reason: sending or scheduling broadcasts and test emails, putting contacts into an automation or taking them out, deleting automations (their contact runs go with them) or a step, deleting contacts, unsubscribing and resubscribing, deleting fields and field groups, and contact exports.
• API keys, connectors, licences and plugin installs are never reachable. Settings changes go through a short allowlist (sender, reply-to, unsubscribe and consent texts, cart tracking) and other keys are refused.
• Contact exports (export-contacts, get-contact-export) need confirm and return the CSV inline, up to 2 MB.

Not available over MCP: importing a recipe and importing contacts from CSV. Use the FunnelKit admin for those.

In the admin

The FunnelKit Automations card sits under EMCP Tools → Tools → Plugins, in the E-Commerce group. Both tools are Pro; the write tool starts disabled. While FunnelKit Automations is not active, the card carries a Needs FunnelKit Automations badge.