Cue + Make
AutomationThe short version
Cue connects to Make two ways: Make can listen for updates from Cue (a code was created, changed, or retired), and Make can drive Cue — creating codes or changing destinations automatically using Cue's developer access. Listening is a 15-minute, no-code setup; driving Cue is a job for whoever builds your Make scenarios.
Works on: Business and Enterprise plans (webhooks and API)
What you can do with Make
React to code changes anywhere
When a code is created or repointed in Cue, a Make scenario can update your project tracker, notify the client, or refresh a document — across the hundreds of apps Make connects to.
Create codes in bulk
Feed Make a spreadsheet of campaigns and let it create a Cue code for each row — useful when a season launch needs fifty codes, not five.
Switch destinations on a schedule
Have Make change where a code points every Monday morning — weekly offers on the same printed table talker, no reprinting and no early-morning admin.
Before you start
- A Cue Business or Enterprise plan — webhooks and developer access are included on both.
- A Make account (their free plan includes what you need to start).
- For bulk creation or scheduled changes: whoever builds your Make scenarios, since those use Cue's developer tools.
Set it up
Create a scenario with a webhook trigger
In Make, create a new scenario and add the "Webhooks" module as the trigger, choosing "Custom webhook". Make shows you a web address — copy it.
Give that address to Cue
In Cue, go to Dashboard → Webhooks, click "New endpoint", paste the address, tick the updates you want, and save.
Send a test and build from there
Create or edit a code in Cue — Make receives it within seconds. Add whatever modules should come next: a spreadsheet row, a client email, a task in your project tool.
Good to know
- Updates flow when codes are created, changed, or retired — not per scan. Scan totals are in Cue analytics, downloadable any time.
- Bulk creation and scheduled destination changes use Cue's developer access (Dashboard → API) — that part is best set up by whoever runs your automations.
- Make's free plan is enough to receive Cue updates; heavier scenarios may need a paid Make plan.
Questions, answered
- What's the difference between using Make and Zapier with Cue?
- They do the same jobs. Zapier tends to be simpler; Make gives power users more control and is cheaper at volume. Cue connects to both the same way, so pick whichever your team already uses.
- Can Make change where my codes point automatically?
- Yes — Make can update a code's destination through Cue's developer access, on a schedule or in response to anything else Make sees. Setting that up is a technical task, so hand it to whoever builds your scenarios.
- Do I need a developer just to get updates from Cue into Make?
- No. Listening for updates is copy-paste: one address from Make into Cue's dashboard. Only driving Cue (bulk creation, scheduled changes) needs technical help.