Automations

Read the institute's automations (workflows): event-driven or scheduled flows of nodes (QUERY, SEND_EMAIL, SEND_WHATSAPP, DELAY, CONDITION, ...) that message learners, leads and staff. Pick an `action`:
- list (status?, search?, limit?): every automation with its trigger or schedule, status, last/next run.
- get (workflow_id): one automation as builder JSON — nodes with their config, edges, trigger, schedule — plus a one-line step summary.
- runs (workflow_id?, execution_id?, limit?): recent executions; with execution_id, that run's per-node log (status, timing, error). A run marked COMPLETED can still contain FAILED nodes — read the node log before saying it worked.
- catalog (section?): the authoring contract the builder enforces. `overview` (default) has the workflow JSON shape and the hard generation rules; `node_types` each node's config; `queries` prebuilt query keys with their output keys and item field names; `triggers` the common trigger events and every #ctx key each event provides; `trigger_events` the full event list; `query_keys` every query's parameter contract; `all` everything.
- context (kind?, search?): the REAL ids to reference — batches (package_session_id), audiences (lead campaigns), templates (ACTIVE email + APPROVED WhatsApp, with their placeholders; WhatsApp templates still DRAFT/PENDING/REJECTED are listed separately and cannot be sent yet), live_sessions, invites. Never invent an id or a template name: take them from here.
- template (channel, name): one template in full — an email's subject and HTML, or a WhatsApp template's body, header, footer, buttons, sample values, status and rejection reason. Read it before reusing a template or writing templateVars for it.
To build an automation: read catalog(overview) and the sections you need, fetch context for the ids and templates, create any missing template with workflows_edit(create_email_template | create_whatsapp_template), compose the workflow JSON, then use workflows_edit(validate) until it is clean and workflows_edit(create_draft) to save it as a draft the admin publishes.

Create and edit DRAFT automations (workflows). Nothing here ever runs or goes live: every action saves status=DRAFT, and a draft fires only after the admin reviews it in the builder and presses Publish. Pick an `action`:
- validate (workflow): normalise + lint + run the backend validator on a workflow JSON you composed. Saves nothing. Returns errors (must fix) and warnings (tell the admin).
- create_draft (workflow): validate, then save as a new DRAFT. Returns the id and editor_url the admin reviews and publishes at. Refused while errors remain.
- update_draft (workflow_id, workflow): replace a DRAFT automation's definition. Refused for ACTIVE/INACTIVE automations — published ones are edited in the dashboard.
- discard_draft (workflow_id): remove a DRAFT automation (the undo for create_draft). Refused for anything that is not a DRAFT.
- create_email_template (name, subject, html, placeholder_labels?): a NEW email template a SEND_EMAIL node can reference by name. Write {{placeholders}} in the subject/html for per-recipient values; the placeholder list is derived for you and becomes the node's templateVars keys. Plain {{var}} substitution only — no conditionals or loops. Names must be unique; existing templates are never changed (they may be in use by live automations).
- create_whatsapp_template (name, body, category?, language?, sample_values?, variable_names?, header_text?, footer_text?, buttons?, submit?): a NEW WhatsApp template. Meta rules: name is lowercase letters/digits/underscores; variables are {{1}}, {{2}}, ... in order; the body cannot start or end with a variable; one sample value per variable; body <= 1024 chars; category UTILITY (transactional: confirmations, reminders, credentials — default) or MARKETING (promotions; Meta rate-limits repeats to one number). It is submitted to Meta (status PENDING) unless submit=false; approval usually takes minutes to hours — the automation can be drafted now but the admin should publish after it is APPROVED.
- sync_whatsapp_templates: pull the latest template statuses from Meta (use it to check whether a PENDING template got APPROVED, or to see templates made in Meta Business Manager).
`workflow` follows workflows(catalog) → workflowJsonShape: {name, description, workflow_type EVENT_DRIVEN|SCHEDULED, trigger{trigger_event_name, event_applied_type, event_ids[], idempotency_generation_setting} | schedule{schedule_type CRON, cron_expression, timezone}, nodes[{id, name, node_type, config, is_start_node}], edges[{source_node_id, target_node_id, label?, condition?}]}. Wire the flow with edges (routing is derived from them): a CONDITION node's true branch is the edge carrying `condition`, its false branch the edge labelled 'false'. Use only ids and template names returned by workflows(context). Obey every rule in catalog.generationRules; the same rules are linted here.