Get outside events into Shopify Flow with proof you can trust.

Keep Shopify Flow as the workflow engine. FlowRelay gives outside systems a governed front door: verify each request, record what was accepted, show what was handed to Shopify Flow, and keep recovery safe when something needs attention.

Trust the senderSigned requests or static-header checks verify the source before an event enters Shopify Flow.
Know Flow was readyReceipts show whether the matching Shopify Flow trigger was known to be enabled when FlowRelay processed the event.
Keep context intactOrder, customer, inventory, and other event families keep the right Shopify Flow trigger shape.
Recover carefullyReplay and diagnostics show what to review first, with sensitive data redacted.

FlowRelay for Shopify Flow, in one page.

FlowRelay for Shopify Flow is the current FlowRelay edition for sending authenticated external events into Shopify Flow with receipt facts, replay context, diagnostics, and governed operator access.

Product
FlowRelay for Shopify Flow
Category
External event intake and handoff reliability for Shopify Flow.
Best fit
Shopify merchants and partners connecting ERP, warehouse, CRM, custom app, or partner-system events to Shopify Flow.
Not for
Replacing Shopify Flow, building generic workflows, or proving downstream outcomes after Shopify Flow receives the trigger.

A clear first event path for merchants and partners.

For teams connecting an ERP, warehouse, CRM, custom app, or partner system, the goal is simple: external system to FlowRelay endpoint to Shopify Flow trigger to receipt/result, with the workflow logic still inside Shopify Flow.

  1. 01 Create an endpoint for the sender

    Pick the Shopify Flow event family and the authentication mode your sender will use.

  2. 02 Connect the matching Flow trigger

    Build the workflow in Shopify Flow, where rules, branches, and downstream actions belong.

  3. 03 Send a test event

    FlowRelay verifies the request, required fields, mapping, and Flow readiness.

  4. 04 Check the receipt

    Confirm what arrived, what passed, and what FlowRelay handed to Shopify Flow.

Need the full walkthrough? Start with the first endpoint guide. Replacing an existing webhook, custom-code, or manual path? Use the swapover guide.

FlowRelay Events / Shopify Flow receipt Redacted
Receipt fr_rcpt_shopify_0429
Delivered to Shopify Flow
The receipt shows what FlowRelay could prove. After Shopify Flow receives the trigger, workflow decisions and action results belong there.
Trigger variantExternal order event
Endpoint settingsOrder risk intake, v3
Auth resultHMAC verified
Flow readinessMatching trigger enabled
MappingOrder reference mapped
Handoff resultTrigger handed to Shopify Flow
Replay Review before retry

Compare the original receipt with current settings and possible Flow side effects.

Diagnostics Share a redacted package

No raw event bodies, authentication headers, endpoint secrets, tokens, or customer data.

Proof your team can use when something needs recovery.

A generic webhook log can show that a request arrived. FlowRelay adds the Shopify Flow context merchants and partners need: which trigger family handled the event, which endpoint settings were active, whether the matching Flow trigger was ready, what was handed off, and what is safe to try next.

The same receipt facts can support human operators, setup partners, and authorized agents without exposing secrets or raw event bodies.

  • FlowRelay showsIntake, validation, receipt facts, recovery context, diagnostics, and handoff.
  • Shopify Flow ownsWorkflow branches, downstream app calls, email sends, fulfillment actions, and other results after the trigger.
  • Stays out of proofSecrets, authentication headers, raw event bodies, tokens, session data, and customer data.

Use the event family that matches the workflow.

Each endpoint is tied to a Shopify Flow trigger family, so setup guidance, receipts, mapping, and recovery language stay close to the merchant workflow instead of becoming generic webhook noise.

GenericExternal event

General operational events that do not need a Shopify resource reference.

OrderExternal order event

Order, payment, risk, and post-purchase signals from external systems.

CustomerExternal customer event

Lifecycle, support, account, and loyalty signals.

ProductExternal product event

Catalog, merchandising, and product updates.

InventoryExternal inventory event

Warehouse, planning, or stock-position updates.

FulfillmentExternal fulfillment event

Shipment, carrier, and logistics updates.

Return / refundExternal return event

For return, refund, and exception workflows.

Company / B2BExternal company event

B2B account, approval, and wholesale operations.

Fit and handoff boundaries.

What is FlowRelay for Shopify Flow?

FlowRelay for Shopify Flow is an external event intake layer for Shopify Flow. It authenticates sender requests, validates expected fields, records receipt facts, and hands a normalized trigger to Shopify Flow.

Can FlowRelay trigger Shopify Flow from an external system?

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.

What does Delivered mean in FlowRelay?

Delivered means FlowRelay handed the trigger to Shopify Flow. It does not mean Shopify Flow branches, downstream app calls, emails, fulfillment actions, or later systems completed successfully.

When is FlowRelay a good fit?

FlowRelay is a good fit when Shopify Flow should remain the workflow engine, but outside systems need a governed way to send events with authentication, receipts, replay context, diagnostics, and controlled operator access.

What should stay in Shopify Flow?

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.

Install FlowRelay from the Shopify App Store.

Start from the Shopify listing when you are ready to install. Launch pricing is based on the work this edition actually does: accepted events, diagnostics shares, replay executions, and controlled operator or agent access with governed safeguards.