Automations

Automations let you build ordered chains of actions that execute automatically when a webhook arrives at your debug endpoint. Extract data, make HTTP requests, run JavaScript, store values, set conditions, and customize responses — all without writing a full integration.

How it works

1. A webhook arrives at your endpoint
2. Mock response rules are evaluated first (if any) to determine the base response
3. The automation chain runs — each action executes in order by position
4. The response is sent back to the webhook sender (with any modifications applied by actions)

Actions execute sequentially. Each action can read data set by previous actions through chain variables, and errors in individual actions are non-fatal — the chain continues.

Action types

Type	Description
Condition	Evaluate filters against request data to continue or stop the chain
Extract JSON	Pull values from the request into chain variables for use in later actions
HTTP Request	Make outbound HTTP calls to external services
Run Script	Execute JavaScript in a sandboxed QuickJS runtime
Store Variable	Persist data to the Datastore with optional TTL
Modify Response	Override the HTTP response sent back to the webhook sender

Key concepts

Chain variables

Actions can produce variables that are available to all subsequent actions in the same chain. For example, an Extract JSON action can extract a field from the request body, and a later HTTP Request action can use that value in its URL or body via template interpolation.

Chain variables only exist for the duration of a single webhook request.

Template interpolation

Most action configuration fields support template interpolation using the $namespace.path$ syntax. This lets you dynamically reference request data, endpoint metadata, chain variables, and Datastore values.

See Template Interpolation for the full reference.

Non-fatal errors

If an action fails (e.g., an HTTP request times out or a script throws an error), the error is logged but the chain continues to the next action. This ensures that one failing action doesn't block the rest of your automation.

Enabling and disabling actions

Each action has an enabled flag. Disabled actions are skipped during execution without being removed, so you can toggle them on and off for testing.

Creating automations

Dashboard

1. Open your endpoint in the Dashboard
2. Go to the Automations section
3. Click Add Action
4. Select the action type and configure it
5. Save the action

You can reorder actions by dragging them to change the execution sequence.

REST API

Use the Endpoint Actions API to create, update, delete, and reorder actions programmatically.

MCP Server

The MCP server provides tools for managing actions: create_endpoint_action, list_endpoint_actions, and delete_endpoint_action.

Plan limits

Plan	Automations
Free	Not available
Pro	5 actions per endpoint
Team	20 actions per endpoint
Enterprise	Unlimited

See Plans & Billing for full plan details.

Migrating from Scripts

If you previously used Scripts (forwarding destinations with JavaScript), your script logic maps to the run_script action type. The handle(request) function signature and return format are the same.

If you used forwarding destinations for automatic URL forwarding, that maps to the http_request action type — with the added benefit of template interpolation for dynamic URLs, headers, and bodies.