# Postscript

## Overview

With this integration, you can use Postscript to send out the proactive delivery updates that are currently deployed by parcelLab. In the Postscript platform, you can create automation flows to send SMS notifications from Postscript that use trigger events and order data from the parcelLab system

## Standard Trigger Events

The standard parcelLab trigger events that can be used to send notifications in the Postscript platform are described in the following table.

{% hint style="info" %}
Additional custom events can also be made available for use in Postscript.
{% endhint %}

<table><thead><tr><th width="231">parcelLab Trigger Name</th><th width="227">Description</th><th>Postscript Trigger Name</th></tr></thead><tbody><tr><td>Tracking Created</td><td>This notification is sent when a tracking record is created.</td><td>parcelLab - TrackingCreated</td></tr><tr><td>Dispatch</td><td>This notification is sent when a customer’s order has been dispatched from your warehouse.</td><td>parcelLab - Dispatch</td></tr><tr><td>Delayed</td><td>This notification is sent when a customer’s order is delayed while in transit.</td><td>parcelLab - Delayed</td></tr><tr><td>Out for Delivery</td><td>This notification is sent on the day a customer’s order is out for delivery.</td><td>parcelLab - OutForDelivery</td></tr><tr><td>Delivered</td><td>This notification is sent when a customer’s order has been delivered to their delivery address.</td><td>parcelLab - Delivered</td></tr><tr><td>Return to Sender</td><td>This notification is sent when a customer’s order is being returned to the sender. Additional notifications for the order en route to the sender will be suppressed from the customer.</td><td>parcelLab - ReturnToSender</td></tr><tr><td>Return Registered</td><td>This notification is sent when a customer has registered a return.</td><td>parcelLab - ReturnRegistered</td></tr><tr><td>Return Dropped Off</td><td>This notification is sent when a customer has: 1) selected “drop off” as their return method; 2) successfully handed over the return parcel to the carrier.</td><td>parcelLab - ReturnDroppedOff</td></tr><tr><td>Return Delivered</td><td>This notification is sent when a customer’s return has been marked by the carrier as delivered to your warehouse.</td><td>parcelLab - ReturnDelivered</td></tr><tr><td>Return Received in Warehouse</td><td>This notification is sent when a customer’s return has been processed and their reimbursement is being issued.</td><td>parcelLab - ReturnReceivedInWarehouse</td></tr></tbody></table>

## Configuring the Postscript Integration

The following sections describe the configuration required for the Postscript integration with parcelLab.

### Customer Requirements

For successful configuration of the Postscript integration, the following requirements must be met:

* You must have an active account with parcelLab and Postscript.
* Your outbound and/or returns communications must be set up through parcelLab with current order data in the parcelLab system.
* You must provide parcelLab with your Postscript **private** API key.

{% hint style="info" %}
You can find your private API key or create one in your [Postscript account](https://app.postscript.io/account/api).
{% endhint %}

### Implementation Process

When the required information is provided, parcelLab can integrate with Postscript and create the requested event types in your Postscript account to enable the configured communications to be sent via Postscript.

{% hint style="info" %}
For more information on the scope and requirements of integrating Postscript, please contact your parcelLab representative.
{% endhint %}

### Create Automation Flows in Postscript

You can create flows for your SMS communications in Postscript using the trigger events from parcelLab. Each trigger event includes a set of placeholders that can be used in your messages.

To create an automation flow in Postscript:

1. Navigate to your Postscript dashboard.
2. In the navigation menu, select **Messaging**, then select **Automations**.\ <img src="/files/ZkV63RF509FQ5EYE6GW2" alt="" data-size="original">\
   The Automations page will display.
3. Select **Create Automation**, then select **Create Automation Flow** from the dropdown menu.![](/files/lPMCJ6Wk1cXpHnwGeY6G)
4. Select the **Create a new automation** option, then click **Create flow** to create an empty automation flow.\ <img src="/files/Z3oEfij5f6tpHraCDVOj" alt="" data-size="original">
5. In **Automation properties**, select the parcelLab trigger event to trigger the communication flow, and then click **Save**.\
   ![](/files/Asn4zokVgfkJrXlzerRa)
6. Drag and drop the action (for example: Message) that you want to occur after the event is triggered.\
   Each trigger event includes a list of placeholders that you can use in your message.\
   ![](/files/q2D2GDy5ydRGZicjlsEI)
7. When you have added the required action, click **Save**.\
   The automation flow is saved for the selected trigger event.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.parcellab.com/docs/platform/app-store/postscript.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.