Frequently asked questions

Yes. Flow is what runs your automation; this app is the bridge that lets an outside system start it. Flow is free from Shopify.

Yes. Every Webhook Trigger workflow receives events from all your webhooks, so add a condition on Webhook ID in each workflow to pick the one it should respond to.

Either two workflows use the Webhook Trigger without distinct Webhook ID conditions, or your sender retried. History tells you which - two entries means two requests actually arrived. See Duplicate delivery protection.

A field you mapped is not present in the payload. Either send it, or unmap it in Advanced Settings. Full code list in History and troubleshooting.

Yes - turn on Use whole body to pass the entire payload to Flow as a JSON string alongside the four mapped fields. See Payload mapping and Flow variables.

Yes, enable CORS on the webhook. Bear in mind anything in browser JavaScript is public, so do not put a static token in front-end code - use a webhook with no token, or proxy the call through your own backend.

Yes, in invocation history, so you can debug and replay. Sensitive header values are masked. Data returned through our REST API and MCP server is additionally PII-masked - see Developer API and MCP.

Yes - Auth header name in Advanced Settings. Defaults to X-Api-Key. See Authentication.

Further requests are rejected with quota_exceeded until the rolling 30-day window drops below the limit. See Plans and usage.

No. Only accepted invocations count. Tests, replays and suppressed duplicates do not either.

Yes, from the invocation's detail page. Useful for building a workflow, or re-running events that arrived while a workflow was broken.

Webhooks are per store. Recreate it on the other store - it gets its own URL and token. The Export button on the webhook page gives you its configuration to copy from.