shopify flow
Launch a campaign from Shopify Flow
Learn how to launch a campaign from Shopify Flow with a safe Juniper & Trail example, shopper impact, options, and recovery checks. The launch action accepts an eligible campaign reference and still enforces completeness, status, conflicts, and entitlement. A successful Flow step means the command was accepted; monitor Badgy for activation completion.
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 the summary cards to check live, scheduled, and sale-product totals.
Inspect the active campaign and use its view, edit, revert, or end actions.
Check theme embed, badge, banner, background-job, and countdown health.
Search and filter past campaigns before opening their records.
- Open Shopify Flow → Badgy Launch campaign action for the intended shop and confirm the current record and status.
- Set Campaign ID for a complete DRAFT campaign; signed duplicate delivery to SCHEDULED/ACTIVE is a safe 200 no-op, while missing/wrong-shop/terminal input is a permanent 4xx.
- Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
- A 200 accepted response means launch was queued, so monitor Badgy for completion; transient infrastructure 5xx may be retried by Flow.
- Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.
The launch action accepts an eligible campaign reference and still enforces completeness, status, conflicts, and entitlement. A successful Flow step means the command was accepted; monitor Badgy for activation completion.
Juniper & Trail example
Juniper & Trail tests launch a campaign from 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 Launch a campaign from 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.
Related guides
Options reference
| Option | Use it when | Consequence | | --- | --- | --- | | DRAFT | Valid launch input | Jobs enqueue | | SCHEDULED/ACTIVE | Duplicate/late delivery | 200 no-op | | Terminal/invalid | Cannot launch | 4xx no retry | | Infrastructure failure | DB/Redis unexpected error | 5xx retry |
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.