Overview

Postscript lets Shopify merchants send personalized SMS (text message) campaigns. When you integrate Postscript with Growave, Growave sends custom events to Postscript for wishlist activity and review reminders, and you build the SMS automations that respond to those events. This creates a connected experience across your store and your text messaging.

⚠️ Important: The integration now uses a new API: Growave sends a custom event to Postscript and you build the SMS Automation on it (previously, Growave sent each SMS through a Postscript trigger linked by ID). Your old trigger-based automations no longer fire, so rebuild each one once as an event-based automation using the steps below. Until you do, Growave keeps sending events but no SMS is delivered.

Which Growave events Postscript can use

The integration sends these Growave custom events to Postscript, and you can build an SMS automation on each one:

Growave - ReviewRequest: Asks a customer to review a recent purchase.
Growave - WishlistBackInStock: Notifies a customer when an item on their wishlist is back in stock.
Growave - WishlistOnSave: Reminds a customer about items they saved to their wishlist.

Each event carries variables (such as the customer's first name and a link to their wishlist or review page) that you can insert into the SMS to personalize it.

How to connect Growave and Postscript

Connecting Growave and Postscript is a one-time setup that authorizes the two apps to exchange data. This connection step has not changed with the new API.

In your Postscript admin panel, click your account name and select the API section.
Under API keys, click Create Security Key Pair.
Confirm the creation, then click Show under the Private Key label and copy the value.
In your Growave admin panel, go to Settings → Integrations and select the Postscript app card.
Paste your private API key into the field, click Enable, and save your changes.

How to set up an SMS automation in Postscript

To send an SMS in response to a Growave event, you build a Postscript Automation Flow that starts with a Growave custom event as its trigger. Repeat these steps for each event you want to send SMS for.

In Postscript dashboard, go to Messaging → Automations.
Click Create Automation.
In the Choose where to start window, select Automation Flow and click Create an Automation Flow. (Do not use Legacy Automations — the new integration uses custom events, not legacy triggers.)
In Automation Properties, open the Trigger event or property dropdown and select the Growave event you want to send SMS for: Growave - ReviewRequest, Growave - WishlistBackInStock, or Growave - WishlistOnSave. Click Update.
Drag a Message step onto the canvas below the trigger to add the SMS.
Type your SMS text. Wherever you want a personalized value (the customer's first name, product name, or a link), click the merge tag icon in the message toolbar, then pick the value from the Trigger Event Properties list (see the examples and variable list below).
Click Save.
Click Schedule or Activate to make the automation live.

⚠️ Important: Postscript requires every message to include your shop name and adds a Shop Name tag to the start of each new message by default. Leave this tag in place. If you remove it, Postscript shows a "Messages must include your shop name" warning and the message is not valid. The shop name tag comes from the Basic Info section of the merge tag picker (shown as Shop - Name).

Example messages and event variables

In the examples below, the words in bold are values you insert from the Trigger Event Properties list in the merge tag picker — you don't type them. Type the plain text around them, then click the merge tag icon to drop each value in place. Postscript fills in each value with the customer's real data when it sends the SMS.

Each message must contain shop name, so keep the default Shop Name tag in place as described above.

Growave - ReviewRequest: Shop Name Hi First Name, please review Product Name: Order Review Url
Growave - WishlistBackInStock: Shop Name First Name, your item is back! Wishlist Page Url
Growave - WishlistOnSave: Shop Name Hi First Name, the items you saved to your wishlist are waiting for you: Wishlist Page Url

Available event variables

The Trigger Event Properties shown in the merge tag picker depend on which Growave event you chose as the trigger. Every event includes First Name, Last Name, Shop Link, and Shop Name. The properties unique to each event are listed in the last column.

Custom event	What it sends	All Trigger Event Properties in the picker	Event-specific properties
Growave - ReviewRequest	Encourages a customer to review a recent purchase	First Name, Last Name, Product Name, Order Review Url, Shop Link, Shop Name	Product Name — the purchased product; Order Review Url — link to the review page for that order
Growave - WishlistBackInStock	Notifies a customer that a wishlisted item is restocked	First Name, Last Name, Wishlist Page Url, Shop Link, Shop Name	Wishlist Page Url — link to the customer's wishlist
Growave - WishlistOnSave	Reminds a customer about items saved to their wishlist	First Name, Last Name, Wishlist Page Url, Shop Link, Shop Name	Wishlist Page Url — link to the customer's wishlist

📘 Note: If a property you expect isn't listed in the picker, make sure the automation's trigger is set to the matching Growave event, since the picker only shows the properties for the selected trigger.

Make your automations smarter (optional)

A basic automation sends one SMS as soon as the event arrives, but Postscript Automation Flows let you add more steps to the same flow. These are optional and apply to any Postscript flow:

Delay: Add a wait before the SMS sends (a fixed interval, a specific date and time, or a day of the week). Use this if you want to space out a message rather than send it the instant the event fires.
Trigger filter: Add a condition so the automation only runs for certain events. Because Growave sends event data with each event, you can filter on that data to target a narrower group.
Split: Branch the flow so different subscribers get different messages, or run an A/B test on wording, timing, or incentives.

For details on these steps, see Postscript's Guide to Automation Flows and Guide to Automation Flow Triggers and Trigger Filters.

Troubleshooting: my SMS stopped sending after the update

If SMS were sending before but stopped, the most likely cause is that the integration moved to the new custom-event API and your old trigger-based automations are no longer firing.

To fix this, rebuild each automation using the How to set up an SMS automation in Postscript steps above. Once a new Automation Flow is built on the matching Growave event and set to active, SMS will send again for that event.

If a specific automation is active but individual customers still don't receive the SMS, check that the customer is a subscriber in Postscript. Postscript matches each Growave event to a subscriber by phone number or email, and it can only send the SMS if it finds a matching subscriber who is opted in to your SMS messaging.

Customers who are not opted-in Postscript subscribers will not receive the message even when the automation is working correctly.

If you have any questions or need assistance with Postscript integration, please contact our support team at [email protected] or via the chat icon in the bottom-right corner. We are here to help! 🤗

Integrating Growave with Postscript