The PFL + Iterable integration lets you send personalized direct mail from your Iterable journeys, orchestrating physical mail alongside digital channels for a true cross-channel customer experience.
In this article
To use PFL to send direct mail from an Iterable journey, follow these steps:
Schedule an installation call with your PFL customer success manager. They can provide API keys for each PFL store from which you'll place orders.
Before having an installation call with your PFL customer success manager, create a standard Iterable API key. Keep this API key in a safe location; if you lose it, you'll have to create a new one, since Iterable can't show it to you again.
Give the Iterable API key you just created to the PFL Development team. They will use it to authenticate with Iterable when sending events to your project.
The PFL Development team will give you the following information, which you can use to create journey webhooks that make calls to PFL from Iterable:
Webhook URL - The URL your journey webhooks should call to order products. For example:
Webhook key - The key your journey webhooks should use to authenticate with PFL's webhook URL. To use this key, add a custom authorization header to each journey webhook that calls your PFL webhook URL.
JSON request body (one per webhook) - This contains the data the journey webhook will need to pass the PFL endpoint to make an order.
Next, you'll need to create a custom journey webhook for each PFL product that your journeys will order (since the template data and PFL product ID will differ for each). Do this on the Integrations > Journey Webhooks page:
Fill in your new journey webhooks with the following information:
- Name - Something specific to the PFL product being ordered
- Destination - Custom
- Method - POST
- Endpoint - The webhook URL given to you by PFL (see above)
- Authentication - None
To authenticate webhook calls from Iterable with PFL, add a custom header:
<YOUR_PFL_WEBHOOK_KEY>with the value you received from the PFL Development team, above).
Body - The JSON request body provided to you by the PFL Development
team (see above). Also, check Include
We recently renamed Workflows to Journeys—however, our APIs and field names
still refer to them as "Workflows" (for example,
workflowId). Continue to use
the term "Workflows" in your API requests and responses.
Click Create webhook.
Now, you can add this journey webhook to your Iterable journeys.
Order status events
PFL sends order status changes to Iterable as custom events (include statuses associated with PAC order flows). You can use these order statuses to segment audiences, trigger campaigns and journeys, and generate reports.
To make sure that your Iterable project can receive these events from PFL, verify that your project's Manage Custom Events settings (on the Settings > Project Settings page in Iterable) are configured correctly.
If you don't need these events, you can ask your PFL Development team to prevent them from being sent.