Shopify Flow Triggers — Sublyra Developers

1. How it works

Shopify Flow is Shopify's built-in automation tool: a workflow starts from a trigger, optionally checks conditions, then runs actions (tag customers, add order tags, send emails, call webhooks, and more). Sublyra provides four triggers, so subscription events can start any workflow you build — without standing up an endpoint.

1 In your Shopify admin, open Flow and create a workflow.

2 As the trigger, search for Sublyra — you'll find the four triggers listed below.

3 Add conditions and actions. Every trigger provides the customer as a Flow resource (so actions like Add customer tags work directly) plus context fields you can use in conditions and message templates.

Nothing to configure in Sublyra. The triggers fire automatically when the underlying event happens and a workflow using them exists. If no workflow uses a trigger, firing it is a harmless no-op — and a Flow hiccup never delays the subscription event itself.

Plan availability. The Flow connector is part of the API & webhooks toolkit: Pro plan, or the API & webhooks add-on ($19.99/mo).

2. Subscription created

Starts a workflow when a new Sublyra subscription contract is created — a customer just subscribed at checkout.

Field	Type	Example
Customer	customer	The subscriber, as a Flow customer resource.
Contract ID	single line text	`gid://shopify/SubscriptionContract/1001`
Interval	single line text	`MONTH` (also `DAY` or `WEEK`)
Next billing date	single line text	ISO date of the next scheduled billing; empty if none is set.
Selling plan ID	single line text	The selling plan gid the contract belongs to.

3. Subscription cancelled

Starts a workflow when a Sublyra subscription contract is cancelled — by the customer, by you, or after failed payments run their course.

Field	Type	Example
Customer	customer	The former subscriber, as a Flow customer resource.
Contract ID	single line text	`gid://shopify/SubscriptionContract/1001`

4. Billing attempt failed

Starts a workflow when a Sublyra renewal charge is declined. It fires on each declined attempt, so use the Attempt number in a condition if you only want to act on the first decline or the final one.

Field	Type	Example
Customer	customer	The subscriber whose card was declined.
Contract ID	single line text	`gid://shopify/SubscriptionContract/1001`
Attempt number	single line text	`2` — how many times this order has been attempted.
Decline reason	single line text	`insufficient_funds` — a normalised reason string.

Sublyra's dunning is already working. Failed payments are retried automatically with reminder emails before this trigger is useful to you — think of the trigger as the way to add your layer on top: an internal heads-up, a tag for your support team, a personal email from the founder on high-value contracts.

5. Streak milestone reached

Starts a workflow when a subscriber crosses a streak milestone you've configured in Sublyra — for example "6 renewals in a row".

Field	Type	Example
Customer	customer	The subscriber who hit the milestone.
Contract ID	single line text	`gid://shopify/SubscriptionContract/1001`
Milestone	single line text	The milestone label from your streak rule.
Cycles completed	single line text	`6` — renewals completed when the milestone was reached.

6. Workflow ideas

Trigger	Condition	Action
Subscription created	—	Add customer tag `subscriber` so your theme and email segments can recognise members.
Subscription created	Interval equals `MONTH`	Send an internal email to your fulfilment team with the new subscriber's details.
Billing attempt failed	Attempt number equals `1`	Add customer tag `payment-failing` for a support follow-up list.
Subscription cancelled	—	Remove the `subscriber` tag and add `win-back-target`.
Streak milestone reached	Milestone equals `12 renewals`	Send a celebration email or notify your team to include a surprise gift in the next box.

Need the data outside Shopify instead? The same lifecycle events are available as outbound webhooks to your own endpoint, and current state via the REST API.

7. FAQ

Do I need to register anything to use the triggers?

No. Once Sublyra is installed, its triggers appear in Flow's trigger picker — search for "Sublyra". There's no key, no endpoint and no settings page for Flow.

Why didn't my workflow run?

Check three things: the workflow is turned on in Flow; the event actually happened (a contract created, a charge declined); and any conditions you added actually matched. Sublyra fires every trigger best-effort, and a shop with no matching workflow is a normal no-op.

Can a workflow slow down checkouts or renewals?

No. Trigger emission is fire-and-forget — it happens after the real work (contract creation, billing attempt) is already done, and a Flow error can never fail the subscription event.

How is this different from the outbound webhooks?

Flow triggers stay inside Shopify and need no code; outbound webhooks deliver signed JSON to any endpoint you run. Use Flow for tagging, notifications and Shopify-native actions; use webhooks when your own systems need the event.