Should You Build a Custom Flow Connector on Shopify Plus?
Custom Flow triggers and actions are a BUILD on Shopify Plus when an event from an outside system has to start a Flow workflow. Shopify's developer docs call an app's own triggers and actions tasks, and only Plus stores can use tasks from custom partner apps (verified Sep 2026). Outbound-only automation needs no app: Flow's Send HTTP Request action covers Grow, Advanced and Plus. A two-task custom app runs $8,000–$25,000 (Deploi estimate, illustrative).
Your profile — see how the verdict shifts
- Confidence
- High — Read Shopify's Flow help page: Flow is a free app on Basic, Grow, Advanced and Plus; Send HTTP Request is available on Grow, Advanced and Plus; and only stores on the Plus plan can use tasks created by custom partner apps (verified Sep 2026). Read the Flow developer docs: an app integrates through custom tasks, such as triggers and actions, and merchants need both the app and Flow installed. The triggers page documents one path to a custom trigger, a trigger extension defined in TOML inside an app, with no merchant-configurable inbound-webhook trigger anywhere on the page. Browsed the App Store's workflow-automation and staff-notifications categories and fetched the Zapier, Make and Mechanic listings: Mechanic carries 5.0★ across 129 reviews, Zapier 4.0★ across 74, and Make 1.0★ across 3, so Make was excluded. Workflow Companion, the most literally named fit, carries 21 reviews and its listing could not be re-verified in September 2026, so it is not shortlisted. The build band is a Deploi estimate.
- Reference scenario
- $20M–$200M GMV · Shopify Plus · a proprietary ERP, loyalty or warehouse system emitting events Flow cannot see · 10–40 live workflows · an ops team that edits workflows in Flow's editor · agency dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Basic, Grow or Advanced plan | BUY | Custom partner-app tasks are Plus-only, so the build lane does not exist here. Mechanic ($16–$99/month on these tiers, verified Sep 2026) or Zapier covers event-driven logic, and Send HTTP Request handles outbound calls from Grow upward. |
| Plus, outbound-only automation (tell your ERP when something happens in Shopify) | WAIT | Flow already covers it: Send HTTP Request posts to your endpoint, waits up to 30 seconds for a response and can retry 4XX, 5XX and 429 errors for up to 24 hours (verified Sep 2026). Nothing to build, nothing to buy. |
| Plus, outside events must start Flow workflows | BUILD | The reference scenario. The only way an ERP or loyalty event becomes a Flow trigger is a trigger extension in your own app, at $8,000–$25,000 for two to four tasks (Deploi estimate, illustrative). Zapier or Mechanic can react to the event in their own editors, but your ops team then maintains logic in two places. |
| Plus organization with several stores, or an app you'll distribute | BUILD | One custom app installs on each store and its tasks appear in each store's Flow editor; every store needs both the app and Flow installed (verified Sep 2026). The build cost amortizes across stores while a per-store automation subscription multiplies. |
What Custom Flow triggers and actions Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | An ERP or warehouse event that starts a Flow workflow lets the ops team tag, notify, hold or update orders in the editor they already use, instead of filing a ticket for every rule change. |
| Customer experience | Medium | Automation that fires inside Flow the moment the event lands keeps shipping notices, loyalty credits and holds timely, where middleware adds its own delay between systems. |
| Data & insight | Medium | Every trigger payload can be logged to your own warehouse on the way in, giving you an event history that outlives Flow's 14-day run retention and any vendor dashboard. |
| Retention & LTV | Low | Loyalty and post-purchase automations reach customers sooner when the loyalty system's event is a first-class Flow trigger, though the effect is a lift on existing flows rather than a new revenue line. |
Spend ceiling: Size the spend to the ops hours you recover, not to the software. A two-task app at $8,000–$25,000 (Deploi estimate, illustrative) replaces a middleware subscription of $103.50–$199/month (Zapier Team and Mechanic Plus tiers, verified Sep 2026) only over years; the case for building is that the ops team owns the logic in Flow and every store in the organization inherits the same tasks.
What buying enables (top apps)
- + Automation live today on any plan, including the three where custom Flow tasks are unavailable
- + Mechanic's code-based platform with 5.0★ across 129 reviews and no usage fees (verified Sep 2026)
- + Zapier's connections into other SaaS tools your team already uses, with a free tier for two-step Zaps
What building additionally unlocks
- + Your ERP, loyalty and warehouse events as first-class triggers in Flow's editor, next to Shopify's own
- + Actions with authentication, transformation and long-running work that Send HTTP Request's 30-second wait cannot hold
- + One app whose tasks appear in every store of a Plus organization, amortizing the build across the estate
- + An event log you control, with idempotency keys, outliving Flow's 14-day run retention
Find Your Verdict in 3 Questions
Are you on Shopify Plus?
Yes: Go to question 2.
No: Your verdict: BUY — custom partner-app tasks are Plus-only; use Mechanic or Zapier for event-driven logic and Send HTTP Request (Grow and Advanced) for outbound calls.
Does an event from an outside system (ERP, loyalty, warehouse) need to start a Flow workflow?
Yes: Your verdict: BUILD — a custom app with a trigger extension is the only way that event appears in Flow, $8,000–$25,000 for two to four tasks (Deploi estimate, illustrative).
No: Go to question 3.
Does your outbound call need more than Send HTTP Request offers: a 30-second wait, retries up to 24 hours, and an optional Run code parse?
Yes: Your verdict: BUILD — an action task with your own endpoint handles authentication, transformation and long-running work.
No: Your verdict: WAIT — Flow's Send HTTP Request and Run code already cover it at no cost.
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 | Zapier's free tier or Mechanic's $199/month Plus tier (verified Sep 2026) is live in an afternoon; a custom app with two to four tasks is a 3–6 week build at $8,000–$25,000 (Deploi estimate, illustrative). | ||
| Recurring fees | Mechanic bills $199/month on Plus and Zapier's Team plan $103.50/month (verified Sep 2026) for as long as the automations run; Flow itself is free and a custom app's only recurring line is upkeep. | ||
| Maintenance & upgrades | Vendors absorb Shopify's quarterly API version changes; your team absorbs them for the app, plus any change to the ERP event schema that feeds the trigger. | ||
| Switching & exit | Zaps and Mechanic tasks are rebuilt by hand on the next tool; workflows built on your own tasks stay in Flow, and the app's endpoint code moves with your integration layer. | ||
| Risk | |||
| Vendor risk | Mechanic is a single-vendor platform with 129 reviews and Zapier's Shopify listing sits at 4.0★ across 74 (verified Sep 2026); a custom app depends only on Flow, which Shopify ships free on every plan from Basic upward. | ||
| Security & compliance surface | A generic automation tool holds order and customer payloads in a third party's cloud between steps; a custom app's endpoint runs in infrastructure you already secure, and Flow calls it over HTTPS. | ||
| Platform-deprecation exposure | Both lanes ride Shopify's Admin API versions; Flow's task extensions are a current, documented surface with no sunset notice as of September 2026, and Send HTTP Request is documented alongside them. | ||
| Value | |||
| Fit to requirement | Zapier and Mechanic run your logic in their own editors; a custom task puts your ERP's event next to Shopify's own triggers inside Flow, where the ops team already builds and edits workflows. | ||
| Time to market | Today with Zapier or Mechanic against 3–6 weeks for the app (Deploi estimate, illustrative); Send HTTP Request is also same-day for outbound needs. | ||
| Performance & scale | Flow caps at 1,000 workflows per store, 40 wait steps per workflow and a 36-hour execution limit per section (verified Sep 2026); a custom task inherits those limits and nothing else, while a middleware tool adds its own queue between Shopify and your system. | ||
| Data ownership & AI-readiness | Flow stores run history for 14 days (verified Sep 2026) in both lanes; the custom app's endpoint can also log every event into your own warehouse, while a middleware vendor's history stays in its dashboard. | ||
| Focus & opportunity cost | A two-task app is a small, bounded build; the opportunity cost rises only when the ERP side's event feed does not exist yet and has to be built first. | ||
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) | Outbound-only automation and every workflow that starts from a Shopify event |
| Mechanic | Live — Developer-flavored automation: tasks written in Liquid, nothing to host | $16–$199/mo tiers at entry volumes; scales with volume (verified Sep 2026) | Developer-written automation on any plan, including the three where custom Flow tasks are unavailable |
| Zapier: Workflow Automation | Live — 4.0★, 74 reviews; 14-day trial on Professional and Team. Generic middleware connecting Shopify to other SaaS tools; the free tier allows two-step Zaps, and paid tiers add multi-step Zaps and webhooks. Logic lives in Zapier's editor, and the Shopify listing's rating trails Mechanic's. | Free (two-step Zaps); Professional $29.99/month; Team $103.50/month (verified Sep 2026) | Connecting Shopify events to SaaS tools that have no Flow tasks of their own |
| Custom app with Flow trigger and action tasks | Build lane — A custom app carrying trigger extensions (your ERP, loyalty or warehouse events, defined in TOML and sent to Shopify with the trigger payload) and action extensions (an HTTPS endpoint Flow calls with the fields your ops team fills in). Shopify's developer docs call these tasks. Plus only; the store needs both the app and Flow installed. | $8,000–$25,000 one-time plus ~15–20% a year in upkeep (Deploi estimate, illustrative) | Plus merchants whose ops team builds in Flow and whose events come from systems Flow cannot see |
The Build Path
- Trigger extension for outside events: Define the trigger in the app's TOML with the fields your workflows will read, then have your integration service send the trigger payload to Shopify's API whenever the ERP, loyalty or warehouse system emits the event (verified Sep 2026). The trigger then appears in Flow's editor next to Shopify's own.
- Action extension for calls Flow cannot make natively: Expose an HTTPS endpoint the action calls with the fields ops staff fill in; reserve this for calls that need authentication, transformation or a response Send HTTP Request cannot handle within its 30-second wait.
- Send HTTP Request and Run code first: Before writing an action task, test whether Flow's Send HTTP Request (Grow, Advanced and Plus, with retries for up to 24 hours) plus an optional Run code step (ECMA2020 JavaScript, 5 seconds, 10 MB, no network calls) already covers the outbound half (verified Sep 2026).
- Idempotency and observability: Key every trigger payload so a replayed ERP event never fires a workflow twice, log each call into your own warehouse because Flow keeps run history for only 14 days, and wire the Workflow error occurred trigger, which fires once per workflow version within 30 days (verified Sep 2026).
- Effort band
- $8,000–$25,000 build — Deploi estimate (illustrative); lands in the $10–25K contact-form band. Two tasks against an event feed that already exists sit at the bottom; four tasks plus building the ERP event feed itself sit at the top
- Typical timeline
- 3–6 weeks (Deploi estimate, illustrative); ship the trigger first, since the outbound half often needs no code at all
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $1,200–$5,000/yr (Deploi estimate, illustrative) for quarterly Admin API version bumps, ERP event-schema changes and new fields the ops team wants in the trigger. Flow itself stays free.
- What you own — and what you take on
- You own: the trigger definitions, the endpoint code, the event log and the workflows your ops team builds on them. You take on: keeping the app installed on every store that needs the tasks, and the ERP-side contract for the events that feed it.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $3,000–$8,000 (task writing and testing) | $8,000–$25,000 |
| Years 1–3 (recurring) | $7,200–$13,000 (subscription plus changes) | $3,600–$15,000 (maintenance) |
| 3-year total | ≈$10,000–$21,000 | ≈$11,600–$40,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy path: Mechanic's Plus tier at $199/month (verified Sep 2026) plus an initial task-writing project at illustrative agency rates; Zapier's Team plan would land lower.
- † Build path: a custom app with two triggers and two actions, plus upkeep; three-year horizon; the ERP event feed is assumed to exist in both lanes.
What the Sticker Price Hides
On the buy path
- — Mechanic prices to your Shopify plan tier, so moving to Plus takes it from $99 to $199/month (verified Sep 2026) even when your task count does not change
- — Two editors, two owners: automation split between Flow and a middleware tool is the usual root cause of 'nobody knows why this order got tagged'
- — Middleware sits between Shopify and your system with its own delay and its own outage calendar; a miss shows up in the vendor's dashboard, not in Flow's run history
- — Make's Shopify listing carries 1.0★ across 3 reviews (verified Sep 2026); low-review middleware in the order path is a vendor risk, not a bargain
On the build path
- — Building the ERP event feed itself, when none exists, doubles the project; the Flow tasks are the small half
- — Every store in a Plus organization needs both your app and Flow installed for the tasks to appear (verified Sep 2026); expansion stores are separate installs
- — Flow keeps run history for 14 days (verified Sep 2026); without your own event log, a dispute about a missed workflow has no evidence after two weeks
- — ~$1,200–$5,000/yr upkeep (Deploi estimate, illustrative), mostly API version bumps and ERP event-schema changes
What Merchants Say
Ops leads describe the two-editor problem: half the automation lives in Flow, half in a middleware tool, and nobody can answer 'why did this order get tagged' without opening both.
Middleware reviews cluster on delay and visibility: the automation fires minutes after the Shopify event, and the run history that would explain a miss sits in another tool's dashboard.
If You Change Your Mind Later
If you bought and outgrow it
Leaving Zapier or Mechanic means rebuilding every task by hand in the next tool, because neither exports logic in a form Flow or another platform imports. Keep a written inventory of each automation's trigger, conditions and actions from the start, and the rebuild becomes a week of configuration rather than an archaeology project.
If you built and want out
Little strands: the workflows your ops team built stay in Flow, and the app's endpoint and trigger-sending code are ordinary services in your integration layer that move with it. Uninstalling the app removes its tasks from the editor, so migrate any workflow that depends on them before you switch it off.
When This Answer Changes
We're watching for:
- ▸ Shopify opening custom partner-app tasks to Advanced or Grow stores (Plus-only as of September 2026)
- ▸ A native inbound-webhook trigger in Flow that accepts events from outside systems without an app (none documented as of September 2026)
- ▸ Changes to Send HTTP Request's 30-second wait or 24-hour retry ceiling, or to Run code's 5-second and 10 MB limits
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Can I create my own Shopify Flow triggers?
Yes, on Shopify Plus, by building them into an app. Shopify's Flow developer docs describe custom tasks, such as triggers and actions, that a Partner builds for its app. A trigger is defined in a TOML file, and your system sends the trigger payload to Shopify's API. Only stores on the Plus plan can use tasks from custom partner apps, and the store needs both your app and Flow installed (verified Sep 2026).
Is Shopify Flow's Send HTTP Request enough instead of a custom app?
Send HTTP Request covers the outbound half without any app. Available on Grow, Advanced and Plus, the action posts to your endpoint and waits up to 30 seconds for a response code. On 4XX, 5XX and 429 responses you pick Retry, Fail or Ignore; retries run up to 24 hours (verified Sep 2026). An optional Run code step parses the response body. Only inbound events from an outside system still require a custom trigger task.
Does Zapier or Mechanic replace custom Flow triggers and actions?
Zapier and Mechanic replace the automation, not the Flow integration. Both run your logic in their own editors, outside Flow, so the ops team maintains automation in two places and Flow's own actions never see the event. Mechanic costs $199/month on Plus with 5.0★ across 129 reviews, and Zapier's Team plan $103.50/month (verified Sep 2026). Choose them when the ops team does not build in Flow, or on the three plans without custom tasks.
Your Next Steps
If you're going with BUILD(matches your selected profile)
- List every automation that should start from an outside event and every outbound call Flow makes today
- Route the outbound calls through Send HTTP Request first; write an action task only where its 30-second wait or response handling falls short
- Define the trigger fields in TOML with the ops team, so the workflows they build read the names they expect
- Send trigger payloads with an idempotency key and log every event into your warehouse, since Flow keeps runs for 14 days
- Install the app on every store that needs the tasks and wire the Workflow error occurred trigger to a notification
If you're going with WAIT
- Map each outbound need to a Send HTTP Request action with Retry chosen for 5XX and 429 responses
- Add a Run code step only where the response body has to be parsed
- Test each workflow with Flow's test run, which stops at the first action that would make a change
- Revisit this decision the day an outside system needs to start a workflow rather than receive one
Official Docs & Sources
- Shopify Flow (plan availability and custom partner-app tasks) — Shopify Help Center
- Build Flow tasks: triggers and actions (developer overview) — shopify.dev
- Flow trigger extensions — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Plus's 30-Day Card Authorization vs. a Custom Reauth Flow?
Plus stretches Shopify Payments authorizations from 7 to up to 30 days for some payment types. Nothing to build inside that window; past it, buy a deposit app.
Should You Build or Buy Flash-Sale Scheduling on Shopify Plus?
Launchpad, free on Plus, schedules publishing, prices, theme and inventory for a drop. Move Scripts-era rules to Discount Functions; buy a queue only for huge drops.
Shopify Audiences vs. a CDP: Which Builds Better Ad Lists?
Shopify Audiences is included with Plus but gated to US and Canada stores on Shopify Payments. Switch it on first; a CDP answers a different question.
Hitting Shopify's 25-Function Cap: Consolidate or Buy an App?
When one Function type nears its per-store activation cap, consolidate rules into fewer data-driven functions; no app raises the 25 discount function ceiling.
Should You Build or Buy Abandoned Checkout Recovery on Shopify?
Abandoned checkout recovery belongs in the email/SMS platform you already pay for, with an audited tracking layer underneath.
Ready to put your ERP's events inside Flow?
We build the trigger and action tasks, wire the event log, and install the app across your stores, or confirm that Send HTTP Request already covers you and save you the build.
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.