---
title: "Postscript Integration"
slug: "postscript-integration"
updated: 2026-02-18T15:33:51Z
published: 2026-02-18T15:33:51Z
canonical: "help.skio.com/postscript-integration"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.skio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Postscript Integration

## What is Postscript?

[Postscript](https://postscript.io/) is a marketing and transactional SMS platform that helps you reach customers through targeted text messages. It is designed to drive engagement, boost retention, and keep customers informed.

## How does the Postscript integration work with Skio?

When you connect Postscript to Skio, you can automatically send SMS notifications to subscribers based on subscription events such as upcoming renewals, successful charges, or skipped orders. These messages can be personalized to match your brand and configured to trigger at the right time to encourage action or reduce churn.

## How do I set up the Postscript integration in Skio?

### Step 1: Create your Postscript credentials

**Before you configure your Postscript integration, create credentials in Postscript.** You’ll use these credentials when connecting Postscript to Skio in a later step. Follow the steps in [Postscript’s guide for detailed instructions](https://help.postscript.io/hc/en-us/articles/14683733894555-Set-Up-Your-Skio-Integration#01GYBGDRSAFADXDQKVSTB37P8R).

### Step 2: Enable the Postscript Integration

1. In your **Skio dashboard**, go to **API & Integrations** > **Integrations**.
2. Find **Postscript** and click **Enable**.
3. In the setup modal, paste the private API key you generated in Postscript (Step 1).
4. Under **Test Event User**, enter the email address of a user with a configured phone number in Postscript. This user will receive test events.
5. Toggle the integration **On** to activate it.

## How to create an automation flow from Skio events in Postscript

You can trigger Postscript automation flows from Skio subscription events, such as upcoming renewals or skipped orders. These events are available in the **Automation Flows** page in Postscript.

To create an automation flow from a Skio event:

### Step 1: Set up the event in Skio

The event must be created in your Skio account before it can be used in Postscript.

1. In your Skio dashboard, go to **API & Integrations** > **Integrations**> **Postscript**.
2. On the **Postscript Integration** page, scroll to the **Events** section and click **Add event**.
3. From the list, choose the event you want to add. (See the list of supported Skio events below.)
4. Click **Add event** to confirm.

### Step 2: Create the Automation Flow in Postscript

1. In Postscript, go to **Messaging** > **Automations**.
2. Click **Create Automation** > **Create an Automation Flow**.
3. On the left side of the flow builder, under **Trigger event or property**, select the Skio event you want to use.
4. Apply any optional filters you need for targeting.
5. Click **Save** to finalize your automation.

Need help choosing the right trigger or filter? Check out [Postscript’s guide on automation triggers and filters.](https://help.postscript.io/hc/en-us/articles/6402078919323-Guide-to-Automation-Flow-Triggers-and-Trigger-Filters?_gl=1*cuy9y7*_gcl_au*NTEyMjMzMTI5LjE3NTQ5NDU1OTM.#01G5FJWJA485WY72RAYSE8AB8H)

**See all available event metrics**

### Core Subscription Lifecycle

| Event | Metric | Description |
| --- | --- | --- |
| New subscription created | ```plaintext subscriptionCreated ``` | When a new subscription is created. |
| Billing reminder notification | ```plaintext subscriptionWillRenew ``` | When a subscription is about to renew. |
| Subscription renewed | ```plaintext subscriptionRenewed ``` | When a subscription is successfully renewed. |
| Subscription cancelled | ```plaintext subscriptionCancelled ``` | When a subscription is cancelled. |
| Subscription reactivated | ```plaintext subscriptionReactivated ``` | When a subscription is reactivated. |
| Next billing date updated | ```plaintext subscriptionNextBillingDateUpdated ``` | When a customer updates a subscription’s next billing date. |
| Subscription paused | ```plaintext subscriptionPaused ``` | When a subscription is paused. |
| Subscription unpaused | ```plaintext subscriptionUnpaused ``` | When a subscription is unpaused. |
| Subscription skipped | ```plaintext subscriptionSkipped ``` | When a subscription is skipped. |

### Billing & Payment Issues

| Event | Metric | Description |
| --- | --- | --- |
| Billing attempt failed | ```plaintext billingAttemptFailed ``` | When Skio fails to renew a subscription. |
| Card expiration notification | ```plaintext cardWillExpire ``` | When a customer card is about to expire. |
| 3DS verification required | ```plaintext threeDSVerification ``` | When a payment requires 3DS verification. |

### Subscription Management

| Event | Metric | Description |
| --- | --- | --- |
| Subscription lines added | ```plaintext subscriptionLinesAdded ``` | When a subscription line(s) is/are added. |
| Subscription lines removed | ```plaintext subscriptionLinesRemoved ``` | When a subscription line(s) is/are removed. |
| Subscription lines updated | ```plaintext subscriptionLinesUpdated ``` | When a subscription line(s) is/are updated. |
| Subscription split | ```plaintext subscriptionSplit ``` | When a subscription is created from a split. |
| Subscription merged | ```plaintext subscriptionMerged ``` | When a subscription is cancelled from a merge. |
| Subscription mergeable | ```plaintext subscriptionMergeable ``` | When there’s subscriptions that can be merged together. |
| Subscription billing auto merged | ```plaintext subscriptionAutoMergedBilling ``` | When subscriptions are merged into a single order for billing. |

### Inventory & Stock

| Event | Metric | Description |
| --- | --- | --- |
| Subscription item out of stock | ```plaintext subscriptionOutOfStock ``` | When any item in a subscription is out of stock. |
| Item back in stock | ```plaintext oosMissedBillingBackInStock ``` | When an out of stock item missed in the previous billing is back in stock. |

### Customer Retention & Flow

| Event | Metric | Description |
| --- | --- | --- |
| Subscription that was saved during cancel flow | ```plaintext subscriptionWentThroughCancelFlow ``` | When a subscription is saved during the cancel flow. |
| Surprise and delight rule applied | ```plaintext surpriseAndDelightRuleApplied ``` | When a surprise product or discount is applied to a subscription. |
| Automation action ran | ```plaintext automationActionRan ``` | When an automation action is successfully ran on a subscription. |
| Journey notification triggered | ```plaintext journeyNotificationTriggered ``` | When a journey notification action is triggered. |

### Gifts

| Event | Metric | Description |
| --- | --- | --- |
| Prepaid gift received | ```plaintext prepaidGiftReceived ``` | When a prepaid gift is received for a recipient. |

### Loyalty & Credits

| Event | Trigger | Description |
| --- | --- | --- |
| Credits will expire | ```plaintext creditsWillExpire ``` | When customers' credits are about to expire in a given month |
| Credits expired | ```plaintext creditsExpired ``` | A customer's credits have expired |
| Credits received | ```plaintext creditsReceived ``` | A customer has received credits |
| Credits spent | ```plaintext creditsSpent ``` | A customer has spent credits |
| Loyalty tier upgraded | ```plaintext loyaltyTierUpgraded ``` | When customers' loyalty tier is upgraded |
| Loyalty tier downgraded | ```plaintext loyaltyTierDowngraded ``` | When customers' loyalty tier is downgraded |
| Loyalty tier changed | ```plaintext loyaltyTierChanged ``` | When customers' loyalty tier is changed due to program change |
| Loyalty rewards applied | ```plaintext loyaltyRewardsApplied ``` | When customers receive a loyalty reward |

> Learn more about [Skio’s event metrics here.](/help/docs/all-skio-event-metrics)

## Available Skio properties

Postscript receives the same Skio event payload that is sent to Klaviyo. This includes both:

- **Event properties:** Describe the specific subscription action that occurred (ie. subscription created or upcoming order)
- **Profile properties:**which are stored on the customer profile and persist over time. (ie. active subscription count or referral code)

See the full list of Skio event and profile properties [**Skio event and profile properties in Klaviyo**](/help/docs/skio-properties-sent-to-klaviyo).

> [!WARNING]
> Although this reference uses Klaviyo naming and examples, the same Skio properties are available in Postscript for use in segmentation, personalization, and messaging. The exact field names and locations may vary within Postscript.

---

### FAQ

#### Does the Postscript integration replace Skio SMS notifications altogether?

**Postscript can replace some or all Skio SMS notifications.** However, it cannot replace **SkioSMS**. If you keep SkioSMS enabled, messages from that tool will still send from your store’s assigned phone number.

#### How do Postscript notifications differ from Skio SMS notifications?

**Postscript can send transactional messages, but it is primarily designed for marketing and requires the customer’s opt-in.** Because of this, some subscribers may not receive texts through Postscript, even if their phone number is on file in Skio.

**SkioSMS** is a transactional messaging tool, meaning it sends order- and subscription-related notifications without requiring marketing opt-in. It supports two-way texting, so your customers can manage their subscriptions directly from their phones. Messages will send to any subscriber with a phone number on their account, ensuring delivery for critical updates.

#### Why don't I see the event metric in Postscript?

Postscript only displays an event metric after it receives a webhook from Skio. If you're setting up a new event, click **Test event** in Skio to fire the webhook immediately. This should push the metric into Postscript right away.

If the metric still doesn't appear, double-check that the event is added in your Skio settings.

#### How can subscribers skip their next order by text with Postscript?

Subscribers can text `SKIP` to your Postscript number to skip their next subscription order.

You can pair this with the **Billing reminder** notification to offer customers an easy way to avoid an upcoming charge. For example, your Postscript automation could say:

```plaintext
Your subscription will renew in 3 days.  
Reply SKIP to skip your next order.
```