Install FlowRelay, create one test endpoint, and keep its URL and generated authentication value private.
Make setup guide
Connect Make to Shopify Flow through FlowRelay.
Use Make’s HTTP v4 Make a request module to send one authenticated JSON event to a FlowRelay endpoint. FlowRelay checks the request, maps the event, and hands the External event trigger to Shopify Flow. The receipt records whether that handoff happened.
Make the first test harmless.
Prove the transport and handoff before any live schedule, production trigger, or business-changing Shopify Flow action depends on it.
Create a workflow with FlowRelay’s External event trigger and a Log output action. Log only the synthetic event type or summary.
A Make scenario you can edit, with Run once available and no live schedule required for the first test.
Configure FlowRelay and Shopify Flow once.
Use the same endpoint mapping for the first synthetic send. Later, replace the sample values with fields from the real Make workflow.
- Endpoint name
- Make test to Shopify Flow
- Source label
- Make
- Trigger variant
- Generic
- Default event type
- make.synthetic.test
- Mapped paths
- event.type, event.id, event.occurred_at, event.summary
- Required paths
- event.id and event.type
- Authentication
- Static header for this guide; prefer HMAC when the sender can sign exact request bytes
In Shopify Flow
- Create a workflow and choose FlowRelay from the installed app triggers.
- Select External event, which matches the Generic endpoint variant.
- Add a Log output action with a synthetic field such as Event type or Summary.
- Save and enable the workflow before sending the test event.
Configure Make to send the request.
Use Make’s API key keychain with header placement so the FlowRelay static secret is stored as a reusable credential instead of typed into the module’s custom headers.
-
01
Add HTTP v4: Make a request
Place it after a controlled source module. Keep the scenario schedule off while you prove the first event.
-
02
Create an API key credential
Choose API key authentication. Put the generated FlowRelay static secret in Key, choose header placement, and use the endpoint’s exact configured header name as the API key parameter name.
-
03
Set POST and JSON
Paste the private FlowRelay endpoint URL, choose POST, set Body content type to application/JSON, and use a Data structure or JSON string for the synthetic body below.
-
04
Stop on an HTTP failure
In Advanced settings, set Return error if HTTP request fails to Yes so a 4xx or 5xx response does not look like a completed scenario step.
-
05
Run the module once
Send the synthetic event, then verify the Make execution, FlowRelay receipt, and Shopify Flow run as three separate facts.
Use synthetic JSON for the first send.
The values below contain no customer, order, token, endpoint, or merchant data. Replace the timestamp with the current test time if that helps you find the run.
{
"event": {
"type": "make.synthetic.test",
"id": "make-test-001",
"occurred_at": "2026-07-29T15:00:00Z",
"summary": "Synthetic Make to Shopify Flow test"
}
}
| Field | Value |
|---|---|
| Module | HTTP v4 → Make a request |
| Authentication type | API key |
| API key placement | In the header |
| URL and method | Private FlowRelay endpoint URL; POST |
| Body | application/JSON; Data structure or JSON string |
| Failure behavior | Return error if HTTP request fails → Yes |
Verify three different facts.
A successful sender request, a FlowRelay handoff, and a completed Shopify Flow workflow are not the same fact.
- 1Make
The test execution reached the HTTP step and received a 2xx response.
- 2FlowRelay receipt
Authentication, required fields, mapping, Flow readiness, and handoff show the expected state.
- 3Shopify Flow
A separate Recent runs entry shows that the External event trigger started the workflow.
- 4Only then
Replace synthetic values, review side effects, and enable the live schedule or trigger.
Start with the first fact that failed.
Do not change all three systems at once. The earliest missing record identifies where to look next.
- The module never runs
- The route or source module did not reach the HTTP module. Inspect the Make execution before changing FlowRelay.
- The module returns 401 or 403
- Check the keychain’s header parameter name and key against the endpoint’s current static-header credential.
- The module returns 400
- Check that the body content type is application/JSON and that the generated request body is valid JSON.
- Make receives 202 but there is no Flow run
- Open the FlowRelay receipt. A missing event.id or event.type appears there as a mapping failure. Fix a Failed or No workflow receipt first; after Delivered, continue in Shopify Flow.
Sources checked for this guide.
Platform field names and availability were checked against official documentation on July 29, 2026. FlowRelay behavior was checked against the shipped product and current public docs.
Prove one Make event before enabling live traffic.
Use a private credential, a synthetic payload, a harmless Flow action, and the receipt-backed handoff check together.