Automations

Tools in the automations scope, callable over space-mcp (tools/call) or space-api (REST) with a wks_live_* key that grants automations.

create_automation

Scope: automations:write

Create a new automation (starts DISABLED with a 'manual' trigger). Returns { automation_id }. Then call set_automation_trigger to choose what fires it, set_automation_actions to add the steps, and finally update_automation with enabled:true to turn it on. Reuse an existing automation (list_automations) before creating a duplicate. To only be TOLD when something happens (no steps to run), use listen_to_events instead; to send events to another system, create_event_webhook.

create_event_feed

Scope: automations:write

Keep this space's events of the types you name so another system can PULL them (space-api GET /events, or get_events) instead of receiving a webhook.

create_event_webhook

Scope: automations:write

Send this space's events to another system: every event of the types you name is POSTed to an https url, signed (Wakato-Signature header, HMAC-SHA256), retried when it fails. The signing secret is in the answer ONCE — hand it to whoever runs the receiving end. filters narrow per type with the automation trigger's own config. For yourself, use listen_to_events instead.

delete_automation

Scope: automations:write

Permanently delete an automation and all of its action steps and run history (cascades). Cannot be undone.

delete_event_webhook

Scope: automations:write

Delete a webhook or a feed for good.

get_automation

Scope: automations:read

Get one automation's full state: its trigger (type + config), its ordered action steps (with branching), the merge-tag fields available from the trigger, and handy space resource ids (forms, phone numbers, agents with a Reach, email addresses) for wiring config. Use before editing an existing automation.

get_automation_run

Scope: automations:read

Full detail for one automation run: per-action results (action_type, label, status, error message, structured failure details, output, duration) plus the trigger data the run saw. Everything needed to diagnose a failing step and fix its config with set_automation_actions.

get_events

Scope: automations:read

Read what happened in this space, oldest first, after a cursor: events the space keeps (14 days) because some listener, webhook or feed wants their type. Pass the answer's next_cursor as after next time. types narrows; listener_id reads one feed (its types and filters).

list_automation_action_catalog

Scope: automations:read

List every valid automation trigger type and action type, each with its required/optional config fields and the merge-tag fields a trigger exposes. CALL THIS FIRST before building or editing an automation so you use only valid trigger_type / action_type values and supply the right config keys.

list_automation_runs

Scope: automations:read

Run history: list past automation runs (newest first) with status, duration, action/failure counts, and the first error message per run. Filter by automation_id and/or status (running|waiting|completed|partial|failed). Use this to check whether an automation has been working in the wild, then drill into a run with get_automation_run.

list_automations

Scope: automations:read

List space automations.

list_event_types

Scope: automations:read

Every event you can be told about in this space (a new order, a booking, a form reply, a contact created, an agent finishing a task…) with its label and group. Pass type to get one in full with the fields its data carries, or group (e.g. Commerce, Forms, Contacts) to narrow.

list_event_webhook_deliveries

Scope: automations:read

A webhook's delivery log, newest first: which event, delivered or failed, the receiver's HTTP status and error, attempts, when it retries next.

list_event_webhooks

Scope: automations:read

The space's outgoing webhooks and feeds: url, events, on/off (and why it was switched off), deliveries in the last 24 hours. Agents' own listeners are not here.

list_my_listeners

Scope: automations:read

What you are listening to in this space: each listener's events, filters, delivery, whether it is on, and how many events reached you in the last 24 hours.

listen_to_events

Scope: automations:write

Hear about events in this space (a new order, a booking, a form…) — they arrive in your chat. Name the event types (list_event_types), or ["*"] for everything. delivery 'now' = one line per event as it happens; 'batch' = one line every batch_minutes gathering what happened. filters narrow per type with the automation trigger's own config (e.g. { "commerce_order_paid": { "product_id": "…" } }). Only for yourself; to send events to another system, use create_event_webhook.

run_automation

Scope: automations:run

Run a space automation NOW and get the full result back synchronously: run_id, status (completed/partial/failed/waiting), and per-action results with any errors — so you can test an automation, see exactly which step failed and why, fix its config, and run it again. Works on disabled automations too (build disabled → test → enable is the safe workflow). Pass payload to simulate the trigger's merge fields (e.g. {email, name, phone} for a contact trigger). Requires automations.run scope. NOTE: actions really execute — emails/SMS actually send; use a test recipient in the payload.

set_automation_actions

Scope: automations:write

Replace an automation's action steps with the supplied ordered list (full replace, not append). Each action: { temp_id (unique, e.g. 'a1'), action_type (valid type from list_automation_action_catalog), config (object with that action's required fields), enabled? }. Branching: a 'condition' action can have children — give the child parent_temp_id (the condition's temp_id, which must appear earlier) and branch_label ('true' or 'false'). Merge tags like {{field_key}} reference trigger fields or earlier action outputs.

set_automation_trigger

Scope: automations:write

Set what fires an automation. trigger_type must be a valid type from list_automation_action_catalog (e.g. form_submission, contact_created, scheduled, webhook, manual). Pass trigger_config with the type's required fields (e.g. { form_id } for form_submission). Scheduled triggers require a 5-field cron_expression like '0 9 * * *'. Webhook triggers auto-generate a slug. Replaces the existing trigger.

stop_listening

Scope: automations:write

Stop one of your listeners for good (list_my_listeners shows them). To pause instead, update_my_listener with enabled:false.

test_event_webhook

Scope: automations:write

Send a webhook a signed test event now and answer whether the receiver took it (its HTTP status or the error). Nothing is stored or retried.

update_automation

Scope: automations:write

Update an automation's name, description, and/or enabled state. Pass enabled:true to turn an automation ON (or false to pause it). At least one of name/description/enabled is required.

update_event_webhook

Scope: automations:write

Change a webhook or a feed: its events, filters, name, url (webhook), or switch it off/on (enabled — switching on clears a failure stop).

update_my_listener

Scope: automations:write

Change one of your listeners: its events, filters, delivery ('now' | 'batch'), batch_minutes, name, or switch it off/on (enabled).