Skip to main content
Automations replace prompt-only cron jobs with versioned workflows. Each workflow connects a trigger to reusable logic, data, AI, delay, connector, webhook, and notification components.

​
Build an automation

  1. Open Automations in Sontairo AI.
  2. Create an automation and add components from the canvas toolbar.
  3. Connect each component’s success, error, true, or false output to the next step.
  4. Configure every required field in the properties panel.
  5. Select Check setup.
  6. Resolve every setup question, permission, connector, and schedule issue.
  7. Select Activate.
Activation publishes an immutable version. Later edits remain a draft until you select Publish changes, so an in-progress edit cannot alter a running workflow.

​
Unattended AI

AI components are deliberately non-interactive:
  • They cannot ask the user a question during a run.
  • They cannot discover or call tools.
  • Their instructions and output format are fixed at setup.
  • Side effects must use explicit connector, webhook, or notification components.
This keeps decisions visible in the graph and ensures missing information is resolved before activation.

​
Schedule examples

Schedule triggers use five-field cron syntax plus an IANA timezone. Check setup previews the next run times in that timezone. Schedules must be at least five minutes apart.

​
Reliability and run history

Cloudflare Workflows persists each component as a durable step. Components can retry with exponential backoff, delays do not hold a Worker open, and each run stores per-component status, duration, and encrypted inputs and outputs. Repeated failures automatically pause an automation after its configured retry threshold. Use the run history to inspect the exact component that failed, then update and publish a new version.

​
Existing cron jobs

Existing cron jobs are migrated to a three-component workflow: Schedule → AI task → Notification Migrated workflows start as paused drafts. Review the explicit AI and action components, run Check setup, and activate them once before they resume. The old row is retained only for audit and rollback and cannot double-fire.