QR Code Zapier and Webhook Guide: Send Scans Anywhere

A QR code Zapier setup starts with a QR code webhook: QRelix sends a signed webhook the moment a dynamic QR code is scanned, and the QRelix apps for Zapier and Make turn that event into a Google Sheets row, a Slack message, or a CRM update. Webhooks you add in the dashboard work on every plan, while the Zapier and Make apps and the developer API are part of the Team plan.

This guide covers what each scan event contains, how to set up and verify a QR code webhook, how the Zapier and Make apps work, three example automations, and how to create codes from your own software or an AI assistant.

What happens on each QR code scan event

When someone scans a dynamic QR code, QRelix records the scan and sends a qr.scanned event as soon as the scan is recorded. The event is queued while the visitor is redirected, so a webhook never slows down the scan.

Each scan event includes the QR code (its name, type, status, destination, and running scan count) and the scan itself: the time, country, browser, operating system, device, whether it was a mobile device, and the destination the visitor was sent to. A scan event does not include the scanner's name or email address, which matters when you plan a lead workflow (more on that below).

Scans are not the only events. You can also subscribe to:

• qr.created when a new QR code is created.
• qr.updated when a code's name, destination, or settings change, with a list of the changed fields.
• qr.deleted when a code is deleted.
• qr.status_changed when a code is paused, resumed, or expired.
• webhook.test, sent on demand from the dashboard to check an endpoint.

The full list with sample payloads is in the webhooks documentation.

Set up a QR code webhook

A webhook pushes a JSON message to a URL you choose. You need to be the owner or an admin of the workspace.

1. Open Integrations in the dashboard.
2. In the Webhook endpoints card, click Add endpoint.
3. Paste the endpoint URL that should receive events. It must start with https:// and resolve to a public address; local and private network addresses are rejected.
4. Add a description, such as "Order system".
5. Under Events, tick what you want, for example QR code scanned.
6. Leave Only for on All QR codes, or pick a single code.
7. Click Add endpoint, then copy the Signing secret from the dialog.
8. Click Send test event and check that your receiver answers with a 2xx status.

You can add up to 20 endpoints per workspace.

Signing: prove the request came from QRelix

Every request carries an X-QRelix-Signature header in the form t=timestamp,v1=signature. The signature is an HMAC-SHA256 of the timestamp, a period, and the raw request body, using your signing secret. Your receiver should compute the same value over the raw body exactly as received, compare in constant time, and reject timestamps older than five minutes. The docs include a ready-to-use Node.js function. If you rotate the secret on the endpoint page, deliveries from that moment on are signed with the new one.

Each event also has a stable id that is reused for every retry and every endpoint, so you can safely skip duplicates.

Retries and the delivery log

A delivery succeeds when your endpoint answers with any 2xx status within 10 seconds. Redirects, other status codes, timeouts, and connection errors count as failures. A failed delivery is retried after 1 minute, 5 minutes, 30 minutes, 2 hours, and 8 hours: six attempts in total over roughly ten hours.

If ten deliveries in a row use up all their retries, the endpoint is paused automatically and the reason is shown on its page. Events are not queued while an endpoint is paused, so fix the receiver and click Resume endpoint promptly. Every attempt, response code, and error is kept in the delivery log for 30 days, and you can resend any delivery with one click.

QR code Zapier and Make setup

If you do not want to host a receiver, the QRelix apps for Zapier and Make do it for you. They connect with an API key, so they need the Team plan.

1. In Integrations, click Create key in the API keys card, name it "Zapier" or "Make", and copy the key.
2. In Zapier or Make, add the QRelix app and paste the key when it asks for a connection.
3. Pick a trigger. In Zapier: New Scan, New QR Code, Updated QR Code, Deleted QR Code, or Updated QR Code Status. In Make: the Watch events module, then choose the events.
4. Turn the Zap or scenario on.

The app registers a webhook endpoint for you, and it shows up in your endpoint list labelled with its source. More detail is on the QRelix Zapier integration page.

Worked example: a bakery sends QR code scans to Google Sheets and Slack

A neighborhood bakery prints a dynamic QR code on its pastry boxes that opens its catering order page. The owner wants a running log of scans and a heads-up when people engage.

Automation 1: send QR code scans to Google Sheets. In Zapier, the trigger is QRelix New Scan. The action is Google Sheets Create Spreadsheet Row, with columns for scan time, code name, country, device, and destination. Every scan of the pastry box code becomes a row, which makes it easy to chart scans by day or compare codes over a season.

Automation 2: QR code scan notifications in Slack. A second Zap uses the same New Scan trigger with a Slack Send Channel Message action: "Someone just scanned the pastry box code on an iPhone in the US." If the bakery later wants alerts for one code only, a dashboard webhook with Only for set to that code does it.

Automation 3: a CRM activity, with a form for the lead. A scan tells you a code was used, not who used it. So the bakery logs each scan as an activity on its "Catering" campaign in its CRM, and puts a short request form on the catering page. The form, not the scan, creates the actual lead. Our guide to QR code lead capture walks through that part.

Prefer Make? The same three flows work with the Watch events module followed by Google Sheets, Slack, and CRM modules.

Create QR codes in code with the developer API

The QRelix API lets your own software create dynamic QR codes, change their destinations, read scans and statistics, download images, and manage webhook endpoints. It is the same API the Zapier and Make apps use.

1. In Integrations, click Create key and choose only the permissions the integration needs: read QR codes, create and edit QR codes, read scan analytics, or manage webhooks.
2. Copy the key. It starts with qrx_ and is shown only once.
3. Send it as a Bearer token to https://www.qrelix.com/api/v1. A request to /me confirms the key works.
4. Create a code with a POST to /qr-codes, giving a type, a name, and the fields for that type.

Send an Idempotency-Key header on POST requests so a retried request never creates a duplicate. For real-time scans, subscribe a webhook to qr.scanned instead of polling the scans endpoint. The developer overview and an OpenAPI spec are available for tools like Postman.

Manage QR codes from an AI assistant with the MCP server

The QRelix MCP server connects Claude, ChatGPT, Cursor, and other assistants that support the Model Context Protocol. Add https://mcp.qrelix.com/mcp as a connector, sign in with your QRelix account, and ask in plain English: "Create a QR code for our spring sale page" or "Which QR code has the most scans?"

The assistant can create URL codes, update destinations, pause codes, read analytics, create up to 100 URL codes in one request, and point a whole group of codes at a new URL. MCP tools run on Pro or Team, so you do not need Team for this one.

Limits and when not to use it

• Free codes send at most 50 scan events each, because a free code pauses after its first 50 scans until you upgrade.
• A scan is not a contact. Events carry device, country, and destination data, never a name or email. Use a form for leads.
• Paused endpoints do not replay. Events from the paused period are not delivered later.
• API limits: 120 requests per minute per key, 10 active keys, and 20 webhook endpoints per workspace. MCP allows 60 requests per minute.
• Not a developer? You probably do not need the API. Zapier, Make, or a dashboard webhook covers most automations.

What it costs

• Free plan (no credit card): dashboard webhooks, full scan analytics with CSV export, and editable destinations. Each free code works for its first 50 scans, then pauses until you upgrade, and free scans show a brief QRelix screen first.
• Pro, $5.99 a month or $59.99 a year: unlimited scans, no QRelix screen, Smart Routing, conversion pixels, and access to the MCP server.
• Team, $19 a month with 3 seats ($6 a month per extra seat): everything in Pro plus the developer API, Zapier and Make, a shared workspace with roles, custom domains, and bulk creation from CSV.

See pricing for the full comparison.

Frequently asked questions

Can I send QR code scans to Zapier on the free plan?

Not through the Zapier app, which needs the Team plan. You can add a dashboard webhook on any plan, including Free, and point it at a receiver of your own.

Does a webhook slow down the scan?

No. The event is queued while the visitor is redirected and delivered after the redirect is sent.

Can I get notifications for just one QR code?

Yes. Set Only for to a single code when you add or edit the endpoint, or pass a qrCodeId through the API.

How many times does QRelix retry a failed webhook?

Six attempts in total over roughly ten hours: the first try, then retries after 1 minute, 5 minutes, 30 minutes, 2 hours, and 8 hours.

Do webhooks cost extra?

No. Webhooks you add in the dashboard are included on every plan.

Start automating your QR code scans

Create a trackable code with the QR code generator, add a webhook in Integrations, and watch your first scan arrive. When you are ready for Zapier, Make, and the API, upgrade to Team from pricing. For more ideas, read how to create a QR code with tracking and how to use QR codes for event marketing.