Resources · Make integration

Canny Make integrationAutomate Canny with Make.

Can Make keep your Canny board moving while you work elsewhere? The Canny Make integration gives you 32 modules: 4 triggers, 19 actions and 9 searches. This page shows product and support teams how to connect Canny, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Canny Make integration do?

The Canny Make integration links your Canny account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick: a trigger that starts the run, an action that changes something in Canny, or a search that reads data. Canny posts, votes, comments and users can then flow to your other tools without copy and paste.

Close the loop with voters. Watch Status Changes spots a post that moved to a new status, and Create a Comment leaves a note on it. People who follow the request see the update where they voted.

Turn support tickets into requests. When a customer asks for a feature in your help desk, Search Posts checks whether the request already exists. If it does, Create a Vote adds the customer's vote on their behalf; if not, Create a Post opens it on the right board.

Keep your team informed. Watch Comments and Watch Votes react the moment something happens in Canny, so a new comment or vote can reach your chat tool, your CRM or a spreadsheet.

The listed modules do not cover every part of the Canny API. For the rest, Make an API Call reuses your connection to reach any endpoint. Canny may also exist as a node in n8n; if you are still choosing between the two tools, read n8n vs Make. New to the editor? The Make training walks you through it, and the Make pricing page explains how operations are counted.

Connect

How do you connect Canny to Make?

  1. 01

    Copy your Canny API key

    You need an active Canny account. In Canny, open your company's settings panel, select the API section and copy the API key shown on screen. Keep it at hand: Make asks for it once, then reuses it.

  2. 02

    Add a Canny module in Make

    Log in to Make, add any Canny module to your scenario and click Create a connection. A connection is your Canny account linked to Make; every Canny module in every scenario can reuse it.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several Canny workspaces. Paste the API key you copied, or follow the on-screen instructions, and save. The module can now read your boards and posts.

First scenario

Your first scenario: comment on a post when its status changes

GoalWhen a post changes status in Canny, Make leaves a comment on that post so anyone following it sees the news.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for Canny and pick Watch Status Changes as the first module.

  2. 02

    Link your Canny account

    Click Create a connection and paste your API key. Once the connection exists, Make can read your Canny data and fill the module's lists for you.

  3. 03

    Add the comment

    Click the + on the right of the trigger and add Create a Comment. Map the post from the bundle (one item passed from module to module) that Watch Status Changes returned, then write your message.

  4. 04

    Test with Run once

    Change a test post's status in Canny, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the comment before going live.

  5. 05

    Schedule and switch on

    Watch Status Changes is a scheduled trigger, so open the clock on the first module. A new scenario checks every 15 minutes by default; keep it or adjust it, then switch the scenario on.

Triggers

What can start a Canny scenario?

4 modules start a scenario when something happens in Canny. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Canny as soon as it happens.

Canny1Watch Comments

Watch Comments

Instant trigger

In MakeTriggers when a new comment is created or deleted.

Every comment written or removed under a Canny post can start your scenario, so the discussion around a request reaches the tools your team already reads.

How it fires
instant, Canny calls Make through a webhook as soon as it happens. You will see the lightning badge on the module.
When to use it
your support lead wants each new comment on a feature request posted in the team chat.
Watch out
deleted comments fire it too, so plan for both cases in the modules that follow.
Canny2Watch Posts

Watch Posts

Instant trigger

In MakeTriggers when a new post is created, modified or deleted.

You get a run each time a post is created, edited or deleted in Canny, which makes it the widest trigger of the app and the natural entry point for triage.

How it fires
instant, Canny calls Make through a webhook as soon as it happens.
When to use it
a new request lands on your board and you want it logged in your product backlog without anyone copying it by hand.
Watch out
if the same scenario later edits the post, for example with Change Post Status, that edit can start it again.
Canny3Watch Status Changes

Watch Status Changes

Scheduled trigger

In MakeWatches status changes.

Status moves on your posts become bundles you can act on: announce what shipped, update a roadmap sheet, or tell the customer who asked.

How it fires
scheduled, Make checks Canny on the scenario's schedule, every 15 minutes by default, shown by the clock badge.
When to use it
the product team marks a request as done and your customer success team should hear about it without watching the board.
Watch out
changes are picked up at the next check, not the second they happen; on the Free plan the shortest interval is 15 minutes.
Canny4Watch Votes

Watch Votes

Instant trigger

In MakeTriggers when a new vote is created.

A fresh vote on any post can kick off your scenario, which lets you see demand building up the moment it happens instead of reading totals later.

How it fires
instant, Canny calls Make through a webhook as soon as it happens.
When to use it
your account managers want a heads-up in the CRM when one of their customers backs a request.
Watch out
it reacts to new votes only. To review votes cast before the scenario existed, use Search Votes instead.
Modules

What can Make do in Canny?

Canny gives you 28 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Canny1

Add Post Tag

Action

In MakeAdds a tag to a post.

Posts get sorted without anyone opening them: this module sticks one of your tags on a post, so filters in Canny show the right requests to the right team.

When to use it
Watch Posts catches a new request and you want everything coming from a key account labeled for the next product review.
Watch out
if the tag does not exist yet, create it first with Create a Tag.
Canny2

Change Post Status

Action

In MakeChanges status of a post.

Your board stays accurate on its own: this action moves a post to another status, so voters see progress without a product manager updating it by hand.

When to use it
the matching task gets closed in your project tool and the Canny request should follow.
Watch out
a status change edits the post, so a scenario that starts on Watch Posts can fire again on its own change.
Canny3

Create a Comment

Action

In MakeCreates a comment.

People following a request get an answer right where they voted, because this action writes a comment under the post you choose.

When to use it
a support ticket linked to the request is solved, and you want the workaround shared on the post for everyone else who asked.
Watch out
a scenario that starts on Watch Comments and ends here can trigger itself, so keep the two apart.
Canny4

Create a Post

Action

In MakeCreates a post.

Feedback that arrives outside Canny becomes a real request that others can find and vote on. The module opens a new post on the board you pick.

When to use it
a form, a sales call note or a help desk ticket carries an idea that belongs on your public board.
Watch out
run Search Posts first, otherwise the same idea can end up posted twice.
Canny5

Create a Tag

Action

In MakeCreates a tag.

New labels appear in Canny without a trip to the settings, since this action adds a tag you can then place on posts.

When to use it
a new product area or customer segment shows up in your other tools and your requests need a matching label.
Watch out
check with List Tags or Get a Tag before creating one, so you do not end up with two tags under the same name.
Canny6

Create a Vote

Action

In MakeAdd a vote to a post on someone's behalf.

Customers who ask for a feature by email or on a call still count in Canny: this action adds a vote to a post on their behalf.

When to use it
your sales team logs a request in the CRM and the demand should show up on the matching Canny post.
Watch out
the vote needs a person behind it; if that customer is not in Canny yet, Create or Update a User can add them first.
Canny7

Create or Update a User

Action

In MakeCreates a new user or updates an already existing user.

Canny knows who your customers are, and one module handles both cases: it creates the user when they are new and updates them when they already exist.

When to use it
someone signs up for your product, and their Canny profile should exist before they vote or comment.
Watch out
since it also updates existing users, a value you map is likely to replace the one already in Canny, so map only what you trust.
Canny8

Delete a Comment

Action

In MakeDeletes a comment.

Spam and duplicate replies disappear from your board without a moderator scrolling through posts. This action removes one comment for good.

When to use it
a moderation step in another tool flags a comment, and Canny should drop it too.
Watch out
a deletion cannot be undone from Make. Test with Run once on a dummy comment before switching the scenario on.
Canny9

Delete a Company

Action

In MakeDeletes a company.

Your Canny data stays in line with your customer list, because this action removes a company that no longer belongs there.

When to use it
an account is closed or merged in your CRM and the company record in Canny should go as well.
Watch out
nothing comes back after a delete. Let the scenario act only on accounts your CRM marks as closed, and test it with Run once first.
Canny10

Delete a User

Action

In MakeDeletes a user.

Removing a person from Canny becomes one step of a wider cleanup: this module deletes the user you point it to.

When to use it
a customer asks to have their data removed and your process covers every tool, Canny included.
Watch out
the action is final. Find the right user first with Get a User, which accepts a Canny ID, an ID or an email.
Canny11

Delete a Vote

Action

In MakeDeletes a vote.

Vote counts stay honest, since this action takes back a vote that should not be there.

When to use it
a vote was added by mistake through Create a Vote, or a customer changed their mind during a call with your team.
Watch out
identify the exact vote with Search Votes or Get a Vote before deleting it, since a removed vote cannot be restored from Make.
Canny12

Get a Board

Action

In MakeRetrieves a board.

You get the full record of one board when the previous module only hands you a reference to it, which makes messages and reports easier to read.

When to use it
a post arrives through a trigger and your notification should say which board it belongs to.
Watch out
it returns one board; to go through all of them, List All Boards is the right module.
Canny13

Get a Comment

Action

In MakeRetrieves a comment.

One comment, read in full, is what this module brings back, ready to pass on to the next module of your scenario.

When to use it
a bundle from another module points to a comment and you need its content before sending it to your help desk.
Watch out
it needs to know which comment you want; to scan many at once, Search Comments does the job.
Canny14

Get a Post

Action

In MakeRetrieves the details of an existing post, specified by its ID.

The full details of an existing post, found by its ID, land in your scenario so every module after it can use them.

When to use it
Watch Votes tells you a request got a new vote and your CRM note should quote the request itself.
Watch out
the module expects an ID, so map it from an earlier bundle rather than typing it by hand.
Canny15

Get a Tag

Action

In MakeRetrieves a tag.

This module returns a single tag with its details, handy when a scenario must confirm a label before acting on posts.

When to use it
before Add Post Tag, you want to be sure the label your scenario plans to use is the right one.
Watch out
it reads one tag at a time; List Tags gives you the whole set in one go.
Canny16

Get a User

Action

In MakeRetrieves the details of an existing user by Canny ID, ID or Email.

You can find a Canny user from what you already have: a Canny ID, an ID or an email address. The profile then feeds the next modules.

When to use it
your CRM only stores the customer's email and you need their Canny record before adding a vote.
Watch out
an email may match no profile at all, so test that case with Run once before switching on.
Canny17

Get a Vote

Action

In MakeRetrieves a vote.

A single vote comes back with its details, which helps when you need to know who backed what before writing to them.

When to use it
a report lists vote references and you want the full record of one before your team contacts that customer.
Watch out
for all the votes on a post, Search Votes is faster than calling this module many times.
Canny18

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Whatever the listed modules miss, this one reaches: it sends an authorized request to any endpoint of the Canny API, using the same connection as the others.

When to use it
you need a Canny feature that no module in this list covers.
Watch out
you describe the request yourself, so keep the Canny API documentation open while you set it up.
Canny19

Remove Post Tag

Action

In MakeRemoves a tag from a post.

Labels that no longer apply come off automatically: this action takes one tag off a post and leaves the post itself untouched.

When to use it
a request leaves triage and the temporary label your team uses for new items should disappear.
Watch out
removing a tag edits the post, so it can wake up a scenario that starts on Watch Posts.
Canny20

List All Boards

Search

In MakeReturns a list of all boards associated with your company, in no particular order.

One search brings back every board of your company. The order is random, which is fine when your scenario goes through them all.

When to use it
you build a report that covers each board, or you need to find a board by its name.
Watch out
each board is its own bundle, and every module after it runs once per board, which adds operations to your plan.
Canny21

List Changelog Entries

Search

In MakeRetrieves a list of changelog entries. Sorted by newest.

Your release notes can travel beyond Canny: this search returns changelog entries, newest first, ready to go to a newsletter or a help center.

When to use it
your marketing team publishes a digest and wants the latest Canny entries in it.
Watch out
the list can hold many entries; keep only the ones you have not sent yet before passing them on.
Canny22

List Opportunities

Search

In MakeLists opportunities.

The opportunities tracked in Canny come out as bundles, so sales and product work from the same list, each in their own tool.

When to use it
your revenue team wants opportunities in a spreadsheet next to the requests they relate to.
Watch out
a search can return zero, one or several bundles, and each bundle costs an operation in the next module.
Canny23

List Status Changes

Search

In MakeRetrieves a list of status changes. Sorted by newest.

You can pull the history of status changes on demand, newest first, in the middle of any scenario.

When to use it
a report built from another trigger needs the recent moves on your board, and Watch Status Changes would only catch new ones.
Watch out
older changes come back too, so limit what you keep before writing them anywhere.
Canny24

List Tags

Search

In MakeRetrieves a list of tags.

This search gives you the tags that exist in your Canny account, which is the safest way to know what labels you can use.

When to use it
before Create a Tag, you check that the label is really missing.
Watch out
each tag becomes a bundle; if you only need to know whether one exists, add an aggregator (a Make tool that groups bundles) after it.
Canny25

List Users

Search

In MakeLists users.

The people in your Canny account come out as a list you can copy, compare or clean up in another tool.

When to use it
you want to match Canny users with your customer base in a spreadsheet or your CRM.
Watch out
every user is a separate bundle, so a large list uses operations quickly in the modules that follow.
Canny26

Search Comments

Search

In MakeReturns a list of comments.

You get the comments you are looking for without reading each post. The search returns them as bundles for your next modules.

When to use it
your support team wants all the discussion on one request collected in a document before a customer call.
Watch out
an empty result stops the modules that follow for that run, which is normal and not an error.
Canny27

Search Posts

Search

In MakeReturns a list of posts.

Duplicates stay off your board, since this search finds existing posts before your scenario decides to create a new one.

When to use it
a help desk ticket describes an idea and you want to know if a matching request is already in Canny.
Watch out
the search can return several posts; decide which one your scenario keeps before adding a vote.
Canny28

Search Votes

Search

In MakeReturns a list of votes.

Who backed which request becomes visible outside Canny: the search returns votes as bundles you can send to a sheet or a CRM.

When to use it
a feature ships and your team wants the list of customers who voted for it.
Watch out
each vote is its own bundle, and every module after it runs once per vote, which counts as operations.
Need help

Need help automating Canny with Make?

A person reads every message.

FAQ

Canny and Make: common questions

01Is the Canny Make integration free?
Yes, Canny is a standard app in Make, available from the Free plan. That plan gives you 2 active scenarios, 15 minutes minimum between two scheduled runs and up to 5 minutes per execution. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. You still need an active Canny account with API access; Canny's own pricing is set by Canny, not by Make.
02What do you need to connect Canny to Make?
An active Canny account and its API key. In Canny, open your company's settings panel, select the API section and copy the key. In Make, add a Canny module, click Create a connection, optionally fill Connection name, and paste the key. The connection is then shared by every Canny module. For the three instant triggers, click Create a webhook first and create the connection from that window. The scheduled trigger, Watch Status Changes, only needs the connection.
03Do Canny triggers in Make react in real time?
Three of them do. Watch Comments, Watch Posts and Watch Votes are instant: Canny calls Make through a webhook as soon as something happens, and the module shows a lightning badge. Watch Status Changes is scheduled: Make checks Canny on the scenario's schedule, every 15 minutes by default, with a clock badge on the module. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. Pick an instant trigger when speed matters.
04What if a Canny module is missing in Make?
Use Make an API Call. It sends an authorized request to any endpoint of the Canny API with the connection you already set up, so you are not limited to the 32 listed modules. You write the request yourself, so keep the Canny API documentation open. If what you need is a combination of existing modules, a search followed by an action often covers it without any API work. The Make documentation for Canny also warns that its content is AI-generated, so check important details with Canny.
05Should you use Make or n8n for Canny?
It depends on the tool your team already runs. In Make, Canny comes with 32 ready modules, three instant triggers and Make an API Call for anything else, all available from the Free plan. Canny may also be available as a node in n8n; check what that node covers for your use case before deciding. Compare the modules you need on each side, how your team likes to build, and where your other automations already live.