Connect Brij registrations to Kustomer

Brij sends each approved product registration to your Kustomer account. Agents then see it on that customer's timeline, with the product, where it was purchased, the receipt links, and the registration status. Nothing is hosted outside Kustomer, and your current claim flow doesn't change.

You need Kustomer admin access and Brij admin access. Setup is done once, in four parts.

Part 1. Create the "Brij Registration" record type in Kustomer

1. Go to Settings > Platform > Klasses (custom objects).
2. Create a new Klass named Brij Registration. Keep the system name "brijregistration" (lowercase, no spaces).
3. Add these attributes. The type matters, because Kustomer builds each field's system name from its type.

1. Open the Klass's Timeline Layout (Settings > Platform > Klasses > Brij Registration > Timeline Layout). Show Product, Purchase Channel, Purchase Date, Registration Status, Serial Number and Receipt Links. A simple layout is fine, and you can refine it later.

Part 2. Create the webhook receiver in Kustomer

1. Go to Settings > Security > API Keys and add an API key named "Brij Webhook". Give it the role for inbound webhooks (listed as org.hooks; it may appear as org.hook). Copy the key right away, because Kustomer shows it only once.
2. Create an inbound webhook (Settings > Platform, in the Hooks / Inbound Webhooks area; you can also create it from the workflow editor in Part 4). Choose the Webhook type, not Form. Name it "Brij Registrations".
3. Set the event name to start with "kustomer.app", for example kustomer.app.brij.registration.approved. Kustomer only routes events with that prefix to workflows.
4. Copy the webhook URL Kustomer generates.

Part 3. Connect Brij to Kustomer

Set this up in your Brij account. For screenshots and details, see How to Configure Webhooks in Brij Automations. Use the webhook URL and API key from Part 2.

1. In the Integration tab, select Webhook.
2. In the Authentication tab:
   • Name your webhook (for example, "Kustomer Registrations").
   • Select the webhook type External.
   • Enter the Webhook URL from Part 2.
   • Add the API key from Part 2 as the Authorization header (Bearer) if the tab asks for headers.
3. In the Filters tab:
   • Choose the Brij experiences whose registrations should go to Kustomer, or select All Experiences.
4. In the Action tab, select the latest version of the webhook integration.
5. In the Triggers & Properties tab:
   • Select Registration Approval.
6. In the Configuration tab:
   • Leave the HMAC signing key blank (Brij generates one).
   • Optionally, pause the automation after a set number of failures and turn on email notifications.

Then approve one registration in Brij, so Kustomer receives a first event to build the workflow from.

Part 4. Create the workflow in Kustomer

1. Go to Settings > Platform > Workflows and create a workflow named "Brij registration to timeline".
2. Trigger: choose the Hooks app, then the Brij Registrations event from Part 2.
3. Open View Logs at the bottom of the editor. The first approved registration from Part 3 should be listed. Its data is what the field pickers in each step show.
4. Step 1, Customer: Lookup (By Email). Select the customer email from the Brij data.
5. Step 2, create a custom object (KObject) with the customer, Klass "brijregistration". Set the title to something like "Brij registration: <product>", and map the fields from Part 1 to the matching Brij data:
   • Customer email: in the user details (meta > user > email), also sent as "Customer Email"
   • Registration ID, Registration Date, Registration Status, Registration Purchase Date, Registration Purchase Channel
   • Product: "Experience Title"; SKU: "Experience Product or SKU Number"
   • Receipt links: "Purchase Receipt" (a list of image URLs)
   • Serial Number
6. If no customer matches the email, add a step that creates the customer first, then continue to Step 2.
7. Save and enable the workflow.

Checking that it works

1. Approve another registration in Brij.
2. In Kustomer, check the workflow's View Logs. The event should appear within a minute or so.
3. Open that customer in Kustomer and confirm a "Brij Registration" entry appears on the timeline.

Troubleshooting

• Nothing shows in View Logs: check the webhook URL, the event name prefix (kustomer.app), and that the API key has the webhook role. In Brij, check the automation's Request and Response logs.
• The entry shows up but fields are blank: re-select the fields with the pickers in Step 2 of Part 4.
• The entry is attached to the wrong customer: the lookup is by email, so check which email Brij sent.