WEBHOOK_INBOUND
Trigger: fires on an inbound webhook.
What it does
Trigger: fires on an inbound webhook.
Inputs & outputs
| Input handle |
|---|
| None |
| Output handle |
|---|
| None |
Configuration
No configuration.
Example
How it works
WEBHOOK_INBOUND exposes a token-secured, unauthenticated HTTP endpoint:
POST /api/v1/webhooks/inbound/{token}External services (payment processors, CRMs, marketing tools) post JSON to this URL. EzFlow validates the token, flattens the JSON payload into a key/value map, and starts the Workflow with the flattened data available to downstream nodes. The endpoint returns HTTP 202 immediately so the caller is not blocked waiting for execution to finish. A rate-limit guard protects each token from abuse.
Example
Stripe sends a payment_intent.succeeded event to your Webhook URL after a successful charge. Downstream nodes read the flattened fields (type, data.object.amount, data.object.receipt_email) and branch on the event type using a CONDITIONAL node. The matching branch sends a payment-confirmation email via SEND_MAIL and logs the amount to a database record via ADD_DATABASE_RECORD.