Your App Has No Flow Connector: Build the Bridge or Wait?
A missing Flow connector is a DEPENDS that turns on direction. Shopify's docs call an app's own triggers and actions tasks, and only that app's developer can ship them, so no merchant setting makes a vendor app appear in Flow. Outbound needs nothing: Send HTTP Request covers Grow, Advanced and Plus. Inbound needs a bridge app from $29/month (verified Sep 2026) or your own trigger task.
Your profile — see how the verdict shifts
- Confidence
- Medium — Read Shopify's Flow developer overview: a developer integrates an app with Flow through custom tasks, such as triggers and actions, a Partner builds one or more tasks related to their own app, and merchants need both that app and Flow installed (verified Sep 2026). Read the trigger extensions page: the documented route is a trigger extension defined in a TOML file inside an app, with your system calling the Shopify API with the trigger payload. That page describes no generic, merchant-configurable inbound-webhook trigger, and none appears elsewhere in the Flow docs, which is why three separate App Store apps exist to bridge the gap. Confidence is Medium rather than High on that second point specifically: it rests on documented absence plus the existence of those bridge apps, not on a single Shopify sentence saying so. Fetched all three bridge listings: Workflow Webhooks carries 5.0★ across 6 reviews, Flow Plus 5.0★ across 5, and FlowRelay has no reviews yet. All three are Built for Shopify, and all three are young listings. The Flow help page confirms Flow is free on Basic, Grow, Advanced and Plus, Send HTTP Request is available from Grow upward, and only Plus stores can use tasks created by custom partner apps. Build bands are Deploi estimates.
- Reference scenario
- $20M–$200M GMV · Shopify Plus · 25–60 installed apps including an ERP, a 3PL and a loyalty platform · one mission-critical vendor with no Flow tasks · ops team that builds in Flow's editor
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Outbound only: Flow has to tell the vendor something happened | WAIT | Nothing is missing. Send HTTP Request posts to the vendor's endpoint on Grow, Advanced and Plus, waits up to 30 seconds for a response code, and retries 4XX, 5XX and 429 responses for up to 24 hours. An optional Run code step parses the body. |
| Inbound on Basic, Grow or Advanced | BUY | Tasks created by custom partner apps run on Plus only, so writing your own trigger is not an option here. A public bridge app from the App Store is the practical route, starting at $10/month on Flow Plus or free up to 500 events a month on FlowRelay (verified Sep 2026). |
| Inbound on Plus, vendor app you don't control | BUY | You cannot make someone else's app expose tasks, and asking them puts your roadmap on their backlog. A bridge app converts the vendor's outbound webhook into a Flow trigger from $29/month on FlowRelay Starter or $35/month on Workflow Webhooks Grow (verified Sep 2026). Thin review depth is the real cost here. |
| Inbound on Plus, and the app is yours (internal tool or custom app) | BUILD | The one case where the gap is genuinely yours to close. A trigger extension defined in your app's TOML, with your service calling the Shopify API with the trigger payload, puts the event in Flow's editor next to Shopify's own at $7,000–$22,000 (Deploi estimate, illustrative). |
What Flow Connector Gaps Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | A vendor event that lands as a Flow trigger lets the ops team tag, notify, hold or route orders in the editor they already use, instead of filing a ticket for every rule change. |
| Customer experience | Medium | Automation that fires the moment a 3PL or loyalty event lands keeps holds, notices and credits timely, where a nightly reconciliation job leaves the customer waiting until morning. |
| Data & insight | Medium | Every bridged event can be logged on the way through, giving you a record of vendor activity that outlives Flow's 14-day run retention. |
| Revenue — indirect | Low | Faster reaction to vendor events recovers a modest share of at-risk orders, though the gain is a lift on existing workflows rather than a new revenue line. |
Spend ceiling: Size the spend to how often the missing event actually fires. A vendor event that lands twice a day belongs on a free tier of 500 events a month and nothing more. A trigger extension at $7,000–$22,000 (Deploi estimate, illustrative) earns its place only when you own the app, when named fields save the ops team real work, or when a category whose deepest listing has 6 reviews is too thin to trust.
What buying enables (top apps)
- + An inbound vendor event usable in Flow the same afternoon, with no app to write or submit for review
- + Free tiers of 500 events a month on two of the three listings, enough to prove the workflow before paying
- + Built for Shopify status on all three bridges, which sets a baseline for performance and listing quality
- + Event ceilings up to 1,000,000 a month on FlowRelay Scale for high-volume vendor feeds (verified Sep 2026)
What building additionally unlocks
- + Named trigger fields your ops team picks from a list, instead of raw JSON parsed inside every condition
- + No per-event meter between your own systems and Flow's editor
- + An event log you control, with idempotency keys, outliving Flow's 14-day run retention
- + One app whose tasks appear in every store of a Plus organization that installs it
Find Your Verdict in 3 Questions
Does Flow only need to tell the vendor something, rather than react to it?
Yes: Your verdict: WAIT — Send HTTP Request already covers outbound calls on Grow, Advanced and Plus, with retries for up to 24 hours and nothing to install.
No: Go to question 2.
Do you control the app on the other side, as an internal tool or a custom app of your own?
Yes: Go to question 3.
No: Your verdict: BUY — a webhook bridge from $29/month on FlowRelay Starter or $35/month on Workflow Webhooks Grow (verified Sep 2026) is the only lane that does not depend on someone else's roadmap.
Do your ops staff need named trigger fields to build conditions against, rather than raw JSON from a generic payload?
Yes: Your verdict: BUILD — a trigger extension declared in your app's TOML costs $7,000–$22,000 (Deploi estimate, illustrative) and puts named fields in Flow's editor.
No: Your verdict: BUY — a bridge app carries the same event for a fraction of the cost, and you can build the trigger later.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A bridge app installs and points at a webhook URL in an afternoon; a trigger extension in your own app is a 3–6 week build at $7,000–$22,000 (Deploi estimate, illustrative). | ||
| Recurring fees | Bridge apps meter by event: FlowRelay runs $29–$199/month and Workflow Webhooks $35–$100/month for as long as the automation exists (verified Sep 2026). A trigger task you own has no subscription line, and Flow itself is free. | ||
| Maintenance & upgrades | The bridge vendor absorbs Shopify's quarterly API version changes; your team absorbs them for a custom app, plus every change the vendor makes to its outbound payload shape. | ||
| Switching & exit | Uninstalling any app removes its tasks from Flow's editor, so workflows built on a bridge break the day you leave it. The workflows themselves stay, which makes rebuilding a rewiring job rather than a rewrite. | ||
| Risk | |||
| Vendor risk | The three bridge listings carry 6 reviews, 5 reviews and none at all (verified Sep 2026), so this category has no established incumbent; a task in your own app depends only on Flow, which Shopify ships free from Basic upward. | ||
| Security & compliance surface | A bridge app receives your vendor's event payloads in a third party's cloud before Flow ever sees them; a trigger task in your own app keeps that hop inside infrastructure you already secure. | ||
| Platform-deprecation exposure | Both lanes ride the same Flow task platform, which carries no sunset notice as of September 2026. The vocabulary has moved, though: Shopify's current docs say tasks where older material said connectors. | ||
| Value | |||
| Fit to requirement | A bridge gives you one generic trigger carrying a raw payload, so conditions get written against JSON fields; a purpose-built trigger exposes named fields your ops team can pick from a list. | ||
| Time to market | Same day against 3–6 weeks (Deploi estimate, illustrative), and the free tiers let you prove the workflow before committing to either lane. | ||
| Performance & scale | Event caps bite first on the bought lane: 500 events a month free, 15,000 on Workflow Webhooks Grow, 25,000 on FlowRelay Starter (verified Sep 2026). A trigger you own is bounded by Flow's own limits instead. | ||
| Data ownership & AI-readiness | Flow keeps run history for 14 days in both lanes; the build lane also lets you log every inbound event into your own warehouse on the way through, where a bridge keeps its history in its own dashboard. | ||
| Focus & opportunity cost | Writing an app extension to work around a vendor's roadmap gap is rarely the best use of a dev bench unless you already own that app. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify Flow | Native — Per july 2026 research. Shopify's own automation layer — the WAIT option to exhaust first | Free at entry volumes; scales with volume (verified Sep 2026) | Every outbound automation, where the missing connector turns out not to matter |
| Workflow Webhooks | Live — flagged — 5.0★ across 6 reviews; Built for Shopify. Turns an inbound webhook into something Flow can start from. Six reviews is a young listing for a component that sits in the path of a mission-critical vendor event, so treat the free tier as a pilot rather than a trial period. | Free (500 webhook invocations/month); Grow $35/month (15,000 invocations); Unlimited $100/month (verified Sep 2026) | A first inbound bridge you can prove on the free tier before paying |
| Flow Plus: Workflow Automation | Live — flagged — 5.0★ across 5 reviews; Built for Shopify; 7-day trial on all plans; listed previously as HookPost. Event-metered tiers make the pricing predictable, but five reviews under a recent rename is thin evidence for a load-bearing integration. | Start $10/month (1,000 events); Build $50/month (10,000 events); Grow $150/month (200,000 events); Scale $350/month (500,000 events) (verified Sep 2026) | Low-volume inbound events where $10/month beats every alternative (verified Sep 2026) |
| FlowRelay: Webhooks to Flow | Live — flagged — No reviews yet; Built for Shopify. The most literally named fit in this set and the newest listing, with the widest event ceiling on its top tier. No review history at all means the free tier is the only responsible way to evaluate it. | Free (500 accepted events/month); Starter $29/month (25,000); Growth $79/month (250,000); Scale $199/month (1,000,000) (verified Sep 2026) | High-volume inbound events where per-event ceilings decide the bill |
| Trigger extension inside an app you control | Build lane — A custom app carrying a trigger extension: the trigger's fields are declared in a TOML file, and your service calls the Shopify API with the trigger payload whenever the event fires. Only available where you own the app on the other side, and usable on Plus, since tasks created by custom partner apps run on the Plus plan. | $7,000–$22,000 one-time plus ~15–20% a year in upkeep (Deploi estimate, illustrative) | Internal tools and custom apps whose events belong in Flow's editor with named fields |
The Build Path
- Check the direction before anything else: Half the gaps merchants report are outbound, and outbound needs no app at all. Send HTTP Request posts to the vendor from Grow upward, waits up to 30 seconds for a response code, and retries 4XX, 5XX and 429 responses for up to 24 hours. An optional Run code step parses the response body within 5 seconds and 10 MB.
- Bridge the inbound event with a public app: A bridge app gives the vendor's outbound webhook somewhere to land, and gives Flow something to start from. Prove it on a free tier of 500 events a month, then price the paid tier against your real event volume rather than the vendor's example numbers.
- Build a trigger extension only for an app you own: Declare the trigger and its fields in the app's TOML, then have your service call the Shopify API with the trigger payload. The trigger then appears in Flow's editor beside Shopify's own, with named fields your ops team picks from a list rather than JSON they parse by hand.
- Put a date on the vendor request: Ask the vendor for tasks in writing and ask when, because a promised connector with no date is not a plan. If the answer is vague, price the bridge app now and treat the vendor's eventual tasks as a future simplification rather than a reason to stall.
- Effort band
- $7,000–$22,000 build — Deploi estimate (illustrative); lands in the $10–25K contact-form band. One trigger against an event feed that already exists sits at the bottom; several triggers plus actions, with the event feed built from scratch, sits at the top
- Typical timeline
- 3–6 weeks (Deploi estimate, illustrative); the app scaffolding and review cycle usually take longer than the trigger itself
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $1,000–$4,400/yr (Deploi estimate, illustrative) for quarterly Admin API version bumps, payload-schema changes and new fields the ops team wants exposed. Flow itself stays free.
- What you own — and what you take on
- You own: the trigger definition, the field names your workflows read, the event log and the retry behavior on your side. You take on: keeping the app installed on every store that needs the tasks, and an app-review cycle whenever the extension changes.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $1,000–$4,000 (configuration and workflow rebuild) | $7,000–$22,000 |
| Years 1–3 (recurring) | $1,300–$3,600 (subscription plus changes) | $3,000–$13,200 (maintenance) |
| 3-year total | ≈$2,300–$7,600 | ≈$10,000–$35,200 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy path: one bridge app on a mid tier around $35–$79/month plus initial configuration at illustrative agency rates; event overages are excluded, which flatters the buy column.
- † Build path: one trigger extension with two to four fields inside an app you already own, plus upkeep; three-year horizon; the vendor's event feed is assumed to exist in both lanes.
What the Sticker Price Hides
On the buy path
- — Event metering is the real meter: free tiers stop at 500 events a month, and a chatty vendor webhook clears that in a day (verified Sep 2026)
- — Bridge triggers hand you a raw payload, so every condition is written against JSON fields that change whenever the vendor changes its webhook
- — The category's deepest listing carries 6 reviews (verified Sep 2026); putting a barely reviewed app in the path of a mission-critical event is the actual risk, not the price
- — Uninstalling the bridge removes its trigger from Flow, and every workflow built on it stops rather than warns
On the build path
- — Tasks created by custom partner apps run on the Plus plan, so this lane simply does not exist below Plus
- — You need to own the app on the other side; a trigger extension cannot be added to a vendor's app from outside
- — Every store that needs the trigger requires both your app and Flow installed, so expansion stores are separate installs
- — ~$1,000–$4,400/yr upkeep (Deploi estimate, illustrative) for API version bumps and payload-schema changes
What Merchants Say
Ops leads describe hunting through Flow's trigger list for an app they just installed, then discovering the list only ever contained what each developer chose to publish.
Support threads for missing integrations follow one shape: the vendor confirms a Flow connector is on the roadmap, without a date, and the merchant ships a webhook bridge in the meantime.
If You Change Your Mind Later
If you bought and outgrow it
Removing a bridge app deletes its trigger from Flow's editor, and every workflow that started from it stops firing rather than warning you. Inventory which workflows depend on the bridge before you uninstall, keep the vendor's webhook URL and payload samples on file, and the swap to another bridge becomes an afternoon of rewiring.
If you built and want out
Little strands: the workflows stay in Flow and the code that calls the Shopify API with the trigger payload is an ordinary service in your integration layer. Uninstalling your app does remove its tasks from the editor, so migrate dependent workflows to a bridge or a native trigger before switching the app off.
When This Answer Changes
We're watching for:
- ▸ Your vendor shipping its own Flow tasks, which retires the bridge and the subscription with it
- ▸ A native inbound-webhook trigger in Flow that accepts outside events without an app (none documented as of September 2026)
- ▸ Review depth arriving in the bridge category, where the deepest listing carries 6 reviews as of September 2026
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Why doesn't my installed app show up as a trigger in Shopify Flow?
Because its developer has not built one. Shopify's developer docs say a Partner integrates an app with Flow through custom tasks, such as triggers and actions, and both the app and Flow must be installed for those tasks to appear. Shopify's current docs call them tasks, not connectors. No merchant setting adds an app to that list, which is why three App Store apps exist to bridge inbound events, free up to 500 events a month.
Can I create a Flow trigger from a webhook without building an app?
Not natively. Shopify documents one route to a custom trigger: a trigger extension declared in an app's TOML file, with your service calling the Shopify API with the trigger payload. Three App Store apps do that work for you, starting at $10/month on Flow Plus or free up to 500 events a month on FlowRelay and Workflow Webhooks (verified Sep 2026).
What does a Flow webhook bridge app cost on Shopify Plus?
Between free and $350/month, depending on event volume (verified Sep 2026). Workflow Webhooks runs free to $100/month, FlowRelay $29 to $199/month, and Flow Plus $10 to $350/month. Review depth is the harder cost: those three listings carry 6 reviews, 5 reviews and none at all, so pilot on a free tier before a vendor event becomes load-bearing.
Your Next Steps
If you're going with BUY
- Sort every missing integration into outbound and inbound, and close the outbound ones with Send HTTP Request first
- Confirm the vendor emits an outbound webhook for the event you need, since a bridge has nothing to catch without one
- Pilot one bridge on a free tier of 500 events a month and count real event volume before choosing a paid tier
- Write the workflow's conditions against a saved payload sample, and keep that sample in version control
- Ask the vendor for a dated commitment on its own Flow tasks, and diary a review when that date passes
If you're going with BUILD
- Confirm you own the app on the other side, because a trigger extension cannot be added to someone else's
- Agree the trigger's field names with the ops team before writing the TOML, so workflows read the labels they expect
- Send trigger payloads with an idempotency key so a replayed vendor event never fires a workflow twice
- Log every inbound event into your own warehouse, since Flow keeps run history for only 14 days
- Install the app on every store that needs the trigger and wire the Workflow error occurred trigger to a notification
Official Docs & Sources
- Build Flow tasks: triggers and actions (developer overview) — shopify.dev
- Flow trigger extensions (TOML definition and trigger payload) — shopify.dev
- Shopify Flow: plan availability and custom partner-app tasks — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Flow Loops or Bulk Operations for Hundreds of Shopify Records?
Flow's Get data actions run on lists of up to 100 items, so a For each loop cannot sweep a large catalog. Catalog-wide edits need a real bulk lane.
Flow Failure Alerting on Shopify: Build the Watcher or Buy One?
Shopify ships no store-wide Flow alert. Build a watcher on the Workflow error occurred trigger, which fires once per workflow version within a 30-day window.
Flow Workflow Retries on Shopify: Build Your Own Safety Net?
Flow retries transient errors like step timeouts and 5XX statuses, and never retries permanent ones. Critical workflows need their own error branches.
Flow Wait Steps or a Lifecycle Tool for a 90-Day Win-Back?
Shopify Flow allows 40 wait steps per workflow and 90 days of total waiting. A 90-day win-back needs a lifecycle platform; shorter operational waits stay in Flow.
Should You Build or Buy Site Search on Shopify?
Site search on Shopify splits by catalog size: native to ~1,000 SKUs, buy in the middle, build at big-catalog, search-led scale.
Missing a Flow trigger for a vendor you depend on?
We check the direction first, because outbound usually needs nothing, then bridge or build the inbound half and rewire the workflows your ops team already relies on.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing and platform limits carry their verification date and get re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.