Envie alertas de escaneo QR a Slack mediante webhooks
Connect QR-Verse webhooks to Slack and receive real-time notifications when someone scans your QR codes, when codes are created or updated, and when your campaigns hit milestone targets. This guide walks you through the setup in five steps.
What You Need
- A QR-Verse account on the Business or Enterprise plan (webhooks require a paid plan).
- A Slack workspace where you have permission to add apps or create Incoming Webhooks.
- At least one dynamic QR code created in QR-Verse.
Step 1: Create a Slack Incoming Webhook
Slack Incoming Webhooks let external services post messages into a channel. You will create one and give the URL to QR-Verse.
- Go to api.slack.com/apps and click Create New App.
- Choose From scratch, give it a name (e.g., "QR-Verse Notifications"), and select your workspace.
- In the sidebar, click Incoming Webhooks and toggle it On.
- Click Add New Webhook to Workspace, pick the channel where you want notifications (e.g., #qr-notifications), and click Allow.
- Copy the Webhook URL. It looks like:
https://hooks.slack.com/services/T00.../B00.../xxxx
Keep this URL private. Anyone with it can post messages to your Slack channel. Do not commit it to version control or share it publicly.
Step 2: Add the Webhook in QR-Verse
- Log in to QR-Verse and go to Account > Settings > Webhooks.
- Click Add Webhook.
- Paste your Slack Incoming Webhook URL in the Endpoint URL field.
- Give it a descriptive name, e.g., "Slack - QR Notifications".
- Click Save.
Step 3: Choose Your Events
QR-Verse can send webhooks for five event types. Select the ones you want to receive in Slack:
scan.created
Fires every time someone scans one of your QR codes. Includes the QR code ID, scan location (country/city), device type, and timestamp.
qr.created
Fires when a new QR code is created in your account. Useful for teams to track new code creation.
qr.updated
Fires when a QR code destination URL or design is changed. Helps you audit who changed what and when.
qr.deleted
Fires when a QR code is deleted. Important for governance - know when codes go offline.
milestone.reached
Fires when a QR code hits a scan milestone (100, 500, 1000, 5000, 10000 scans). Celebrate wins with your team automatically.
You can select all events or pick only the ones relevant to your workflow. Most teams start with scan.created and milestone.reached.
Step 4: Send a Test Event
After saving your webhook configuration, click the Send Test button next to your webhook. QR-Verse will send a test payload to your Slack channel. You should see a message appear within a few seconds.
If the test succeeds, your Slack channel will show a formatted message with sample event data. If it fails, double-check that the Webhook URL is correct and that the Slack app is still installed in your workspace.
Example Webhook Payload
Here is what a scan.created event looks like when delivered to your webhook endpoint:
{
"event": "scan.created",
"timestamp": "2026-04-21T14:32:00Z",
"data": {
"qr_id": "qr_abc123def456",
"qr_name": "Spring Campaign Menu",
"destination_url": "https://example.com/menu",
"scan": {
"country": "NL",
"city": "Amsterdam",
"device": "iPhone",
"browser": "Safari",
"is_unique": true,
"total_scans": 247
}
}
}Slack automatically formats the JSON. For richer Slack messages, you can route the webhook through a service like Zapier or Make to create Block Kit formatted cards.
Step 5: Monitor and Iterate
Once your webhook is live, you will see notifications flow into your Slack channel. Here are some tips:
- Use a dedicated channel. High-traffic QR codes can generate many scan events. Create a #qr-scans channel to keep your main channels clean.
- Filter by event type. If scan.created is too noisy, consider enabling only milestone.reached for a quieter summary.
- Check delivery logs. In QR-Verse under Settings > Webhooks, you can see delivery history, response codes, and retry status for each webhook.
- Combine with Slack workflows. Use Slack Workflow Builder to trigger follow-up actions when specific messages land in your channel.
Troubleshooting
No messages in Slack
Verify the Webhook URL is correct. Check QR-Verse webhook delivery logs for HTTP error codes. Ensure the Slack app is still installed and the channel exists.
Delayed notifications
QR-Verse delivers webhooks within 5 seconds of the event. If Slack shows delays, check your internet connection or Slack status page (status.slack.com).
HTTP 403 or 404 errors
The Slack Incoming Webhook may have been revoked or the app removed. Recreate the webhook in Slack and update the URL in QR-Verse.
Too many notifications
Disable scan.created and keep only milestone.reached for a quieter experience. Or create separate webhooks for different event types, each going to a different Slack channel.
Frequently Asked Questions
Can I send webhooks to multiple Slack channels?
Yes. Create a separate Incoming Webhook in Slack for each channel, then add each URL as a separate webhook in QR-Verse with different event subscriptions.
Do webhooks work with free plans?
No. Webhooks are available on Business and Enterprise plans only. You can upgrade from your Account Settings at any time.
Is there a rate limit on webhooks?
QR-Verse does not impose a hard rate limit on outgoing webhooks. However, Slack may throttle incoming messages at very high volumes. For high-traffic codes, consider using milestone.reached instead of scan.created.
Can I use this with Microsoft Teams instead of Slack?
The webhook payload is standard JSON, so it works with any service that accepts HTTP POST requests. For Microsoft Teams, use an Incoming Webhook connector in your Teams channel instead of Slack.
Crea tu código QR en segundos
Sin registro, sin tarjeta de crédito. 25 tipos de QR con personalización completa. Mejora a Pro para potencia ilimitada.
Artículos de Ayuda Relacionados
Sigue aprendiendo con estas guías y recursos relacionados.
¿Te Resultó Útil Este Artículo?
Si necesitas ayuda adicional o tienes comentarios sobre esta guía, nuestro equipo de soporte está listo para ayudarte.