Node Reference
OpenClaw Trigger Node
Trigger workflows from OpenClaw and Telegram-linked inbound events.
The OpenClaw Trigger node is the planned managed-event entrypoint for the OpenClaw integration. It is intended to start a workflow from inbound OpenClaw events, including Telegram-linked delivery when an OpenClaw source is filtered to Telegram, without you wiring up raw HTTP yourself.
Availability
The OpenClaw Trigger node is not yet available to place on the canvas in this build, and the OpenClaw integration is still in progress. This page documents the intended purpose so you can plan around it. For inbound events you can wire up today, use the Webhook Trigger node.
What it is meant to do
- Receive OpenClaw events as a workflow trigger, so an inbound event starts an execution of the downstream graph.
- Support Telegram-linked delivery when an OpenClaw source is filtered to Telegram, so messaging events can drive a workflow.
- Remove the need to manage a raw webhook secret and request parsing for this provider by managing the connection for you.
Managed trigger vs raw webhook
Where the Webhook Trigger node gives you a generic secret-protected HTTP endpoint, the OpenClaw Trigger node is designed to be a provider-aware managed source. Until it ships, model OpenClaw or Telegram delivery as an inbound HTTP webhook into a Webhook Trigger node.
Use the generic webhook trigger in the meantime
The Webhook Trigger node already exposes the inbound request to your workflow through its body, headers, query, method, and URL output ports, and it recognizes several provider event headers for idempotency. That makes it a workable stand-in for provider events while the dedicated OpenClaw Trigger node is being built.
Related
See the OpenClaw integration and Telegram integration pages for connection setup, and Webhook Trigger for the live inbound-event node.
Was this page helpful?