shopify flow

Use Badgy with Shopify Flow

Learn how to use Badgy with Shopify Flow with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Badgy exposes launch, normal end, and Early revert actions to Shopify Flow when entitled. Workflows invoke the same validated background operations as the admin and should be tested on a controlled campaign.

Before you begin

A compatible Badgy plan entitlement
Shopify Flow installed and permission to edit workflows
A stable campaign identifier and safe test campaign

Confirm the shop, current status, and intended consequence before changing anything. Use read-only status, preview, or history evidence first.

Step-by-step setup

Use Badgy with Shopify Flow shown in the Badgy admin, with numbered callouts for the controls and verification points described below. — Annotated Juniper & Trail example

Check the current plan before configuring plan-dependent integrations.
Confirm the store timezone used when interpreting campaign automation timing.
Review plan-gated Shopify integrations and their availability for this store.

Open Shopify Flow workflow editor for the intended shop and confirm the current record and status.
With Pro entitlement, choose Badgy Launch campaign, End campaign, or Early revert campaign and supply the stable Campaign ID field.
Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
Run a controlled workflow and inspect both Flow run response and Badgy status/History.
Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.

Badgy exposes launch, normal end, and Early revert actions to Shopify Flow when entitled. Workflows invoke the same validated background operations as the admin and should be tested on a controlled campaign.

Juniper & Trail example

Juniper & Trail tests use badgy with shopify flow against a controlled campaign, then confirms both the Flow run and Badgy audit trail before enabling the workflow. The documentation fixture uses realistic products, inventory states, variants, collections, and protected exclusions so the preview exercises the same decisions as a merchant catalog.

What shoppers will see

Flow changes when Badgy receives a command, but the same background activation and revert phases still determine storefront timing. Check the relevant result from product through cart where applicable. For shopper-facing work, compare desktop and mobile and verify both an eligible and an ineligible item.

Common mistakes and troubleshooting

Acting on the wrong shop. Confirm the Shopify store and campaign before following Use Badgy with Shopify Flow.
Trusting a stale preview. Refresh after catalog, schedule, discount, theme, locale, or market changes.
Repeating a background command. Read status and History first; retry only when Badgy presents a recoverable failure.
Skipping the consequence check. Confirm what changes for shoppers and what the end or restore path will do.

If the status reports revoked authorization, reconnect Shopify before retrying. If the result still differs from the preview, preserve the campaign ID and approximate time, then open support from this identified shop. Never send customer data, access tokens, or full catalog exports in feedback.

Launch a campaign from Shopify Flow

Options reference

| Option | Use it when | Consequence | | --- | --- | --- | | Launch | DRAFT campaign | Queues normal launch | | End | ACTIVE campaign | Queues normal full end | | Early revert | ACTIVE urgent stop | Queues priority early revert |

Badgy behavior in this guide is reviewed against the repository's shipped UI, service rules, and feature design documents. Shopify-owned theme, Markets, Flow, billing, and discount behavior can also depend on the store's Shopify configuration; consult the Shopify Help Center for that platform configuration.