Skip to main content

​
What is this?

These tools let the assistant read your automations and their runs, build a new one from a description (saved as an inactive draft), replace a draft’s flow, turn automations on or off, and start one for a customer. These tools belong to the Workspace MCP. Each tool below shows its Mode (Read runs immediately; Write asks your MCP client to confirm first) and the Permission needed for it to appear for your key — “None” means every connected key sees it.

​
What can I do here?

  • See which automations exist, what they do and whether they ran
  • Build an automation from a description as an inactive draft
  • Turn an automation on or off, or start one for a customer

​
Tools

​
list_automations

List automations (chatbot flows) in the user’s current channel, newest first. Use to answer questions like which automations exist, which are active, or how often they ran. Mode: Read · Permission needed: automations:view

​
create_automation

Build an automation (chatbot flow) from a description and save it as a DRAFT: it is created INACTIVE and does not run until it is activated with activate_automation. Give the channelType (default WhatsApp), the trigger (a keyword, a new conversation, or a contact field change) and the steps as a flat list. Each step goes on to the next one in the list unless it points elsewhere by step id (give the target steps an id), so branches can go as deep as needed and can loop or jump. Steps: send_text, send_buttons, send_list, send_media, send_cta, send_contact, send_location, send_template (approved templates only), send_flow, ask_question (text, number, email, phone, date, location, address, image, video, audio, file; with max attempts, an invalid-answer message, a deadline, and separate answered / not-answered paths), add_label / remove_label, set_field, create_note, wait, assign_team_member, resolve_conversation, condition, branch (several values), working_hours, jump_to, switch_automation, http_request and ai_reply. The flow is checked with the same rules the dashboard flow builder applies, so it opens there without errors. Not covered: payments, product and catalog steps, carousels, Google Sheets / Calendar, Shopify / WooCommerce, sequences; build those in the dashboard. Use list_automations first so you do not duplicate one, list_labels, list_team_members and list_templates for names. Write the messages from what the user told you; do not invent offers, prices or policies. If the user has not said what the flow should do, ask before proposing. Mode: Write · Permission needed: automations:create

​
update_automation

Replace the flow of an automation that is OFF with a new description (same shape as create_automation: name, trigger and the complete list of steps). It REPLACES the whole flow, so read the current one with get_automation first and send everything you want to keep. An automation that is on must be turned off first (pause_automation), and one with runs in progress is refused. Only flows made of the supported steps can be described (see create_automation); for anything else use the dashboard flow builder. Mode: Write · Permission needed: automations:edit

​
activate_automation

Turn an automation ON (automationId from list_automations). It then runs for real customers, so use it only when the user has asked for it. It checks the flow is valid first. Suggest reviewing the flow in the dashboard before activating a new draft. Mode: Write · Permission needed: automations:edit

​
pause_automation

Turn an automation OFF so it stops starting for new customers (automationId from list_automations). Runs already in progress are not deleted. Mode: Write · Permission needed: automations:edit

​
get_automation

Get one automation from the user’s current channel by id: its trigger, status, and the ordered list of steps it contains. Get the id from list_automations first — never guess it. Mode: Read · Permission needed: automations:view

​
list_automation_building_blocks

List the step types an automation can use on a given channel type (messages, questions, logic, actions, integrations), with what each does. Use to answer whether an automation can do something — never claim a capability that is not listed. Mode: Read · Permission needed: automations:view

​
list_automation_runs

Recent runs of the channel’s automations, newest first: which automation, for which contact, status (running, completed, failed), error and timing. Filter by automationId or status. Use it for “did my automation run?” or “why did it fail?”, then get_automation_run for the step-by-step log. Mode: Read · Permission needed: automations:view

​
get_automation_run

One automation run (from list_automation_runs) with its step log: each step’s type, status and error. Mode: Read · Permission needed: automations:view

​
trigger_automation

Start one of this channel’s active automations for the customer of a conversation. Get the id from list_automations. Mode: Write · Permission needed: inbox:send

​
Troubleshooting / Technical Notes

  • A tool I expect isn’t offered. The MCP server only offers tools whose required permission your API key’s owner holds, re-checked on every call. Grant the permission shown on the tool — see Team.
  • A Write tool never seems to run. Your MCP client asks you to approve every Write tool call. Check for a pending approval prompt.
  • A call returns an error. See MCP errors.
Last modified on October 29, 2026