Resources · Make integration

KanbanFlow Make integrationAutomate KanbanFlow with Make.

What if your board updated itself when work moved elsewhere? The KanbanFlow Make integration gives you 8 modules: 2 instant triggers, 5 actions and 1 search. This guide is for teams who run their work on KanbanFlow and want a first working scenario.

Try the KanbanFlow integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the KanbanFlow Make integration do for your board?

The KanbanFlow Make integration links your KanbanFlow account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. With it, tasks on your board can be watched, created, read, updated, listed and deleted without writing code.

Tasks created from the tools you already use. A request lands in another app, and Create a Task turns it into a card on your board, so nobody retypes it. The Make training walks through that kind of mapping step by step.

A reaction every time a card changes column. Watch Task Moved fires as soon as someone drags a task between columns or swimlanes. That is the moment to alert the next person in line, or to fetch the full card with Get a Task and pass its details on.

A clean board after the fact. List Tasks returns the cards that match your filter as separate bundles (one bundle is one item passed from a module to the next), and Update a Task or Delete a Task then acts on each one.

What Make does not do here: the listed modules cover tasks only. Anything else the KanbanFlow API exposes goes through Make an API Call, with the same connection. The doc gives no numeric limit for this app, and the Make troubleshooting guide helps when a run fails.

KanbanFlow may also have a node on n8n. If you are weighing both tools, the n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect your KanbanFlow account to Make?

  1. 01

    Add a KanbanFlow module

    In your scenario, click the + and search for KanbanFlow, then pick any of its modules. Make shows a field for the connection, which is your KanbanFlow account linked to Make once and reused by every KanbanFlow module. Click Create a connection.

  2. 02

    Name the connection

    This step is optional, but a clear name pays off later when you look at the list of connections. Something like the name of the board or of the team that owns the account tells you at a glance which one a module is using.

  3. 03

    Authorize Make and save

    Depending on what Make asks, either approve access on the KanbanFlow page that opens, or paste the key that KanbanFlow gives you. Then click Save. The module now reads your account and offers its values in dropdowns.

First scenario

Build your first scenario with KanbanFlow

GoalWhen a request arrives in another app, Make creates the matching task on your KanbanFlow board.

  1. 01

    Create the scenario

    Open the Scenarios page and create a new scenario. Click the big + to add the first module: here, the trigger of the app where your requests arrive, such as a form tool.

  2. 02

    Set up the first module

    Search that app by name, choose its trigger and link your account with Create a connection. Fill in its fields; Make lists what it can read once the connection exists.

  3. 03

    Add Create a Task

    Click the + on the right of the first module, search for KanbanFlow and pick Create a Task. Create your KanbanFlow connection as shown above if you have not done it yet.

  4. 04

    Map the request onto the task

    Fill the fields of Create a Task by clicking into each one and choosing data from the first module. Make offers the values it received, so the title of the request can become the name of the card.

  5. 05

    Test with Run once

    Click Run once, then send one test request in the other app. Open the bubbles above each module to read the bundles they received, and check that the card appeared on your board.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module (a new scenario runs every 15 minutes by default) and switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Triggers

What starts a KanbanFlow scenario

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

KanbanFlow1Watch New Tasks

Watch New Tasks

Instant trigger

In Make“Triggers when a new task is created.”

You get a scenario that starts the moment a task is added to KanbanFlow, carrying that new card into the rest of your flow as one bundle.

How it fires
instant, which means KanbanFlow calls Make through a webhook as soon as the task is created; you will see a lightning badge on the module.
When to use it
pick it when a new card should be announced or copied somewhere, for example posting every fresh bug report into the channel your developers read.
Watch out
it reacts only to creation, so a card that later changes column will not fire it again.
KanbanFlow2Watch Task Moved

Watch Task Moved

Instant trigger

In Make“Triggers when a task is moved between columns or swimlanes.”

This one hands you the exact moment work changes stage: a card dragged to another column or to another swimlane starts the scenario with that task in hand.

How it fires
instant, KanbanFlow calls Make through a webhook as soon as the move happens, shown by the lightning badge.
When to use it
choose it over Watch New Tasks when the move itself means something, like a card reaching the review column and the reviewer needing a heads up.
Watch out
every move fires it, between columns as well as between swimlanes, so expect more runs than the moves you actually care about.
Modules

What KanbanFlow can do inside Make

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

KanbanFlow1

Create a Task

Action

In Make“Creates a new task.”

A new card appears on your board with data taken from earlier modules, so requests collected elsewhere stop being copied by hand.

When to use it
a form submission, an email or a signed deal should become a task your team can pick up.
Watch out
if the trigger can fire twice for the same request, you get two cards; test with Run once first.
KanbanFlow2

Delete a Task

Action

In Make“Deletes a specified task.”

Removes the card you point to. Your board stays free of tasks nobody needs anymore, without anyone clicking through them one by one.

When to use it
once List Tasks has found the cards to drop. Think of the duplicates an old test left behind.
Watch out
a deleted task is gone for good. Try the module on a test card first, then point it at real ones.
KanbanFlow3

Get a Task

Action

In Make“Returns information about a specified task.”

Returns everything Make can read about one task you already know, handy when a trigger or another module gives you only part of the picture.

When to use it
right after Watch Task Moved, to pull the full card before sending its details to a colleague or another tool.
Watch out
it needs a specific task to read; to find cards you have not identified yet, List Tasks is the right module.
KanbanFlow4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the KanbanFlow API with the connection you already set up, which covers what the seven other modules leave out.

When to use it
you need something from KanbanFlow that is not a plain task operation, and no listed module offers it.
Watch out
you build the request yourself, so keep the KanbanFlow API documentation open while you fill it in.
KanbanFlow5

Update a Task

Action

In Make“Updates information about a specified task.”

Changes the information of an existing card instead of creating a second one, so the board keeps a single, current version of each task.

When to use it
a status or a detail changes in another app and the matching card should reflect it.
Watch out
you must tell it which task to change; store or look up the task first, with Get a Task or List Tasks.
KanbanFlow6

List Tasks

Search

In Make“Returns a list of tasks.”

Gives you a set of tasks from your account, each passed on as its own bundle, so the next module handles them one by one.

When to use it
a tidy-up or a report where you want to act on several cards at once rather than on one known card.
Watch out
as a search, it can return zero, one or many tasks, and each returned task costs an operation in every module that follows.
Need help

Need help automating KanbanFlow with Make?

A person reads every message.

FAQ

KanbanFlow and Make: common questions

01Is the KanbanFlow Make integration free?
Yes, KanbanFlow is a standard app in Make, so it works on the Free plan, like the 3,000+ other standard apps. The Free plan has its own limits: 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Usage is counted in credits, meaning operations, per month.
02What does it take to connect KanbanFlow to Make?
You need a KanbanFlow account and a Make account. The doc lists no other prerequisite. Add any KanbanFlow module, click Create a connection, optionally give it a name, then either approve access on the KanbanFlow page or paste the key KanbanFlow provides, depending on what Make asks. Click Save and the connection is ready. That single connection is reused by every KanbanFlow module in your scenarios, so there is no need to repeat the process for each module you add later.
03Does the KanbanFlow trigger in Make fire in real time?
Yes. Both KanbanFlow triggers are instant: Watch New Tasks and Watch Task Moved rely on KanbanFlow calling Make through a webhook as soon as the event happens, which the editor marks with a lightning badge. There is no scheduled KanbanFlow trigger, so Make does not need to check the board at an interval to catch a new or moved card. If your scenario starts from another app instead, that app decides whether it runs on a schedule or instantly.
04What if a KanbanFlow module is missing in Make?
It depends on what you need. The 8 modules focus on tasks: watch new ones, watch moves, create, read, update, list and delete. For anything else the KanbanFlow API offers, use Make an API Call, which reaches any endpoint of the API with the connection you already created. The official doc gives no numeric limit for this app, so there is no documented ceiling to plan around. Keep the KanbanFlow API documentation at hand when you write the call yourself.
05Make or n8n for KanbanFlow: which one fits?
It depends on where the rest of your automations live. On the Make side, this page lists what the integration offers: 2 instant triggers, 5 actions and 1 search, with Make an API Call to reach the rest of the API. The same app often has an n8n node too, so check the n8n catalog before you decide. If your team already builds its scenarios in one of the two tools, keeping KanbanFlow there avoids splitting your flows across two places.
Same platform

Other docs you might need on this stack.

Browse all integrations