• INTEGRATIONS AND DEVELOPER API • SETUP GUIDE

How to Configure an Outbound Webhook

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Send Shopify registration submissions as JSON to a webhook endpoint for Make, n8n, or your own service.

Before you begin

Use the intended service account and select the destination list, channel, spreadsheet tab, or endpoint. Decide whether you are testing a new-submission event or an approval event, and use a clearly identifiable test application.

Send application data to your own workflow

The outbound webhook sends the full submission as JSON to your configured HTTPS endpoint. It can connect an owned receiver or a workflow in Make or n8n. An optional HMAC-SHA256 secret lets your receiver verify authenticity.

The receiver must handle the documented event payload and avoid unintended duplicate downstream work. Inspect a new-submission event and an approval event separately; do not guess headers or JSON property names from an older integration.

Set up this workflow

  1. Open Integrations and choose Outbound webhook.

  2. Enter an HTTPS endpoint controlled by your intended workflow.

  3. Set an HMAC secret when the receiver will verify signatures.

  4. Save the integration.

  5. Submit a non-spam test and inspect the received JSON at the endpoint.

  6. Approve through a supported path and check the expected approval event without creating duplicate downstream processing.

Example

Point the integration to a test receiver you control and submit one application with dummy business data. Inspect the JSON, then test an approval event separately.

Expected result

The receiver records the expected event and can identify its application without processing the same event twice.

Limits and important behavior

  • The webhook sends the full submission JSON; handle applicant information appropriately.
  • Integrations run asynchronously, so endpoint failure should not block form submission.
  • Use the documented event and signature details from the current app/API docs rather than assuming header names.

Troubleshooting and verification

If data does not reach the destination, confirm the application exists and is not Spam, then check the connection, event, and selected destination. Email-marketing services need an applicant email. Background failures do not undo a received submission.

Screenshots to add

Screenshot placeholder: Capture the relevant app screen for “How to Configure an Outbound Webhook” after completing the setup. Show the controls used to open Integrations and choose Outbound webhook. Add a second screenshot showing the result of this check: Approve through a supported path and check the expected approval event without creating duplicate downstream processing. Use dummy applicant details and mask any secrets.

Related guides