Skip to content
Releaseo

Send events to Zapier, Make, n8n, or your server with Webhook Out

Create signed webhook destinations, choose which widget and custom events to forward, and verify requests with your signing secret.

Webhook Out forwards selected Releaseo events to a URL you choose as signed HTTP requests. Use it to trigger automations in Zapier, Make, or n8n, or to send events straight to your own backend. You can create several destinations, each with its own environment, events, and signing secret.

Create a webhook destination

  1. Open Integrations in the sidebar and find Webhook Out under Automation.

  2. Select Connect, then Create webhook.

  3. Enter a Destination name you'll recognize (for example, “Zapier – new contacts”), a unique Destination key, and an optional Description.

  4. Choose the Environment: Production, Stage, or Development.

  5. Enter the Endpoint URL that will receive events, for example https://example.com/webhooks/releaseo.

  6. Under Signing secret, select Generate, then Copy and store it somewhere safe. It's stored encrypted and is never shown again after you save.

  7. Pick the events to send (see below) and select Create destination.

Choose which events to send

  • Send subscribed events turns on delivery for the events you select. On by default.

  • Include identify payloads adds user identify data to the requests. Off by default.

  • Rate limit per minute caps how many events are delivered each minute. The default is 1,000.

Widget events you can subscribe to:

  • SDK initialized (sdk_init)

  • Widget loaded (widget_loaded)

  • Widget opened (widget_open)

  • Widget closed (widget_closed)

  • Post viewed (post_open)

  • CTA clicked (cta_click)

  • Link clicked (link_clicked)

  • Contact CTA clicked (home_contact_cta_clicked)

  • Read state changed (read_state_changed)

  • Contact submission created (contact_submission_created)

Only Contact submission created is selected by default. Under Custom event triggers, you can also forward any custom events you've set up in your workspace.

Security and privacy

  • Every request is signed with the destination's signing secret. Verify the signature on your server before you trust the payload, and reject requests that don't match.

  • Contact submissions use PII-safe properties by default.

  • Keep the signing secret on your server only, never in client-side code. If it leaks, replace the destination with a new one and a fresh secret.

Connect Zapier, Make, or n8n

  1. In your automation tool, add a trigger that receives a webhook, such as Webhooks by Zapier → Catch Hook, a Make Custom webhook, or an n8n Webhook node, and copy its URL.

  2. Paste that URL as the Endpoint URL of a new destination in Releaseo.

  3. Trigger one of the selected events, for example by submitting the contact form in the widget, and check that it arrives in your tool.

Was this article helpful?

Still stuck? Contact us and mention this article.