The first move should feel reversible and specific, not like a full rewrite.
Migration
Move a custom webhook receiver into FlowRelay.
Custom receiver code often looks cheap until the person responsible for a failed handoff has to reconstruct intent from logs, deploy history, and tribal knowledge.
The team should know who checks sender, endpoint, Flow trigger, and rollback.
The value becomes concrete when the new receipt is easier to explain than the old logs.
What changes
The hidden cost is confidence, not code.
A custom receiver may already work, but the team still has to ask who owns replay, which setting was live, what changed, and how support can help without seeing secrets.
FlowRelay role
FlowRelay gives the path an operating shape.
Move one event path behind a FlowRelay endpoint, keep Shopify Flow as the workflow engine, and use receipt facts to compare behavior before widening the change.
Evidence to check
Before and after responsibility table
Use the comparison to show what stops depending on memory and what becomes visible.
Before
Receiver code, deploy logs, sender retries, and developer memory carry the explanation.
That can work, but it is fragile when the original owner is unavailable.
After
Endpoint settings, receipt facts, replay context, and diagnostics are visible in FlowRelay.
The event path becomes easier for operators and partners to understand.
Rollback
The old receiver path and owner remain named until the FlowRelay path is proven.
A reversible change lowers the perceived cost of starting.
How to start
Move one receiver path, not the whole setup.
The safest migration is narrow enough to explain in one meeting.
-
01
Inventory the current receiver
Record URL owner, sender, workflow target, volume, failure behavior, evidence source, confidence, and rollback path.
-
02
Create the matching endpoint
Match the Shopify Flow trigger family and authentication mode without changing downstream workflow logic yet.
-
03
Run a low-risk event
Send one safe event and compare the old evidence trail with the FlowRelay receipt.
-
04
Switch only after proof
Move production traffic when receipt, Flow trigger, owner, and rollback are all understood.
Current-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.
Inventory
Endpoint discovery may require real work.
FlowRelay, Shopify Sidekick, and authorized agents cannot automatically inventory endpoints hidden in apps, serverless functions, scripts, middleware, Zapier or Make scenarios, or private repos unless those systems are available to inspect.
- Treat unknown current paths as access gaps, not as solved facts.
- Use evidence source and confidence level in the migration notes.
- Start with a low-risk event when the current environment is incomplete.
Questions
Common questions.
Can FlowRelay discover all existing webhook endpoints for me?
Not by itself. Endpoint inventory depends on what systems, repos, apps, automation tools, and environments are available to inspect.
Should migration start with production traffic?
No. Start with a low-risk event and compare the old evidence trail with the FlowRelay receipt first.
Does moving the receiver move the workflow logic?
No. FlowRelay should handle the intake boundary while Shopify Flow continues to own workflow rules and actions.