Automations

Connect a trigger to context, AI, logic, actions, and human checkpoints.

Create automations

An automation remains a draft until it is valid and published.

Build and publish a flow

  1. Open Automations and select New automation.
  2. Name the automation, add an optional description, and choose a Manual, Webhook, or Cron trigger.
  3. Add nodes to the canvas, configure each node in the inspector, and connect every required output to its next step.
  4. Resolve every item under Fix before publishing, then save and publish the definition.
  5. Turn the published automation on when its webhook or schedule should accept work. Manual automations can be started explicitly.

Choose flow nodes

  • Block adds custom content or a selected Library page to the working context.
  • Prompt sends the accumulated context and configured prompts to the selected AI model.
  • Decision compares templated values and selects a true, false, or failure branch.
  • Wait pauses a run for a configured number of minutes.
  • Machine runs a templated shell command in an isolated Linux machine.
  • Create block creates a new Inbox item or Library page from templated content.
  • Add to Library moves the incoming working block into the Library.
  • Edit and Approval pause the run for a person to respond in Inbox.
  • End stops that branch of the flow.

Run code in a Machine

  1. Add a Machine node and enter an optional reusable setup script and the command to run from /workspace.
  2. Use workflow variables when the command needs output from an earlier node.
  3. Choose compute, set a timeout, and allow all network access, deny network access, or allow only listed domains.
  4. Connect Next for success and Failure for a non-zero exit code or provider error, then publish the automation.
  5. Open the run trace after execution to inspect stdout, stderr, and the exit code.

Inspect and control runs

  1. Open Automations to see recent runs, or open a definition to see its ten most recent runs.
  2. Open a run to inspect its current status and execution history.
  3. Complete human requests from Inbox to resume a paused run.
  4. Cancel a run from its pending Inbox request when further work is no longer wanted.