Turn incoming events into useful work.

Receive an event, transform its payload, and hand it to the next service.

Get the YAML ↓Workflow docs

THE FLOW

From trigger to outcome.

A traceable path from an incoming event to a checked downstream response.

01 →
Receive
Define the webhook event and the payload your application sends.
02 →
Transform
Parse the request and select the fields the next step needs.
03 →
Deliver
Call your destination endpoint and inspect the recorded response.

USE THIS RECIPE

Your workflow,
in YAML.

Set context.destination_url to an endpoint that accepts an order as JSON.
Create API_TOKEN in Adios secrets. The destination must accept it in the X-API-Key header.
Send an order.created event with the sample payload shown beside the YAML.

Configure secret references →

Copy or download the manifest, configure your values, and add it through Workflows or your AI workspace. Opening the console does not create or enable a workflow.

Parse requests
Transform JSON
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 }}"

3 stepsOpen Workflows

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"}}

EXPECTED RESULT

Know what to look for.

With the sample event, the destination receives {"id":"ord_1042","total":49,"currency":"USD"}. The deliver step records its response body.

The request-parser extracts fields; it does not validate an order schema. Add validation in your application or a script step if fields are required.

TEST YOUR SETUP

Check a complete run.

The delivered body should contain id, total, and currency, without the outer order wrapper.
Handle repeated order IDs at the destination before connecting real events. This example does not deduplicate them.
Test a missing order and a failed destination request, then inspect the step error in run history.

Adapt this recipe with your AI agent

Help me create an Adios webhook-processing workflow. First ask for a sample payload, event name, destination endpoint, and required secret references. Use a request-parser or data-json step to select the fields and an HTTP step to deliver the result. Explain how duplicate events and failures will be handled. Show me the workflow and a test plan before creating or enabling anything. Do not send real customer data during tests.

Open Workflows ↗

KEEP CONNECTING