Workflows

Workflows automate reactions to user activity: submitting a form, clicking a button, loading a page, cron schedules, chat messages, inbound webhooks, or Stripe events.

Triggers you can use

Pick a trigger that matches how users interact with your UI, how external services notify you, or how you want time-based jobs to run.

  • form_submit — bind to a generated form id.
  • button_click — bind to actionable controls.
  • cron — scheduled execution with platform quotas.
  • chat_message — conversational flows with LLM actions and optional human handoff patterns.
  • webhook — receive HTTP POSTs from external services (Shopify, Zapier, custom backends, etc.). A unique URL is auto-generated per workflow; optional HMAC-SHA256 signature verification.
  • stripe_event — react to Stripe webhook events on your connected account (payment_intent.succeeded, invoice.paid, etc.).

Core actions

Actions compose linearly. Combine data loading, transformation, notifications, and AI steps without deploying your own servers.

  • save_record — persist payloads to a record type.
  • send_email — uses project email templates with merge context.
  • http_request — integrate external APIs.
  • fetch_data — pull from your record store or HTTP endpoints.
  • llm_chat / send_reply — power chat experiences.

Node output variables

Every action node stores its result so downstream nodes can reference it via {{nodes.<node_id>.<field>}}. For example, an http_request node with id 'fetch_order' stores its response body as {{nodes.fetch_order.body}}, making it available in subsequent send_email or save_record nodes.

  • {{nodes.<id>.body}} — response body (HTTP response, LLM text, etc.).
  • {{nodes.<id>.success}} — boolean success flag.
  • {{nodes.<id>.status_code}} — HTTP status code.
  • {{nodes.<id>.record_id}} — saved record ID (save_record).
  • {{nodes.<id>.data}} — structured data from the action.

Draft, publish, and test

Edit workflows in draft, validate with the in-app testing panel (including chat test UI for chat_message), then publish so live traffic executes the new graph. Execution history lists successes, failures, and diagnostics.

Plan limits

Free tier enables workflows but only basic actions (e.g. save_record, send_email) and does not include monthly execution quota for full automation. Starter and above unlock the full action library with generous monthly run allowances; Pro and Business raise limits further.

Info:
Workflow runs are billed in small credit increments per execution in addition to monthly quotas—see Subscriptions & credits.