FlowRelay
Setup
Event types and payloads
FlowRelay for Shopify Flow supports a fixed set of trigger variants. Choose the one your workflow needs, then make sure the sender can provide the required JSON fields.
Steps
Complete these in order.
- 01Start with Generic when you only need a custom event to start a Shopify Flow workflow.
- 02Choose Order, Customer, or Product when the workflow needs Shopify's native resource reference for that object.
- 03Choose Inventory, Fulfillment, Return/refund, or Company/B2B when the workflow needs the related resource lane FlowRelay exposes for that trigger variant.
- 04For native or related-resource variants, configure the JSON path where FlowRelay can find the required Shopify ID or GID.
- 05Add up to five required payload paths only for fields the sender must always include.
- 06Send a synthetic test event and confirm the receipt shows the expected mapping result before enabling production traffic.
Supported variants #
The Shopify Flow edition supports a fixed set of trigger variants. Choose the variant that matches what the workflow needs from the event.
| Variant | Use when | Payload requirement |
|---|---|---|
| Generic | The workflow only needs a custom external event. | Valid JSON and any required paths you configure. |
| Order, Customer, or Product | The workflow needs a native Shopify resource reference. | A configured JSON path to the relevant Shopify ID or GID. |
| Inventory, Fulfillment, Return/refund, or Company/B2B | The workflow belongs in one of those exposed Shopify Flow lanes. | A configured JSON path for the resource identifier FlowRelay resolves. |
Required paths #
Use required paths only for fields the sender must always provide. Missing required values fail early with a stable FlowRelay error instead of becoming a vague downstream workflow issue.
Success check #
The test receipt shows the selected event type, mapped identifier when required, validation result, and whether the matching Shopify Flow trigger was ready.
Delivered means FlowRelay handed the trigger to Shopify Flow. It does not mean downstream Shopify Flow branches, app calls, fulfillment changes, emails, or later systems completed.