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 setup
Agent-ready event setup for Shopify Flow.
Agent-ready does not mean handing an agent a pile of raw payloads. It means giving it the same bounded receipt facts and safe next actions a careful operator would use.
The value is reducing the fear that the agent is guessing.
One endpoint, one receipt, one support-safe summary.
Agent access is governed operator access, not a separate permission system.
What changes
Agents amplify ambiguity if the context is messy.
Without structured receipts, an agent has to infer state from logs, docs, screenshots, and platform behavior. That makes automation feel less safe, not more.
How FlowRelay helps
FlowRelay packages the handoff context.
FlowRelay exposes receipt facts, redacted diagnostics, action previews, audit, and scoped grants so authorized agents can help without secrets or silent changes.
Evidence to check
Scoped agent setup brief
Use a concise brief: endpoint, event family, permitted reads, safe diagnostic actions, stop conditions, and human approvals.
- Scope
- The agent can inspect only the allowed endpoint, receipt, or support path.
- Preview
- Sensitive operations are previewed before execution where the product requires confirmation.
- Audit
- Agent operations leave a record instead of becoming invisible background automation.
How to start
Set up for the operator you will actually use.
Human and agent recovery both improve when context is explicit before work begins.
-
01
Create the event endpoint
Use the standard Shopify Flow setup path and confirm the first receipt.
-
02
Define the agent job
State whether the agent is allowed to inspect, prepare diagnostics, preview replay, or request support.
-
03
Limit the grant
Use scoped access, redaction, action previews, and refusal boundaries.
-
04
Test with a harmless case
Verify the agent can summarize the receipt without exposing secrets or taking silent action.
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 or partner needs to inspect receipts, prepare diagnostics, or support recovery without raw payload access or broad store privileges.