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.
Agent-ready recovery
Agent-ready event recovery for Shopify Flow.
Agent-ready recovery is not an agent doing whatever it thinks is best. It is an agent operating through evidence, previews, redaction, and stop conditions.
A constrained agent feels safer than an omniscient assistant promise.
FlowRelay changes scattered logs into an action-ready recovery packet.
The operator sees how mistakes are slowed down.
What changes
Recovery gets unsafe when the next action is inferred.
Without a receipt and governed actions, an agent or helper may over-trust logs, miss downstream side effects, or ask for sensitive material it should not need.
How FlowRelay helps
FlowRelay gives the agent a constrained recovery path.
Authorized agents can inspect receipt facts, prepare diagnostics, preview recovery options, respect redaction, and keep an audit trail within the merchant's grant.
Evidence to check
Recovery action preview
The preview should show the proposed action, evidence used, side-effect caution, confirmation requirement, and refusal boundary.
- Evidence
- Receipt facts and endpoint context explain why the recovery action is being considered.
- Preview
- Replay or support actions show consequences and required confirmation before execution.
- Refusal
- The agent refuses raw payload requests, secret exposure, broad endpoint discovery, and unsupported silent changes.
How to start
Recover with confirmation, not guesswork.
Agent participation should feel more governed than manual improvisation.
-
01
Find the event receipt
Use scoped access to inspect the event state and Shopify Flow handoff context.
-
02
Prepare the recovery option
Summarize whether diagnostics, replay review, support, or Shopify Flow inspection is next.
-
03
Preview sensitive action
Show side effects, redactions, and confirmation requirements before acting.
-
04
Record the result
Keep audit, support, and receipt context attached to the recovery work.
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 an authorized agent may help recover failed or unclear external-event handoffs, but the merchant wants scoped access, previews, redaction, and audit.