What does Delivered mean?
Delivered means FlowRelay handed the trigger to Shopify Flow. Shopify Flow still owns branches, downstream app calls, emails, fulfillment actions, and later outcomes.
Comparison
Generic webhook infrastructure vs FlowRelay for Shopify Flow.
Webhook infrastructure can be excellent at transport. FlowRelay is for the moment when the team cares less about the pipe and more about the Shopify Flow handoff.
A focused product can feel safer when the operational context is specific.
The receipt is valuable because it answers a Shopify Flow question.
General infrastructure can be strong. FlowRelay is for the Shopify Flow handoff.
What changes
The category comparison changes when the destination matters.
A general webhook product can show delivery attempts and retries, but the Shopify operator still needs to know what the event meant inside their native automation boundary.
How FlowRelay helps
FlowRelay is narrower on purpose.
FlowRelay focuses on authenticated intake, Shopify Flow trigger context, receipt facts, replay caution, redacted diagnostics, and governed access for humans or authorized agents.
Evidence to check
Category responsibility grid
The useful comparison is not more features. It is what each category makes easier to believe and operate.
- Infrastructure
- Best when teams need general event transport, routing, observability, and developer-owned flexibility.
- FlowRelay
- Best when Shopify Flow should remain the workflow engine and the handoff needs receipts and recovery context.
- Decision
- Choose based on the operational question your team wants answered during failure.
How to start
Compare the recovery moment.
Picture the day something fails, because that is when the value of destination-aware evidence becomes real.
-
01
Name the destination
If the destination is Shopify Flow, note the trigger family and workflow owner.
-
02
Name the evidence need
Decide whether transport logs are enough or whether handoff receipts are needed.
-
03
Name the operator
Identify whether a merchant, partner, support person, or authorized agent must recover the issue.
-
04
Pick the narrowest fit
Use infrastructure for general pipes and FlowRelay for Shopify Flow handoff operation.
Existing-path check
Verify the current path before changing it.
Before changing a sender, list the outside system, current receiver, intended Shopify Flow trigger, owner, rollback path, evidence source, confidence level, and any access gaps. FlowRelay, Shopify Sidekick, and authorized agents cannot automatically discover every existing webhook app, Zapier or Make scenario, middleware route, serverless function, or receiver unless those systems are available to inspect. If the current environment is incomplete, start with one low-risk event and document what is unknown.
Questions
Common questions.
Do public examples need raw payloads or secrets?
No. Public proof should use receipt facts, endpoint settings, mapped fields, support codes, and redacted diagnostics. Do not include endpoint secrets, authentication headers, tokens, raw event bodies, customer data, or copied private logs.
When is this a good fit?
This is a good fit when the team is choosing between a broad webhook infrastructure product and a Shopify Flow-specific handoff layer.