Overview
Brands using Brij often want registration data available directly inside Shopify so it can power customer experiences and downstream automations.
With Shopify Flow, you can automatically call the Brij API whenever a customer registers in Brij and store that registration data on the Shopify customer profile as a metafield.
The automation runs automatically whenever Brij updates a Shopify customer profile with a new tag for the specific registration.
Your Shopify store must be on the correct plan to make API calls from Flow. Currently this is the Grow, Advanced and Plus plans. The Basic plan can't run this Flow.
Benefits
Adding Brij registration metadata to Shopify customer profiles enables several powerful use cases:
This creates a single source of truth for registration metadata inside Shopify that can be used to power:
- Personalized “My Gear” pages for logged-in customers showing their registered products
- Automations and segmentation using Shopify Flow or other Shopify apps
- Syncing enriched registration data to external platforms (CRM, ESPs, loyalty platforms, etc.) via Shopify apps or APIs.
- Operational workflows that require product ownership or warranty data
How It Works
When a customer registers a product through Brij:
- Brij updates the customer profile in Shopify with a tag
- Shopify Flow detects the tag update
- Flow calls the Brij Customer Registration API to retrieve the full registration data set using the customer email
- The workflow writes the aggregated registration data (could be multiple) to a Shopify customer metafield
Brij returns a pre-aggregated set of registration data, so the metafield always contains all registrations associated with that customer.
Each time a new registration occurs, the metafield is updated with the latest full customer data set.
Step-by-Step Setup
1. Install Shopify Flow
Shopify Flow is Shopify’s native automation tool.
- In Shopify Admin, go to Apps
- Search for Shopify Flow
- Install the app
2. Create a Customer Metafield
You’ll need a metafield where the registration data will be stored.
- Go to Settings → Custom Data
- Select Customers
- Click Add definition
- Create a metafield as described in the box below
- Save the metafield.
| Field | Value |
|---|---|
| Name | Brij Registration Metadata |
| Namespace | brij |
| Key | registration_metadata |
| Type | JSON |
When creating the Flow workflow, this field will automatically get created if it doesn't exist. You don't have to set it up separately first
3. Create the Shopify Flow Workflow
You can also ask your account manager for the Flow file that can be quickly imported into Shopify, skipping the setup steps below!
Open Shopify Flow and create a new workflow.
Step 1 — Trigger
Set the trigger to: Customer tags added or updated
Brij automatically adds tags to customer profiles whenever a registration occurs, which will trigger the workflow.
Step 2 — Call the Brij API
Add an HTTP request action block that calls the Brij API to retrieve registration metadata.
- Add the URL for the Customer Registrations or Customer Rebates API. Ask your Brij Account Manager for the full URL if you don't have it already.
- Add an 'emails' parameter to the URL as written below so it only returns registrations for the specific shopify profile
emails={{ customer.email | url_encode }}
- Add your Brij API key in the Headers section.
- First remove any defaults Shopify has in the headers section
- Key: API-KEY
- Value: Paste the API key from Brij platform as the Value.
Step 3 — Update the Customer Metafield
Add a step to the flow to update customer metafield created earlier.
Map the API response to the metafield brij.registration_metadata. If you didn't create it already, adding it in the flow here will create it for you.
Configure the step as seen in the screenshot below:
- Choose "use an unstructured metafield"
- Namespace: brij
- Key: registration_metadata
- Type: JSON
- Value: {{ sendHttpRequest.body }}
- This is the response from the API in step 2 above.
What the Data Looks Like
The metafield contains a structured JSON object that includes all registrations tied to that customer. The data returned comes directly from the Brij Customer Registrations API.
Example:
{
"data": [
{
"Registration ID": "Edv6AqsiUW4G",
"Registration Initiation Date": "October 23, 2025 at 20:12 UTC",
"Registration Submission Date": "October 23, 2025 at 20:12 UTC",
"Registration Approval Date": "-",
"Device OS": "Mac OS 10.15.7",
...
}
{
"Registration ID": "Edvdjr98kU7d",
"Registration Initiation Date": "November 13, 2025 at 20:12 UTC",
"Registration Submission Date": "November 29, 2025 at 20:12 UTC",
"Registration Approval Date": "November 29, 2025 at 20:12 UTC",
...
}
],
"limit": 100,
"pageInfo": "Page 1 of 1",
"returnedCount": 2Each time the workflow runs, the API returns the complete set of registrations for that customer, and the Shopify Flow workflow updates the metafield with the latest aggregated data.
For a full list of available fields and the complete response structure, see the Brij API documentation:
Viewing the Data in Shopify
To see the stored metadata:
- Open a customer profile
- Click "View all" fields under the metafields section card
- In the header along the top, click "View unstructured metafields"
- Locate the metafield: brij.registration_metadata
- You can then click "Format JSON" at the bottom to see it in a readable format
The JSON object will contain the customer's full registration history.
Testing the Workflow
You can confirm the automation works by:
- adding any tag to a profile, even something like "testing Brij API"
OR
- Register a product through Brij
- Opening the customer profile in Shopify
- Checking that:
- A new registration tag was added
- The new metafield contains registration metadata
Shopify Flow will also show a history of workflow runs so you can confirm each step executed successfully.
Troubleshooting
The workflow didn’t trigger
Check that:
- The customer profile received new tags from Brij
- The Flow trigger is set to customer tags updated
The metafield is empty
Confirm that:
- The API key is correct
- The API request step succeeded
- The metafield key matches your definition
✅ Once configured, this workflow runs automatically and can typically be deployed in just a few minutes using a reusable upload file.