STEP 1
Select Postscript in workflow
Pick Postscript app in the workflow builder [4] - just one click to select the app.
Postscript Integration
SMS marketing automation for ecommerce brands on Shopify. Use Postscript as a communication layer for triggering workflows and sending context where it belongs. Start from Watch Events, then follow with Get a Message or Get a Message Request.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Postscript integration
Triggers can detect changes in Postscript and run actions that can create, search or modify data inside Postscript automatically [3] — exactly how you set them.
- Watch EventsTriggers when a specified event occurs.
- Get a MessageRetrieves a message by given id.
- Get a Message RequestRetrieves a message request by given id.
- Get a SubscriberRetrieves a subscriber details by id.
- Search SubscribersSearches for subscribers by specified criteria.
- Create a SubscriberCreates a new subscriber.
- Make an API CallPerforms an arbitrary authorized API call.
- Send a MessageSends a message to a contact.
- Update a SubscriberUpdates an existing subscriber by id.
How to integrate Postscript in automation workflow?
3 simple steps to make your Postscript connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
STEP 2
Connect Postscript
When prompted, authorize access to Postscript in WEXTL once. Postscript credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your Postscript account. Approve?
STEP 3
Build a workflow
Build your workflow with Postscript yourself or with WEXTL® AI Builder. Connect Postscript to any available integrations [5], or use HTTP node to go beyond them.
Postscript
How Postscript connects and integrates with WEXTL
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever Postscript app is called in workflows. That allows your communication automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that Postscript supports.
The following table illustrates what fields Postscript integration require during authorization flow inside our workflow builder [4].
Connect Postscript
API Key*Text
••••••••
Demonstration of Postscript connection step inside WEXTL Workflow Builder [4].
| Field | Type | Help |
|---|---|---|
API KeyRequired | password | Be sure to request your partner keys from the team. Request your API keys here. |
Connect Postscript to popular apps on WEXTL
Enter a name of the other app you want to sync with Postscript below. Click on selected app to explore integration options with Postscript. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Example automation with Postscript integration
Select Watch Events trigger from Postscript - this will be a starting point in your automation. Whenever event happens in Postscript, workflow will start [7] from Watch Events node.
Search for Create a Subscriber, connect it as the next step of integration sequence. You can use filters between Watch Events and Create a Subscriber, so only important data pass from Watch Events to the next step. WEXTL gives you full control over the process of Postscript automation. All parts of workflow are visible on the canvas [4].
Postscript on WEXTL has 9 modules for combining communication automations. Explore Postscript documentation for more.
Video slide demonstrates how Watch Events and Create a Subscriber [6] nodes are used in Postscript workflow.
Frequently asked questions
Common questions about automating Postscript in your workflows.
Postscript has 1 trigger, including "Watch Events". Triggers are start points of the workflow, and automations may start from them.
Integration has 8 actions, including "Get a Message", "Get a Message Request", and "Get a Subscriber", and more. Refer to our Postscript Documentation for detailed inputs and outputs.
No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].
Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.
The Postscript integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by Postscript official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.
Absolutely. Where Postscript provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever Postscript or any other service sends event to webhook URL.
WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for Postscript inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with Postscript modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.
References
List of sources used to gather information about the Postscript integration.
- Postscript integration source code, module specs and credentials implementation.
- Internal Postscript integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Postscript vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® Postscript App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation