This guide walks through how to connect Brij with Postscript so that phone numbers collected through Brij experiences are synced to Postscript in real time.
Once enabled, the integration will:
- Create a subscriber in Postscript when a user submits a phone number through a Brij experience
- Send an opt-out signal to Postscript when a user opts out of SMS messages in Brij
This is especially useful for rebate campaigns and other phone-number-driven experiences. For example:
- A user starts a rebate campaign in Brij
- Brij collects their phone number and sends follow-up SMS messages (e.g., proof of purchase requests)
- That phone number is sent to Postscript as a new subscriber
- If the user later opts out of SMS in Brij, that opt-out is also sent to Postscript
Prerequisites
Before starting, make sure you have the following:
- A Postscript account with permission to create or view API keys
- At least one active Brij experience that collects phone numbers (rebate experiences, registration experiences, or other phone-number-based flows)
This setup requires coordination between the Brij team and the customer. Steps 1 and 3 involve the Brij team. Steps 2 and 4 are completed together with the customer.
Two key values used during setup
There are two values involved in this process, and they serve different purposes. Mixing them up is the most common setup mistake, so it helps to understand them upfront.
Webhook URL — Provided by your Brij representative. This goes in the Authentication step of the Brij automation (Step 4). It tells Brij where to send the webhook data.
Installation User ID — Generated when the customer completes the integration installation. This goes in the Webhook Body inside the Brij automation (Step 4). It allows our system to identify the correct installation instance and route data accordingly.
Both values are required, and each one goes in a specific place. Using the wrong value in the wrong field will prevent the integration from working.
Step 1 - Generate and share the installation link (Brij team)
A Brij team member needs to generate the installation link and share it with the customer.
To do this:
- Log in to the Brij integrations platform
- Navigate to Integrations
- Find the Postscript integration
- Click Installation Link
- Click Share with a new user
- Enter the customer's email address
- Generate the link
Once generated, share the link with the customer directly or walk them through it during a meeting.
Step 2 - Install the integration and authenticate with a Postscript API key (Customer)
When the customer opens the installation link, an installation modal will appear.
Install the integration
- Click Install
- Continue to the Authentication step
Generate the Postscript API key
Before completing authentication, the customer needs to grab an API key from Postscript:
- Log in to Postscript
- Go to Account Settings
- Click API
- On the API page, click Create Security Key Pair in the upper-right corner
- Create a new key labeled for Brij
- Copy the private key
Complete authentication
- Return to the installation modal
- Paste the Postscript private key into the authentication field
- Click Connect
Once connected, the integration is fully configured on the Postscript side.
Step 3 - Capture the Installation User ID (Brij team)
After the installation is complete, the system generates a User ID tied to that specific installation instance. This value is needed in the next step.
The Brij team should locate the Installation User ID and share it with whoever is configuring the automation. Screenshots showing where to find this value are included below.
Important: Do not confuse the Installation User ID with the Webhook URL. They are used in different fields during automation setup. See the "Two key values" section above.
Step 4 - Create the Brij automation (Customer or Brij team)
Now that the installation is complete, the final step is to create a Brij automation that sends the right events into the integration.
Create the automation
- In Brij, create a new automation
- Choose Webhook as the integration type
Authentication
- Use the Webhook URL provided by your Brij representative
- Paste it into the authentication field
This webhook routes data from Brij through our processing layer and into Postscript.
Action
Click Next (no changes needed on this step).
Filters
Select the Brij experiences that collect phone numbers. This includes:
- Rebate experiences
- Registration experiences
- Any other experiences where phone number collection and SMS communication are part of the flow
Only include experiences that are relevant to this integration.
Trigger and Properties
Select the following events:
- Rebate Initiation — captures phone numbers for subscriber creation
- Registration Submission — captures phone numbers for subscriber creation
- SMS Opt-Out — ensures opt-out actions in Brij are reflected in Postscript
These are the only events that collect phone numbers or handle opt-outs, so all three should be selected.
Configuration
- Switch the webhook setting to Internal Webhook
- In the Webhook Body field, paste the Installation User ID generated during setup (not the Webhook URL)
- Save the automation
- Activate it
What to expect after activation
Once the automation is live:
- Brij will begin sending phone numbers from the selected experiences to Postscript
- Eligible users will be created as subscribers in Postscript
- SMS opt-out events from Brij will be sent to Postscript so those users can be unsubscribed
Subscriber creation and opt-out handling will happen automatically as users move through supported Brij flows.
Troubleshooting
Subscribers are not appearing in Postscript
- Confirm the integration was installed successfully
- Verify the Postscript private API key was pasted correctly during authentication
- Make sure the selected Brij experiences actually collect phone numbers
- Confirm the correct trigger events were selected in the automation
Opt-outs are not syncing to Postscript
- Make sure the SMS Opt-Out event is included in the Brij automation triggers
The automation is active, but no data is flowing
- Verify the Webhook URL was used in the authentication step (not the Installation User ID)
- Verify the Installation User ID was pasted into the webhook body (not the Webhook URL)
- Confirm the webhook is set to Internal Webhook
The wrong experiences were included
- Review the Filters step and make sure only phone-number-based experiences are selected