Overview

Brij’s Webhook integration enables seamless data transmission by automatically sending event-triggered payloads to a designated webhook URL. Events such as Registration Initiation, Submission, Approval, Denial, Form Submission, and Review Submission act as triggers, generating a configurable data payload that is delivered to external systems in real-time.

All event triggers and their associated properties can be customized within Brij’s no-code Automations setup wizard, allowing for flexibility in how and when data is sent. If the receiving application requires the payload data to be reformatted for proper ingestion, middleware may be necessary to transform the data before it reaches its destination.

<aside> 💡 For assistance with custom middleware integrations, you can contact Brij Support to explore tailored solutions that ensure compatibility with your specific tech stack.

</aside>

How to Configure a Webhook in Brij Automations

1. In the Integration tab, select Webhook from the available options.

   

2. In the Authentication tab:

   • Give your webhook a name.

   • Select the webhook type (Internal or External).

   • Enter the Webhook URL.

     

3. In the Filters tab:

   • Choose the Brij experiences for which you want this webhook to run.

   • To apply the webhook to all experiences, select All Experiences from the dropdown.

     

4. In the Action tab, select the latest version of the webhook integration.

   

5. In the Triggers & Properties tab:

   • Choose the specific Brij events that should trigger the webhook (see “Triggers & Properties”) section below for a complete list of triggers and properties.

   Note: Not all properties will be available for every trigger. Only the properties captured at the time of the trigger event will be sent.

   For example, if a customer enters their purchase channel during the registration process, this property will be included in the Registration Submission event but not in the Registration Initiation event, as it was entered after the initiation event occurred.

   

   Note: To optimize performance, only include events relevant to your use case.

   

6. In the Configuration tab:

   • Optionally, add an HMAC signing key, or leave it blank to generate one automatically.
   • Configure automation settings, such as:

     • Pausing the automation after a set number of failures.

     • Enabling email notifications when the automation is paused or for every error.

       

Available Webhook Triggers & Properties:

Trigger Events:

Registration Initiation

• This event is triggered when a user begins the registration process but has not yet completed it. It captures basic details such as device, location, and experience data, but may not include all customer-provided information.

Registration Submission