Understanding Postscript Triggers
The Postscript API uses the concepts of "triggers" and "subscribers" in order to deliver notifications to customers.
Subscribers are customers who have explicitly opted in to receive SMS notifications for a brand.
Triggers essentially represent different types of events that, when fired, can be used to send SMS notifications to a subscriber.
Automations are "multi-stage communication that are triggered by a certain event", and are the primary tool for building and sending SMS notifications.
Available Triggers with Malomo
When a trigger is fired (when a Malomo event occurs), an active Postscript automation for that trigger must also exist in your account in order for SMS notifications to be sent. Since Malomo will send a unique event for each Shipment, it's our recommendation that you only use the following events for triggers: Pre-transit, Out-for-delivery, and Delivered. This will ensure that you do not send a customer two notifications for their order.
However, the triggers that are available to use in Postscript are:
Malomo: Shopify Order Created
Malomo: Shipment Created
Malomo: Pre Transit
Malomo: In Transit**
Malomo: Out for Delivery
Malomo: Delivered
Malomo: Available For Pickup
Malomo: Return To Sender
Malomo: Failure
Malomo: Cancelled
Malomo: Error
**
Event name | Description |
| Shopify records a new order placed by a customer. |
| Shopify records a new shipment on an order and that shipment registers in the Malomo platform. |
| Malomo records an error when trying to register a shipment in the Malomo platform. Learn more about error codes here. |
| A shipping label was created and has been registered in the carrier’s system. However, the carrier has not yet taken possession of the shipment. |
| Only the first scan event when the shipment is in the carrier’s possession and is en route to its destination. |
| The shipment is in the carrier’s possession and is en route to its destination. |
| Only the first scan event when the shipment is currently on its last mile and is en route to the destination address. |
| The shipment is currently on its last mile and is en route to the destination address. |
| The local delivery vehicle has reported the package was delivered. |
| The shipment was not successfully delivered and is en route back to sender. |
| The delivery has been canceled typically by either the seller or recipient. |
| The shipment is available for pickup from the carrier’s facility such as a post office. |
| A delivery was attempted but the shipment could not be delivered. |
| An unknown delivery error occurred. |
| An order that has been created but has not been fulfilled in the specified time frame within our Problem Orders feature. |
| An order that has been fulfilled or is in transit and has not received a scan update in the specified time frame within our Problem Orders feature. |
*Please note, we do not recommend triggering a status off of InTransit or OutforDelivery, as the journey will may trigger multiple texts to your customer. Our system receives the InTransit status on every scan event received between PreTransit and OutForDeliveryPlease use our Malomo: ShipmentFirstInTransit and Malomo: ShipmentFirstOutForDelivery triggers instead.
Testing your PostScript Integration
Unlike email, SMS notifications require explicit opt-in from the customer in order to be sent.
To send SMS notifications to yourself:
From your main Postscript dashboard, click Keywords in the left sidebar.
Text one of the listed keyword codes to the phone number shown on the screen, and follow the prompts to opt into SMS notifications from your store.
In order to receive SMS notifications to your phone, make sure that your phone number is associated with a customer record in your Shopify store, and that you always use this customer when creating test orders in Shopify.
...