Workflows

Triggers you can use

Pick a trigger that matches how users interact with your UI or how you want time-based jobs to run. Chat triggers power embedded assistants that call the same action model as traditional automations.

• form_submit — bind to a generated form id.
• button_click — bind to actionable controls.
• page_load — run when a route renders.
• cron — scheduled execution with platform quotas.
• chat_message — conversational flows with LLM actions and optional human handoff patterns.

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.
• redirect — send users to another route after server-side logic.

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.