Adios

ADIOS WORKFLOWS

Your app runs.
Let the work flow.

Connect APIs, transform data, schedule routine jobs, and pause for approvals. Keep every step and its result in view.

PRACTICAL STARTING POINTS

Pick the work you want off your list.

Each guide includes a complete YAML manifest, the values to configure, and the result to expect from a test run.

  1. 01 / TRIGGER

    Start when it matters.

    Run manually, on a schedule, or in response to a webhook or event.

  2. 02 / CONNECT

    Make the steps explicit.

    Link steps with dependencies, pass their outputs forward, and pause for a human decision when needed.

  3. 03 / INSPECT

    Know what happened.

    Follow inputs, outputs, status, and errors for each step of a run.

SUPPORTED ACTIONS

Ten ways to get the work done.

Every action uses the same run history. Choose an action to see its configuration in the reference.

COMPLETE YAML EXAMPLES

Five examples. Ready to adapt.

Explore all five examples, including object storage and scripts. Configure your services before running them.

  1. Parse requests
  2. Transform JSON
  3. Call APIs
webhook-delivery.yaml
Download
workflow_id: webhook-delivery
title: Route a webhook
enabled: true
triggers:
  - type: webhook
    event: order.created

context:
  destination_url: https://api.example.com/orders

steps:
  - step_id: parse
    kind: request-parser
    command:
      extract:
        order: .payload.order

  - step_id: order
    kind: data-json
    dependencies: [parse]
    command:
      from_step: parse
      path: .order

  - step_id: deliver
    kind: http
    dependencies: [order]
    command:
      method: POST
      url: "{{ .context.destination_url }}"
      headers:
        X-API-Key: secret://API_TOKEN
      body: "{{ .steps.order.output }}"

Setup Set your destination URL and API_TOKEN secret for the X-API-Key header. Send the sample payload with the order.created event.

Sample event payload{"order":{"id":"ord_1042","total":49,"currency":"USD"}}

Scheduled examples use repeating intervals. For timing, credentials, and approval behavior, see the workflow reference →

Keep automation next to the app.

Build in the console or define workflow manifests alongside your source.

Read the workflow docs ↗