HTTP & Webhook Actions

The http family makes outbound HTTP calls to external APIs (optionally authenticated via a stored connection). The webhook family sends signed outgoing webhooks and writes a custom response back to an inbound webhook trigger.

HTTP — Outbound Requests

Six operators. The generic request operator takes an explicit method; the verb operators (get/post/put/patch/delete) are shorthands and accept a connection reference for authenticated calls.

A 2xx response succeeds the step; any other status fails it, with the status folded into a stable error category (HTTP 429 rate_limited, HTTP 503 upstream_error, and so on) that retry policies can match on. The status and body are on the step output either way, so a step that must tolerate a 404 can be marked continueOnError and branched on {{steps.X.response.status}}.

- name: createContact
  type: http
  operator: post
  props:
    url: 'https://api.crm.example/contacts'
    connection: crm-oauth
    contentType: json
    body: { email: '{{trigger.data.email}}', name: '{{trigger.data.name}}' }

Webhook — Outgoing & Response

Two operators. send fires a signed outgoing webhook; response writes the HTTP response for an automation started by a webhook trigger.

# Notify a downstream service
- name: notifyDownstream
  type: webhook
  operator: send
  props:
    url: 'https://hooks.example.com/orders'
    event: order.created
    data: { id: '{{trigger.data.id}}' }
    secret: $env.OUTGOING_WEBHOOK_SECRET

# Reply to the inbound caller
- name: ack
  type: webhook
  operator: response
  props: { status: 200, body: { ok: true } }

Related Pages

• Connections — OAuth2, API key, basic, bearer credentials.
• Environment Variables — $env secrets used in headers.
• Triggers — the inbound webhook trigger.
• Table Webhooks — automatic outgoing webhooks on record events.
• Data & State Actions — transforming HTTP responses.