Cue + Slack
Team chatThe short version
Cue can post to Slack whenever a QR code is created, changed, or retired — so the whole team knows before a printed code starts pointing somewhere new. The simplest route is through Zapier: Cue notifies Zapier, Zapier posts to your Slack channel. About 15 minutes, no code.
Works on: Business and Enterprise plans (webhooks)
What you can do with Slack
A heads-up when destinations change
The moment anyone repoints a code that's out in the world — on menus, posters, packaging — your campaign channel hears about it, with the code's name and its new destination.
Announce new codes as they go live
New campaign codes appear in the channel as they're created, so print, social, and store teams all work from the same, current list.
A tidy audit trail where the team already looks
Instead of checking a dashboard, the history of who changed what sits in the channel scrollback — alongside the conversation about why.
Before you start
- A Cue Business or Enterprise plan — webhooks are included on both.
- A Zapier account on a plan with premium apps (the "Webhooks by Zapier" trigger), plus your Slack workspace connected to Zapier.
- A Slack channel for the messages — a #campaigns or #marketing channel works well.
Set it up
Create a Zap that listens to Cue
In Zapier, create a Zap with "Webhooks by Zapier → Catch Hook" as the trigger and copy the address it gives you.
Add the address in Cue
In Cue, go to Dashboard → Webhooks, click "New endpoint", paste the address, and tick the updates you want the channel to hear about.
Point it at your channel
Add "Slack → Send Channel Message" as the Zap's action. Write the message using the fields Zapier caught — for example: "🔁 {code name} now points to {destination}". Test it, turn it on, done.
Good to know
- Messages fire when codes are created, changed, or retired — not on every scan, so your channel won't be flooded.
- If your team prefers Microsoft Teams, the identical Zapier recipe works — swap the Slack action for the Teams one.
- A developer can also connect Cue to Slack directly (without Zapier) using a small script — worth it only if you're avoiding a Zapier subscription.
Questions, answered
- Will Slack ping the channel on every single scan?
- No — and that's deliberate. Cue sends updates about the codes themselves (created, changed, retired), not each scan. Scan totals stay in your analytics, where they're useful rather than noisy.
- Do I need Zapier, or can Cue post to Slack directly?
- Through the dashboard, Zapier (or Make) is the no-code route. A developer can wire Cue to Slack directly with a small script — the result is the same message in the same channel.
- Can different channels get different updates?
- Yes. Add a webhook endpoint per audience in Cue — say, all changes to #marketing-ops and only destination changes to #store-managers — each feeding its own Zap.