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.
Shopify Flow guide
Custom script events into Shopify Flow.
Custom scripts are easy to start and hard to operationalize because ownership and recovery context decay over time. FlowRelay gives the event a governed front door before Shopify Flow runs the workflow.
custom script events are framed by operational impact, not as generic webhooks.
The team can see what must be known before production traffic moves.
The sender event enters the workflow system the store already uses.
What changes
The sender event is only useful when its meaning survives the handoff.
A custom script system may say it sent a batch job completion, manual ops action, nightly reconciliation, or admin tool signal event, but the operator still needs to know which Shopify Flow trigger family received it, what was accepted, and what can be safely retried or shared.
How FlowRelay helps
FlowRelay turns the sender event into a receipt-backed path.
Use a FlowRelay endpoint for the custom script sender, choose the generic, order, inventory, customer, or product trigger family, send one safe test event, and confirm the Shopify Flow handoff before relying on production traffic.
Evidence to check
Custom script event checklist
The checklist makes the guide concrete: sender, event, Shopify Flow target, safe test event, receipt check, common failure states, and rollback owner.
- Sender context
- custom script source, event name, owner, expected volume, and business meaning.
- Flow trigger
- Shopify Flow trigger family, workflow owner, safe test event, and downstream side-effect check.
- Recovery
- Receipt check, common failure states, diagnostics share path, replay caution, and rollback owner.
How to start
Prove one sender event before broadening.
Start with one concrete event and the exact evidence the operator will inspect.
-
01
Name the event
Pick one custom script signal such as batch job completion, manual ops action, nightly reconciliation, or admin tool signal.
-
02
Choose the trigger family
Select the Shopify Flow trigger family that matches the business object: generic, order, inventory, customer, or product.
-
03
Send a safe event
Use a low-risk example without secrets, copied customer records, or irreversible downstream actions.
-
04
Use the receipt
Confirm authentication, mapping, Flow readiness, handoff result, diagnostics path, and replay caution.
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 custom script events should trigger Shopify Flow while keeping handoff evidence, recovery context, and sensitive data boundaries clear.