Actions

Integrate with product built-ins or call arbitrary HTTP endpoints. Webhook steps expose method, URL, headers, and body templates on the Execution tab.

Overview

Action steps cover first-party operations (the generic action template) and outbound HTTP via the webhook-call template. They are ideal for side effects after data has been validated by earlier nodes.

Steps in this family

Action

Uses the product's built-in action catalogue: pick the integration behaviour your workspace exposes, then map inputs from upstream tags.

Webhook call

Performs an HTTP request with templated URL, headers, and body. Downstream steps read status codes and response snippets through {{exe.*}} mappings on the Output tab.

Configuration

Webhook call uses the Execution tab for transport details; both templates use Output to shape passthrough or response-derived fields.

Data flow

Templates resolve with the same expression variable rules as AI and code: see Expression variables. Avoid logging secrets into outputs mapped for later AI prompts.