Blueshift
Integrate Poplar with Blueshift to trigger direct mailers from any journey.

Before You Start
Make sure you’ve completed the following in Poplar:
Create a Campaign in Poplar.
Upload at least one Creative (a placeholder is fine for testing).
Locate your Test Access Token and Production Access Token on the API page of your Poplar account.
App Hub (Custom App)
In Blueshift, go to App Hub → My Apps → +ADD CUSTOM APP.
Name it (e.g., Poplar Mail).
Authentication: choose Basic HTTP and add the HTTP Headers as shown below.
(Optional) Upload a logo and save.

Add an Adapter
Open your new Poplar Mail app → click +ADAPTER.
Enter the HTTP Headers exactly as pictured below. Copy and paste your Test API key from Poplar in the API Key section after "Bearer" (later the production API key will be used when you want to set the campaign live).
Save the adapter.

Cloud App Template (Payload)
Go to Templates → Cloud App → +TEMPLATE and choose your Poplar Webhook app.
Properties → Settings: select your Adapter and set API Endpoint to:
https://api.heypoplar.com/v1/mailing/
Advanced settings:
HTTP method:
POST
HTTP headers: add
Authorization: Bearer YOUR_TEST_OR_PRODUCTION_ACCESS_TOKEN
Leave default
Content-Type: application/json
(Optional) Unique Sent Identifier → choose
email
orcustomer_id
to prevent duplicates.
Click the eye in the top right to pull up your user attributes for reference
Content: set the Payload to JSON and paste one of the templates below.
{
"recipient": {
"full_name": "{{user.firstname}} {{user.lastname}}",
"address_1": "{{user.address_line1}}",
"address_2": "{{user.address_line2}}",
"city": "{{user.address_city}}",
"state": "{{user.address_state}}",
"postal_code": "{{user.address_postal_code}}"
},
"campaign_id": "REPLACE-WITH-YOUR-CAMPAIGN-ID",
"creative_id": "REPLACE-WITH-YOUR-CREATIVE-ID"
}
Merge-tags (Optional): If using custom merge tags for a dynamic creative, they should be listed within a merge_tags object like so:
{
"recipient": {
"email": "{{user.email}}"
},
"merge_tags": {
"promo-code": "{{user.code}}"
},
"campaign_id": "REPLACE-WITH-YOUR-CAMPAIGN-ID",
"creative_id": "REPLACE-WITH-YOUR-CREATIVE-ID"
}
Journey (Trigger)
Create or open a Campaign in Blueshift.
In Journey builder, choose the trigger type you need (e.g., Event-triggered for cart abandonment, Segment-triggered for lifecycle).
Add a Cloud App node. Select:
Channel/App: your Poplar Webhook app
Adapter: the adapter you created
Template: the Cloud App template you just built
Connect it in the flow where the mailer should be sent.
Validate and launch your Journey!

Conditional / Decision Splits (optional)
If some customers have only email while others have full address data, branch your journey:
Add a Decision Split that checks for presence of address fields (e.g.,
user.address_1
anduser.postal_code
).Path A → Use Template A (Email-only) for Address Enrichment.
Path B → Use Template B (Address Data) for direct mail.
Test & Preview
There are two reliable ways to test in Blueshift:
1) Test from the Cloud App Template
Open your template → Test Send.
Pick a Preview User and send.
Confirm a 201 response is returned
400 indicates an error in the payload setup, or missing required data from the user's profile (address 1, city, postal code).
2) Test from the Journey
In your campaign’s Journey tab, use Test send message on the Cloud App node.
This method uses the actual adapter + campaign context, which is handy if you rely on campaign parameters.
Validate the Connection in Poplar
In your Poplar campaign, open the History tab to see the test mailers.
Click into a mailer to view the PDF proof and Request Details; verify the request matches the payload you built in Blueshift.
If everything looks good, Edit your Adapter and enter your Poplar production API key to start sending mailers
Last updated