All integrationsMarketing Automation
Postscript
Grow and text your Shopify store's SMS subscribers in Postscript: add, find, tag and opt out subscribers, text them, send events to flows, and start workflows when someone opts in, opts out or texts the shop.
- actions
- 20
- triggers
- 5
Triggers
Start a workflow when something happens in Postscript.
- Subscriber opted inRuns when someone confirms they want the shop's marketing texts and becomes a subscriber. Subscribers who joined before the workflow is turned on don't start it.
- Subscriber changedRuns when a subscriber changes, such as new tags, properties or an opt-out, and when one joins. Changes made before the workflow is turned on don't start it.
- Subscriber opted outRuns when a subscriber stops the shop's texts, such as by replying STOP. Postscript tells Lodol through a webhook Lodol sets up for you.
- Incoming textRuns when someone texts the shop. Keyword sign-ups and opt-in or opt-out replies may not start it. Postscript tells Lodol through a webhook Lodol sets up for you.
- Email collectedRuns when a Postscript popup collects someone's email, whether or not they also sign up for texts. Postscript tells Lodol through a webhook Lodol sets up for you.
Actions
Steps a workflow can run in Postscript.
- Get connected shopGet the Postscript shop the connection acts for: its id and name.
- List subscribersList the shop's SMS subscribers, filtered by email, phone, Shopify customer or when they joined or changed. Gets one page; run it again with the next page number to see more.
- Find subscriberLook up a subscriber by phone number (in any format) or email. Says whether one was found instead of failing.
- Get subscriberGet one subscriber with their tags, properties and whether the shop may text them promotions or order updates.
- Add subscriberSign a phone number up to the shop's texts through a keyword. Only add people who agreed to get marketing texts: Postscript texts them to confirm and adds them only once they reply. Until then the id returned is a pending one.
- Update subscriberAdd tags, set custom properties or give a subscriber an email. Tags only add, other properties are kept, and an email is saved only if they have none yet.
- Unsubscribe subscriberOpt a subscriber out of the shop's texts, by id or phone number, for example when they ask you to stop texting them.
- Erase subscriber dataErase a person's data from Postscript for a privacy request, found by id, phone, email or Shopify customer. It opts them out too and can't be undone.
- List keywordsList the shop's active keywords, the words people text in to sign up, with how often each was used.
- Get keywordGet one keyword with how many times it was texted in.
- Send text messageText one existing subscriber who agreed to get the shop's texts. Postscript starts it with the shop's name, and holds a promotional text until the subscriber's waking hours.
- Get message requestCheck a text sent with 'Send text message': its status, and the sent text once Postscript has sent it.
- Get sent messageGet a text Postscript sent, with what it said and the credits it used.
- Send custom eventSend an event, such as QuizCompleted, that Postscript flows can start from or wait for, tied to a subscriber by id, phone or email.
- List webhooksList the shop's webhooks: which event each sends, and where.
- Get webhookGet one webhook with its event, address and headers.
- Create webhookHave Postscript send one kind of event, such as a subscriber opting in, to an https address you have.
- Update webhookChange where a webhook sends, or add or change its headers. The headers not named are kept.
- Delete webhookDelete a webhook so Postscript stops sending to it.
- Send test webhookHave Postscript send made-up data to every webhook of the shop for one event, to check the address receives it.
No actions match that.
Automate Postscript with Lodol.
Connect Postscript, then hand Lodol the job in Slack, Claude or ChatGPT.
We’re letting people in a few at a time.