Custom business values
Select incoming fields or use JSONata. Declare text, numbers, lists, or objects; preview the result and copy the generated Shopify Run code recipe.
Choose your mapping →
FlowRelay
FlowRelay for Shopify Flow
Receive authenticated JSON from your tools. Pass business values and optional native Shopify references into Flow, then keep a receipt of the handoff. Your conditions and actions stay in Shopify Flow.
Decide what your workflow needs
Select incoming fields or use JSONata. Declare text, numbers, lists, or objects; preview the result and copy the generated Shopify Run code recipe.
Choose your mapping →Use generic events without order, customer, or product read scopes. Native triggers require the matching optional permission and a Shopify reference supplied in the event.
Check permissions →Import a template or configuration, add fresh credentials, and prove the destination workflow. Invalid or oversized data fails clearly.
Reuse a configuration →Setup path
FlowRelay keeps Shopify Flow as the place where workflow logic lives, while each external sender gets its own authenticated intake point, receipt history, and recovery context.
Name the endpoint, identify the service that will send the POST request, and review its compatible authentication preset. Open the trigger, authentication, and mapping controls when the integration needs them.
Preview a synthetic sample, filter the trigger by the immutable endpoint ID, and use the generated parser when passing custom data. Build conditions and actions in Shopify Flow.
FlowRelay verifies the request, required fields, mapping, and Flow readiness.
Confirm what arrived, what passed, and what FlowRelay handed to Shopify Flow.
FlowRelay supports generic, order, customer, product, inventory, fulfillment, return, and company/B2B event families. Need the full walkthrough? Start with the first endpoint guide. Replacing an existing receiver? Use the swapover guide.
Shopify Flow guides
Connect an external webhook, trace a missing run, or decide whether a retained event should be handed to Shopify Flow again.
Compare the original receipt with current settings and possible Flow side effects.
No raw event bodies, authentication headers, endpoint secrets, tokens, or customer data.
Receipt
A generic webhook log tells you a request was sent. The FlowRelay receipt shows the event we received, how we normalized it, and the exact trigger we handed to Shopify Flow — with timestamps you can cite.
The same receipt facts can support store teams, setup partners, and authorized agents without exposing secrets or raw event bodies.
Questions
It receives external events, checks the sender and required fields, records receipt facts, and hands a normalized trigger to Shopify Flow.
Yes. A sender such as an ERP, warehouse system, CRM, partner app, or custom service can send an authenticated JSON event to a FlowRelay endpoint, then Shopify Flow can use the matching FlowRelay trigger.
No. Delivered means FlowRelay handed the trigger to Shopify Flow. From there, Shopify Flow runs your workflow. FlowRelay's receipt proves the handoff — not the downstream result.
FlowRelay is a good fit when Shopify Flow should remain the workflow engine, but outside systems need a controlled way to send events with authentication, receipts, replay context, diagnostics, and authorized access.
Generic endpoints do not need extra Shopify read permissions. Order, Customer, and Product triggers need the matching optional Shopify permission so Shopify Flow can receive the native reference from your event payload. Read the data access note.
FlowRelay is not for replacing Shopify Flow, building generic workflows, or proving downstream outcomes after Shopify Flow receives the trigger.
Rules, branches, conditions, downstream app actions, email sends, fulfillment actions, and business outcomes should stay in Shopify Flow or the downstream systems that execute them.