OpenClaw Trigger
The OpenClaw Trigger starts your workflow from an inbound OpenClaw call. You describe the trigger as a skill, install that skill in your OpenClaw agent, and the agent calls your workflow's webhook URL whenever the skill is needed.
Agent-to-workflow bridge: Your OpenClaw agent gains a new skill — "call this Indite workflow" — and sends a JSON payload that your workflow can read and act on.
The OpenClaw Trigger requires a paid plan. It is not available on the Free plan.
Key Features
- Dedicated Webhook URL: Each workflow gets its own URL:
https://<your-builder>/api/webhooks/openclaw/<workflowId> - Authenticated: Every call must send an
Authorization: Bearer <API key>header — unauthenticated requests are rejected - Body Schema: Define the JSON structure OpenClaw should send, so the agent knows what data to include
- Generated Skill Command: The block generates a ready-to-run command (Linux, macOS, Windows) that installs the skill into OpenClaw
- Variable Mapping: Save fields from the request body into workflow variables
Configuration
| Parameter | Type | Required | Description |
|---|---|---|---|
| Name | Text | Yes | A unique name to identify this trigger, e.g. send-email-indite. Used as the OpenClaw skill name |
| Description | Text | Yes | Helps OpenClaw understand when to use this trigger |
| OpenClaw Webhook URL | Read-only | — | Auto-generated. Copy it with the copy button |
| Expected JSON Body Schema | JSON | No | The JSON structure OpenClaw will send |
| Save in variables | List | No | Map request body fields to workflow variables |
Setting up the trigger
- Add the OpenClaw Trigger block to your workflow.
- Give it a Name and a clear Description (OpenClaw reads the description to decide when to call it).
- Optionally define the Expected JSON Body Schema so the agent sends the right fields.
- Create an API key under Settings → Account → API keys if you don't have one.
- Open the Curl Command section, pick your OS tab (Linux, macOS, or Windows), and copy the command.
- Run the command on the machine where OpenClaw runs. It creates a
SKILL.mdfile in OpenClaw's workspace with the webhook URL and instructions. Replace<YOUR_API_KEY>in the file with your real API key. - Publish the workflow. Your OpenClaw agent can now trigger it.
Calls without a valid Authorization: Bearer <API key> header will fail. Always keep the header in the skill file, and never share your API key.
Output
The full request body is available to downstream blocks. Map fields under Save in variables:
| Field | Description |
|---|---|
data.<field> | Any field from the JSON body. For example, if OpenClaw sends { "id": 1 }, map data.id to a variable |
Add one entry per field you need, pick the body key, and choose the variable to store it in.