> For the complete documentation index, see [llms.txt](https://docs.subrise.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subrise.app/guide/settings/integrations/shopify-flow.md).

# Shopify Flow

<figure><img src="/files/ILzfFVwG4zbRgIIkp8vB" alt=""><figcaption><p>In this example the Merchant can Add custom tags when a subscription is paused, and the pause reason = "Too Expensive"</p></figcaption></figure>

## How Do I Use It?

The two main components of Shopify Flow are Triggers and Actions. Shopify comes with a ton of they're own custom triggers and actions, and we at Subrise also have created our own custom ones as well that will work with Shopify's. When a Trigger occurs (New Subscription) you can assign that trigger a Action (Tag Customer, or Send an Email, or Add Or Remove Certain Products)

## Subrise Triggers

When the following triggers below happen on your shop they will send subscription data, to the action you have assigned it in the Shopify Flow Workflow.

### Cancelled Subscription

This Trigger will fire off an action when a subscription is cancelled.

### Failed Billing

This Trigger will fire off an action when a subscription billing fails.

### New Subscriber

This Trigger will fire off an action when your shop gets a new Subscriber.

### New Subscription

This Trigger will fire off an action when your shop gets a new Subscription.

### Paused Subscription

This Trigger will fire off an action when a subscription is paused.

### Prepaid Subscription

This Trigger will fire off an action when a prepaid subscription has been created.

### Subscription Resumed

This Trigger will fire off an action when a subscription is resumed.

### Subscription Addons

This Trigger will fire off an action when a Add-On has been added to a subscription.

### Subscription Modified

This Trigger will fire off an action when a subscription has been upated/modified by either the admin or a customer.

### Successful Payment

This Trigger will fire off an action when a subscription has been billed successfully.

### Upcoming Subscription

This Trigger will fire off an action when a subscription will be billed within 48 hours.

## Subrise Actions

These are only the actions we offer custom from our app, but Shopify Flow has hundreds of built-in actions to perform various tasks in your shop. We recommend looking at the Shopify Flow docs to get a larger idea of what's capable. If you can imagine it, it's probably possible.

{% embed url="<https://help.shopify.com/en/manual/shopify-flow/reference/actions>" %}

### Add Subscription Line Item

This Action will add a variant to a Subscription.

### Cancel Subscription

This Action will cancel a subscription contract.

### Pause Subscription

This action will pause a subscription contract.

### Remove Line Item From Subscription

This action can remove a Line Item from a subscription contact.

### Resume Subscription

This action can Resume a subscription contract.

### Run Billing Now

This action will run billing on a subscription contract.

### Set Next Billing Date

This action will set the billing date on a subscription to a new date of your choosing.

### Skip Next Billing Date

This action will skip the billing, and not run till the next billing date.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.subrise.app/guide/settings/integrations/shopify-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.