Turn backend scripts into workflows you can inspect.

Define webhook integrations, scheduled tasks, and multi-step processes in YAML. Your AI agent can draft and update the manifest, and you inspect each run and its step outputs.

Create a workflow ↗Read the workflow guide

Free to start, no card. Always-on hosting from $10/month.

IN PRACTICE

Publish a market brief every weekday morning.

A cron trigger runs at 8:00 on weekdays in your timezone, fetches prices, selects the JSON fields it needs, and posts the brief to your app. Each step is recorded in the run.

workflows/daily-brief.yaml

workflow_id: daily-market-brief
enabled: true

triggers:
  - type: cron
    cron: "0 13 * * 1-5"

steps:
  - step_id: fetch-prices
    kind: http
    command:
      method: GET
      url: https://api.example.com/quotes

  - step_id: publish-brief
    kind: http
    dependencies: [fetch-prices]
    command:
      method: POST
      url: https://dashboard.example.com/api/market-briefs

HOW IT WORKS

Describe the trigger and steps, then inspect every run.

Read the guide ↗

01
Write a workflow manifest, or ask the AI agent to draft one.
02
Add triggers and steps for HTTP calls, data selection, scripts, SQL, email, S3, AI agents, and approvals.
03
Push it with adios workflow push --create, start a run with adios workflow run, and check each step's status, output, and error.

WHY IT BELONGS HERE

Operational scripts become invisible until they fail.

Cron jobs, webhook transforms, approval steps, and maintenance tasks are often scattered across scripts and services with no shared run history.

Keep automation beside the app

Version triggers, shared context, secret references, and steps with the source they support.

Build from visible steps

Call HTTP services, parse requests, select JSON, run Bash or Python, query SQL, send email, use S3, run an AI agent, or pause for approval.

See what happened later

Check each step's status, output, and error instead of piecing together a failed script from scattered logs.

What’s included

✓ Webhook, event, cron, and interval triggers, plus manual runs
✓ HTTP steps with secret:// references
✓ Approval (wait) steps that pause a run
✓ Per-step status, output, and error for every run

PLANS AND LIMITS

Workflows are included on every plan. Manage them from the workspace or the CLI.

Cron schedules use the timezone you set. Interval schedules align to UTC.
Steps run one at a time. Dependencies set the order, and a condition can skip a step.
SQL read queries return at most 100 rows.

Compare plans →

DOCSRead the workflows docs

CONNECTED CAPABILITIES