Can FlowRelay trigger Shopify Flow from an external system?
Yes. A sender can post an authenticated JSON event to FlowRelay, then Shopify Flow can run from the matching FlowRelay trigger.
Use case
External webhooks into Shopify Flow.
A webhook is easy to send. The harder question is whether the store team can trust what happened when the outside event was supposed to become a Shopify Flow trigger.
Why it matters
A successful HTTP request can still leave the team guessing.
Sender logs usually explain transport. They often do not show which Shopify Flow trigger was expected, which endpoint settings were active, whether the workflow was ready, or what is safe to try next.
What FlowRelay adds
FlowRelay gives the handoff a receipt.
FlowRelay receives the outside JSON event, verifies the sender, validates expected fields, records endpoint and mapping context, and hands the trigger to Shopify Flow with a receipt the team can inspect later.
Evidence to check
First-event verification checklist
Use the first event to confirm the handoff, not just to confirm that an endpoint returned a status code.
Sender
Signed request or static-header check passed.
The store can trust where the event came from before Shopify Flow acts.
Endpoint
Trigger family, required fields, and mapping are visible.
The event has Shopify Flow meaning, not only JSON shape.
Handoff
Delivered means FlowRelay handed the trigger to Shopify Flow.
Downstream workflow outcomes remain in Shopify Flow, but the handoff is easier to check.
How to start
Start with one useful event.
A small first event makes the setup feel governable. Pick something real enough to matter and safe enough to test.
-
01
Name the sender
Record the outside system, event name, owner, expected volume, and Shopify Flow trigger family.
-
02
Create the endpoint
Choose authentication, required fields, and the FlowRelay trigger variant Shopify Flow will use.
-
03
Connect the Flow trigger
Add or check the matching FlowRelay trigger in Shopify Flow before you send the first test event.
-
04
Send a safe event
Use a low-risk example without secrets, copied customer records, or irreversible downstream actions.
-
05
Confirm the receipt
Confirm auth, validation, mapping, Flow readiness, and handoff so the production path has a clear record.
Boundary
Delivered means handoff, not downstream success.
FlowRelay can show that it handed the trigger to Shopify Flow. Shopify Flow and downstream apps still own branches, actions, emails, fulfillments, tags, refunds, and later business outcomes.
- Use FlowRelay receipts for intake and handoff evidence.
- Use Shopify Flow run history for workflow conditions and actions.
- Use downstream system logs for actions that happen after Shopify Flow.
Questions
Common questions.
What does support need to see when something fails?
Redacted receipt facts — the endpoint settings, mapped fields, support code, and a diagnostics share. Support does not need raw payloads, endpoint secrets, or authentication headers, and should not be sent them.