Send your first test event

# Send your first test event

Canonical: https://docs.flowrelay.app/getting-started/first-event/
Markdown: https://docs.flowrelay.app/getting-started/first-event.md

Use this guide after an endpoint and safe Shopify Flow workflow already exist. It covers one sender request, its receipt, and the next safe action.

## Steps
Complete these in order.
1. Confirm the existing setup
   Open the existing endpoint and confirm its Source label, trigger variant, default or mapped event type, authentication mode, and enabled Shopify Flow workflow.
2. Send a synthetic event
   Send one test event with synthetic data from the sender, using non-customer values that are safe to store in a test receipt.
3. Inspect the receipt
   Open Event history in FlowRelay and inspect the receipt's authentication, validation, mapping, readiness, and handoff facts.
4. Check downstream results separately
   If the receipt is Delivered, check Shopify Flow separately for any branch or downstream outcome that matters.
5. Follow the receipt outcome
   If the event is rejected, waiting, failed, or in manual review, follow its support code before resending or replaying.

## Verify an existing endpoint
Use this check after endpoint creation, a credential rotation, or another setup change. Use a Shopify store where FlowRelay is installed, a sender you control, and a Shopify Flow workflow that is safe to run. Send synthetic values for the test event, not real customer or merchant data.

- [Install FlowRelay from the Shopify App Store](https://apps.shopify.com/flowrelay-1): If setup is not complete yet, use the end-to-end First endpoint guide before this test-only guide.

## Success check
The receipt shows Accepted, then Delivered. Delivered means FlowRelay handed the trigger to Shopify Flow — after receiving, authenticating, validating, and normalizing the event. It does not show whether the Flow run finished or which branches matched; check that in Shopify Flow.


## If it does not deliver
Use the receipt outcome to pick the next owner instead of retrying blindly.


- Outcome: Authentication failed; Likely owner: Sender and endpoint setup; Next action: Fix the signing or static header setup, then ask the sender to send a fresh test event.
- Outcome: Required field or mapping failed; Likely owner: Sender payload or endpoint mapping; Next action: Fix the payload field path or sender event body. Use a sender resend because FlowRelay rejected the event before a successful handoff.
- Outcome: No matching Shopify Flow workflow; Likely owner: Shopify Flow setup; Next action: Enable the matching FlowRelay trigger, then preview replay if the accepted event is still retained.
- Outcome: Handoff failed; Likely owner: FlowRelay to Shopify Flow boundary; Next action: Read the support code, confirm replay availability, and share diagnostics if support or a partner needs evidence.

## Handoff Boundary
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.

## Related
- [Read receipts](https://docs.flowrelay.app/operate/receipts.md)
- [Support codes](https://docs.flowrelay.app/recover/error-codes.md)
- [Replay an event](https://docs.flowrelay.app/recover/replay.md)

## Safety Boundary
Do not share endpoint secrets, authentication headers, HMAC values, tokens, raw event bodies, customer records, Shopify sessions, store passwords, or database URLs in public examples.