Webhook
Node Card
Category: Communication Nodes
Type:
webhookTypical position: Any point in a flow where an external system must be notified: for example, after a successful registration or before a Success Final node.
Properties
Outputs & Errors
| Property | Type | Required | Description |
|---|---|---|---|
| Webhook Name | text | Yes | Identifier for this webhook call. Displayed as the node label on the canvas. |
| Subscribe URL | text | Yes | The HTTPS endpoint to POST the event payload to. Must be a valid HTTPS URL. |
| Secret Name | select | No | An HMAC signing secret from your configured webhook secrets. When provided, LoginRadius signs the payload and includes the signature in the request headers so the receiving endpoint can verify authenticity. |
| Output | Condition |
|---|---|
output | Always proceeds after firing the webhook, regardless of the remote endpoint's HTTP response. |
note
The webhook fires asynchronously: the workflow does not wait for a response from the target endpoint before continuing to the next node.
Common Next Nodes
Webhook (output)→Success Finalevent fired: complete the flow
Usage Notes
Use the Webhook node to push identity events (such as registration, login, or profile updates) to external systems like CRMs, data warehouses, or audit services. Always use HTTPS endpoints and configure a Secret Name to enable HMAC signature verification on the receiving end.