maestro
latest
false
Maestro Orchestrate user guide
- Introduction
- Getting started
- Build on any canvas
- Build with Case
- Reference
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Build with Flow
- Delay
- Connector event
- HTTP Webhook
- Build with BPMN
- Operating
- Monitoring
- Optimizing
- Reference information
HTTP Webhook
Start a workflow, or resume a paused run, when another app sends a request to a web address that the HTTP Webhook node gives you.
HTTP Webhook connects a workflow to any app that can send a webhook, a request that the app sends to a web address when something happens. The node gives you that address. You paste it into the other app, and each request it sends reaches the workflow.
The node appears in two places, and works the same way in both:
- As a trigger, in the Change trigger list: each request starts a new run.
- As a wait step, in Add node > Wait for event: the run pauses at the node until a request arrives, then continues.
Set it up
- Add the node, as a trigger or as a wait step.
- In Connection, select an HTTP Webhook connection, or create one. HTTP Webhook authentication describes the options.
- Copy the webhook URL from the box at the top of the panel, and paste it into the webhook settings of the other app.
- Optionally, add a Filter, so only matching requests count:
- Select Add condition or Add group.
- Choose All (AND) or Any (OR).
- Deploy the workflow. Requests reach it only after it's deployed.
Fields
| Field | Required | Description |
|---|---|---|
| Webhook URL | — | The address to paste into the other app. Each node has its own. |
| Connection | Yes | The HTTP Webhook connection that receives the requests. Refresh Schema reloads the shape of the incoming data. |
| Filter | No | Conditions that a request must match. Requests that don't match are ignored. |
| Input arguments | No | Trigger only. Values that other nodes read under $vars.<node ID>.output. |
Output
The node's output is the request that the other app sent. Until the first request arrives, the node doesn't know its shape, so send one test request before you reference its fields in later nodes. Using the Webhook connector describes the connector in full.
Next steps
- Triggers: the other ways to start a workflow.
- Delay: pause a run for a set time instead.
- Deploy a workflow: make the webhook live.