Reference

Glossary

Plain-language meanings for the FlowRelay terms you see in setup, receipts, recovery, Agent Access, and usage docs.

On this page

Event proof #

Use these terms when you are trying to understand what FlowRelay can prove about one outside event.

Term	Meaning
Receipt	A FlowRelay record for one accepted event. It shows arrival, authentication and mapping outcome, support code when relevant, replay and diagnostics context, and whether FlowRelay handed the trigger to Shopify Flow.
Delivered	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.
Support code	The short, stable code shown on a receipt that names where an event stopped, such as authentication, validation, workflow readiness, or the Shopify Flow handoff. Use it to decide what the next safe action is, and quote it instead of pasting private request details.
Stored durably on arrival	FlowRelay records an accepted event before answering the sender while capacity remains. It is a receipt and retention promise, not proof that Shopify Flow or later systems completed.

Use these terms when you are configuring an endpoint, deciding whether an event can be recovered, or sharing evidence with a partner or support.

Term	Meaning
Source label	The endpoint routing identity surfaced to Shopify Flow. Use it in Shopify Flow conditions when more than one endpoint shares a trigger variant.
Trigger variant	The FlowRelay trigger payload and native-reference shape selected for an endpoint: Generic, Order, Customer, Product, Inventory, Fulfillment, Return/refund, or Company/B2B. These are trigger variants, not event types.
Default event type	The endpoint's fallback event label when no mapped event-type path supplies a value. It does not select the FlowRelay trigger variant.
Resolved event type	The value read from the configured event-type path when present, otherwise the endpoint's default event type. Use it with Source label conditions when workflows share a trigger variant.
Diagnostics share	A redacted support package an operator can preview before sharing. It can include receipt facts, endpoint state, support codes, retention state, replay context, and recovery guidance without exposing raw event bodies, full authentication headers, secrets, tokens, sessions, database URLs, or customer data.
Replay	A deliberate second handoff attempt from retained event material after preview and approval. Use replay when FlowRelay accepted the original event and the event is still replayable; use sender resend when the payload was rejected, wrong, expired, or intentionally new.

Use these terms when an agent is helping with FlowRelay or when a store is close to a plan limit.

Term	Meaning
Scoped grant	A time-bounded Agent Access grant that gives a trusted agent a named set of FlowRelay operations for one store. It is revocable and does not give broad Shopify store authority or raw payload and secret access.
Event grace	The bounded paid-plan buffer after the included accepted-event capacity is reached. Events accepted during grace are still stored, metered, and handed off normally when the receipt path succeeds; FlowRelay does not create silent overage charges.