Postscript integrates with Whym through Zapier and webhooks. Whym gives shoppers a way to remember great products. It also gives sellers the tools and insights they need to understand what their shoppers want, when they want it. With our Whym integration, brands can:
- Consolidate all first-party data by reducing the number of apps, widgets, integrations, and subscriptions you're managing with one tool.
- Segment and scale personalization by leveraging first-party data to re-market products to high-intent shoppers.
- Update subscriber profiles when you create new subscribers, tag subscribers, and track custom events.
In this article, we'll walk you through how to complete the integration set up in Zapier, Whym, and Postscript.
Generate Your Webhook with Zapier
In this section, we'll walk you through how to generate the webhook URL that you will add to your Whym account and kick off the creation of your Zap.
- Log in to your Zapier account (Note: Zapier professional account or higher required)
- Create a new Zap
- Select Webhooks by Zapier as your Trigger
- Select Catch Hook as the Event
- Under Set up trigger, leave Pick off a Child Key blank
- Copy Your webhook URL
Add Your Webhook in Whym
In this section, we'll walk you through how to add the webhook URL you generated previously to your Whym account.
- Log into your Whym account
- Click on Settings' -> Integrations
- Select Install next to Webhook
- Paste your webhook URL from Zapier
- Select post for webhook methods
- Leave Authorization Headers blank
- Click Add your webhook
Create a Postscript API Key
In this section, we'll walk you through how to generate the Postscript API key you will add to Zapier in step four, later in this article.
- Select your Shop Name in the side menu of your Postscript dashboard, then select API.
- Select Create Security Key Pair on the right side of the page, then confirm your action by selecting Yes.
- Add a label to your API key so you can track where this API key is being used.
- Select Show in the Private Key column to reveal your API key. Copy this key or write it down—you'll need to enter it in Zapier later.
Create a Postscript Keyword
To properly configure the integration, you'll need to generate a keyword that you'll enter into Zapier later. In this section, we'll walk you through how to create a keyword
- Select Acquisition in the side menu of your Postscript dashboard, then select Keywords.
- Select Create Keyword in the top-right corner of the page.
- Name your keyword. Aim for something that will allow you to easily identify that this keyword is associated with your Whym integration.
- Select Save Keyword.
- You can customize your keyword reply and add additional actions via + Add Action if desired.
- Be sure to activate your keyword before adding it in Zapier.
Build Your Zap
In order to create a successful integration between Postscript and Whym, the following 15 steps should be followed.
-
Navigate back to the Zap you created in the Generate Your Webhook with Zapier section above
- In order to complete the integration setup successfully, you will need to build your zap with the steps shown below. In the following sections, we will do a deep dive into all fifteen steps.

Step 1: Set Up Zapier Trigger
In order to properly set up the integration to catch the hook in webhooks by Zapier, please enter the URL you generated from the Generate Your Webhook with Zapier section above.

Step 2: Filter: Only Continue If
This step filters out other events that could mistakenly trigger your zap.
- Select the dropdown under Only continue of... and choose Name.
- In the middle drop-down, select (Text) Contains.
- In the third dropdown, please select the value Text Me This Item.

Step 3: Formatter by Zapier
This step is used to transform the number into the format accepted by Postscript.
- Under Action, select Transform phone number.
- Under Values, choose 1. Phone Number for the Input field.
- In the To Format field, enter 15558001212 (No Symbols, International).
- In the Phone Number Country Code field, choose United States.
- In the Validate Phone Numbe field, choose Yes.

Step 4: Find Subscriber in Postscript
This step is used to create the paths in the subsequent for Existing vs New Subscribers.
- Enter Postscript in the Action field.
- Select your first Action Event (Find Subscriber) and select Continue.
- Next, connect your Postscript account. A pop-up will appear and ask you to enter your Postscript Private API Key (Note: the API key used in this gif is a dummy key used for illustration purposes).
- Under the Action tab, select Output in the Phone Number field.
- Please leave the Shopify Customer ID blank.
- For the Should this step be considered a "success" when nothing is found, please choose Yes.

Step 5: Paths
In this section, we'll create new paths. One path for new subscribers and a separate path for existing subscribers. In the graphic shown above, you'll notice this is where the zap branches.

Step 6: Path Rules for Existing Subscribers
In this section, we'll set up the path rules for existing subscribers.
- Under the Rules setup & testing tab, find the dropdown under Only continue if.
- Choose 4. Zap Search Was Found Status.
- For the following value, choose (Boolean)is true.

Step 7: Create Custom Event in Postscript
This step creates a custom event in Postscript that will be used to trigger your automation. In each field, please choose the following values:
- Event Name = WHYM_TMTI
- You can include a Version or other identifying characters in the Event Name
- Subscriber ID = 4. ID
- This will be an 's_###" shown in the test data (this is the Postscript Subscriber ID)
- External ID = leave blank
- Properties - build the following three properties
- Property 1:
- Name: Productname
- Value: 1. Product Name
- Property 2:
- Name: ProductURL
- Value: 1. Texted Products Product Url
- Property 3:
- Name: Creationsource
- Value: 1. Creation Source
- Property 1:

Step 8: Update Subscriber in Postscript
This step will update the existing subscriber record in Postscript with customized tags. Please use the following parameters and values:
- Subscriber ID = 1.ID:
- Email = leave blank
- Tags - include the following tags:
- 1.Texted Products Creation Source
- WHYMTMTI
- 1. Product Name

Step 9: Path Rules for New Subscribers
In this section, we'll set up the path rules for new subscribers.
- Under the Rules setup & testing tab, find the dropdown under Only continue if.
- Choose 4. Resource.
- For the following setting, choose (Text) Does not exactly match.
- In the final value, please add the value subscriber.
Step 10: Create Subscriber in Postscript
This step creates a new subscriber record in Postscript. Please use the following parameters and values for this step:
- Phone Number = 1. Phone Number
- Keyword = WHYMTMTI
- Note: This keyword was created in the CREATE A NEW KEYWORD IN POSTSCRIPT section above
- Origin = other
- Shopify Customer ID: leave blank
- Email: leave blank
- Tags:
- 1.Texted Products Creation Source
- WHYMTMTI
- 1. Product Name
- Custom Properties = leave blank

Step 11: Delay by Zapier
This step creates a delay that allows new subscribers time to confirm their opt in. Please note that the minimum amount of time recommended is 12 hours. To learn more about Confirmed Opt-In, see here.
- Under the Action tab, please add the number 2 for the Time Delay For (value) field.
- In the Time Delayed For (unit) dropdown, please add days.

Step 12: Find Subscriber in Postscript
This looks up the new subscriber to check if they have Replied Y and are now opted in. Please use the following values and parameters for this step:
- Phone Number = 3. Output
- Shopify Customer ID = leave blank
- Should this step be considered a "success" when nothing is found = No

Step 13: Filter: Only Continue If
This stops the zap if a shopper has not Replied Y and are subscribed. Please use the following parameters and values:
- Only continue if = 12. Subscriptions Promotional Can Send
- (Boolean) is true

Step 14: Create Custom Event in Postscript
This step creates a custom event in Postscript that will be used to trigger your automation.
- Event Name = WHYM_TMTI
- You can include a Version or other identifying characters in the Event Name
This MUST be the same as the Event Name you put in STEP 7 above - Subscriber ID = 12. ID
- This will be an 's_###" shown in the test data (this is the Postscript Subscriber ID)
- External ID = leave blank
- Properties - build the following three properties
- Name: Productname
- Value: 1. Product Name
- Name: ProductURL
- Value: 1. Texted Products Product Url
- Name: Creationsource
- Value: 1. Creation Source
- Name: Productname

Step 15: Finalize and Ensure Activation on All Apps
- In Zapier, test all of your steps.
- Also in Zapier, be sure your zap is published and activated.
- In Postscript, be sure to activate your keyword.
- In Whym, please ensure your Webhook integration is turned on and connected to Zapier.
- Also in Whym, please confirm your Text Me This Item (or VBB) button is active on your website.
Create a Whym-Triggered Automation in Postscript
- Select Messaging in the side menu of your Postscript dashboard, then select Automations
- Select Create Automation in the top-right corner of the page.
- Choose Automation Flow as your flow type.
- Select Create a new automation, then select the Create Flow button.
- Select the Automation Properties card on the left side.
- Under Trigger event or property, select Zapier - Event Name (Note: the event name is the name you put in Step 4 & 7 above in the Build Your Zap section).
- Set your Entry filter. We recommend setting this to 7 to 30 days. This will limit how often a subscriber can enter this automation.
- Set your Cancellation trigger to Order Created. This will remove a subscriber from your automation flow when they purchase.
- Click Save to save the automation properties.
- Add your preferred follow up messaging steps
- Click Schedule or Activate and activate your automation.
Data Overview
The following data is available in Zapier for each Text Me This Item (TMTI) event.
Data | Value Example | Description |
name | Sarah | The shopper's name |
textedProducts | 1 | The number of products texted to the subscriber |
creationSource | TMTI button or Visual Browsing Bookmark VBB | Whym feature used |
phoneNumber | +18881231234 | The shopper's phone number |
sarah@gmail.com | The shopper's email | |
productName | hydrating moisturizer | The name of the product |
productVariantName | large |
The name of the product variant (if known) |
productPrice | 14.5 |
The price of the product or variant (if known) |
productImage | https://cdn.shopify.com/s/files/1234 |
The image URL of the product or variant (if known) |
productUrl | https://yourshopname.com/products | The URL of the product page |
Get Support
Have questions? Please feel free to reach out to our wonderful Support team at support@postscript.io or via live chat. You can also submit a support request here!
Need ongoing channel strategy guidance? Please fill out this form and we'll connect you to one of our certified partners.