FlowRelay
Use Cases
Work with a partner without sharing secrets
Use this path when another team needs to help investigate an event, but the merchant should not copy private request data into chat, tickets, or screenshots.
Who this helps #
This is for setup partners, sender owners, and support teams that need to resolve the setup or handoff issue without receiving secrets, raw payloads, or customer data.
What the partner gets #
The partner gets redacted receipt facts, endpoint state, stable recovery codes, retention and replay context, and a support-safe summary that can be discussed without widening access.
What stays private #
Do not share raw request bodies, full auth headers, signing secrets, tokens, sessions, database URLs, customer records, or copied private incidents.
Typical path
A typical path starts from the scenario, then moves into setup and verification.
- 01Agree on the question the partner needs to answer, such as whether the sender used the right URL, sent valid JSON, mapped the expected ID, or reached Shopify Flow.
- 02Open the FlowRelay receipt or endpoint that anchors the investigation.
- 03Preview the diagnostics package and check that it contains redacted setup facts, stable codes, receipt context, and recovery guidance.
- 04Confirm that the package excludes raw payloads, full headers, endpoint secrets, HMAC values, Shopify tokens, sessions, and customer data.
- 05Share the diagnostics ID or support-safe summary only after the merchant or operator approves it.
- 06Keep the follow-up tied to the frozen diagnostics package instead of pasting private logs into another tool.