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.
Diagnostics
Webhook diagnostics for Shopify Flow handoffs.
Good diagnostics change the support conversation from please look at everything to here is the exact boundary and the safe evidence.
The value is the permission to ask for help safely.
The bundle makes the issue easier to triage.
The product demonstrates restraint instead of asking for broad access.
What changes
Support often gets either too little context or too much sensitive material.
Screenshots, copied payloads, secrets, and vague failure reports all slow down recovery. The team needs help without increasing data exposure.
How FlowRelay helps
FlowRelay packages a safer evidence bundle.
Diagnostics use redacted receipt facts, endpoint snapshots, support codes, and replay context so the helper can understand the handoff without raw event bodies.
Evidence to check
Redacted diagnostics bundle anatomy
Show what the bundle includes and, just as importantly, what it leaves out.
- Included
- Receipt ID, endpoint name, status, trigger family, support code, timeline, and safe recovery context.
- Excluded
- Endpoint secrets, HMACs, authentication headers, tokens, raw event bodies, customer data, and copied private logs.
- Previewed
- The operator can review what will be shared before sending diagnostics.
How to start
Share the handoff, not the payload.
Diagnostics should feel like a privacy-preserving operating tool, not a dump of debugging data.
-
01
Open the event or endpoint
Start from the specific receipt or endpoint involved in the support question.
-
02
Preview diagnostics
Review the redacted facts that will be shared.
-
03
Send the share ID
Use the support-safe identifier and expected business outcome in the support request.
-
04
Keep private data out
Do not add secrets, raw payloads, tokens, customer records, or private logs to the message.
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 support, a developer, a partner, or an authorized agent needs handoff context without seeing secrets or raw payload data.