Resources · Make integration

Nozbe Make integrationAutomate Nozbe with Make.

Tasks and comments in Nozbe can move on their own. The Nozbe Make integration gives you 12 modules: one trigger, nine actions and two searches. This page shows how to link your account, build a first scenario and pick the right module for each job.

Try the Nozbe integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Nozbe Make integration do for your team?

The Nozbe Make integration links your Nozbe account to Make, a no-code tool where you chain apps into a scenario, the automation you build. Make can spot new tasks, create or update tasks and comments, look them up, and delete them, all without writing code.

Requests that turn into tasks. A form, a support email or a chat message lands in another app, and Create a Task files it in Nozbe with the details already filled in. Nobody retypes anything.

A heads-up for every new task. Watch Tasks picks up each task created in Nozbe, so the scenario can post it to a team channel or add a row to a tracking sheet.

Comments as a shared log. Create a Comment and Update a Comment keep a status note on a task, written by the scenario whenever something changes elsewhere, like a payment or a signed contract.

The listed modules cover tasks and comments only. For anything else the Nozbe API offers, the Make an API Call module reaches it with the same connection. There is no instant trigger either, so Make checks for new tasks on a schedule. If you also weigh n8n, read n8n vs Make first. To learn the editor step by step, the Make training starts from zero, and Make pricing explains how operations are counted.

Connect

How do you connect Nozbe to Make?

  1. 01

    Generate an API token in Nozbe

    In Nozbe, click the gear icon, then Settings and API tokens. Click Add new token, give it a name you will recognize, tick the global option only if your setup needs it, generate it and copy the token shown on screen.

  2. 02

    Add a Nozbe module in Make

    In your scenario, add any Nozbe module and click Create a connection. A connection is your Nozbe account linked to Make once, then reused by every Nozbe module you add later.

  3. 03

    Paste the token and save

    The Connection name field is optional, but a clear name helps when you manage several accounts. Paste the token you copied from Nozbe, confirm, and Make can now read and write your tasks.

First scenario

Your first scenario with Nozbe

GoalWhen a new task is created in Nozbe, Make adds a standard comment to it, such as the checklist the team follows before closing a task.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the editor. Each brick you add is a module: a trigger that starts the flow, an action or a search.

  2. 02

    Add Watch Tasks

    Search for Nozbe, pick Watch Tasks and click Create a connection to paste your API token. This trigger will hand each new task to the next module.

  3. 03

    Add Create a Comment

    Click the + on the right of Watch Tasks and pick Create a Comment. Map the task coming from the trigger, then type the text the team should see on every new task.

  4. 04

    Test with Run once

    Create a test task in Nozbe, then click Run once. Make shows the bundles each module received; a bundle is one item passed along the chain, here one task.

  5. 05

    Schedule and switch it on

    Set the schedule on Watch Tasks (every 15 minutes by default) and switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Triggers

What starts a Nozbe scenario?

1 module starts a scenario when something happens in Nozbe. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Nozbe as soon as it happens.

Nozbe1Watch Tasks

Watch Tasks

Scheduled trigger

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

With Watch Tasks, every task created in Nozbe becomes the starting point of your scenario, passed along as one bundle per task so the next modules can copy it, notify someone or enrich it.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default; the Free plan keeps at least 15 minutes between runs, paid plans go down to 1 minute.
When to use it
your team logs incoming requests as Nozbe tasks and wants each new one echoed to a chat channel or a sheet.
Watch out
the module is described as firing on new tasks, so do not rely on it to catch edits to existing ones.
Modules

Every Nozbe module in Make

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

Nozbe1

Create a Comment

Action

In Make“Creates a new comment.”

You get the context from another tool written straight under the right Nozbe task, so the team reads it where the work happens instead of hunting through an inbox.

When to use it
a client replies to an email or fills a form, and that answer belongs on the task it concerns.
Watch out
point the module at the right task by mapping one from Watch Tasks or Search Tasks earlier in the flow.
Nozbe2

Create a Task

Action

In Make“Creates a new task.”

This one turns an event from any other app into a fresh Nozbe task, so nothing that needs doing stays stuck in a form, a mailbox or a chat thread.

When to use it
a new lead, a support ticket or a signed quote should become an action item for someone on the team.
Watch out
if Watch Tasks runs in the same scenario, tasks you create here will be picked up by it too.
Nozbe3

Delete a Comment

Action

In Make“Deletes the selected comment.”

Old or wrong notes disappear from a task without anyone opening Nozbe, which keeps the comment thread short and readable for the people working on it.

When to use it
a scenario posted a temporary status note and the status has since been resolved.
Watch out
treat the deletion as final and test on a throwaway task with Run once before you switch the scenario on.
Nozbe4

Delete a Task

Action

In Make“Deletes the selected task.”

Tasks that no longer make sense leave the list automatically, for example when the request behind them gets cancelled in another tool.

When to use it
an order is refunded or a meeting is called off, and the matching Nozbe task should go with it rather than sit there forever.
Watch out
if the task you link is the wrong one, that is the one that goes, so find it with Search Tasks first and check the bundle in a Run once test.
Nozbe5

Get a Comment

Action

In Make“Returns information about the selected comment”

Reading one known comment gives the scenario its full content, ready to reuse in an email, a report or a message to a client.

When to use it
you already hold the comment's reference from an earlier module and need its text or details before acting.
Watch out
it reads a single comment; when you do not know which one you need, start with Search Comments instead.
Nozbe6

Get a Task

Action

In Make“Returns information about the selected task.”

Fetching one specific task brings back its current details, so later modules work with fresh data rather than what the trigger saw earlier.

When to use it
a scenario starts from another app that only knows the task reference, and you need the rest of the task to fill a message or a sheet.
Watch out
it expects a task you can point at; to find tasks by criteria, Search Tasks is the better fit.
Nozbe7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the Nozbe API offers but the other modules skip becomes reachable here, using the connection you already set up, so you do not need a second login.

When to use it
the eleven ready-made modules stop at tasks and comments and your scenario needs something beyond them.
Watch out
you write the request yourself, so keep the Nozbe API documentation open and test every call with Run once.
Nozbe8

Update a Comment

Action

In Make“Updates the selected comment.”

A single comment can act as a live status line on a task: the scenario rewrites it each time something changes, instead of stacking new comments.

When to use it
a delivery, an approval or a payment moves forward in another tool and the task should show where things stand.
Watch out
the scenario has to know which comment to edit, so store or search its reference before this step.
Nozbe9

Update a Task

Action

In Make“Updates the selected task.”

Changes made elsewhere reach the matching Nozbe task, so people stop editing the same information in two places.

When to use it
a deal moves stage in your CRM or a deadline shifts in a project sheet, and the Nozbe task has to follow.
Watch out
pair it with Search Tasks or Get a Task so the scenario edits the right task and not the last one it saw.
Nozbe10

Search Comments

Search

In Make“Searches for comments.”

Looking through comments lets the scenario find the notes it needs without you knowing their references in advance.

When to use it
before posting a status update, check whether the scenario already left one on that task and update it instead of adding a duplicate.
Watch out
a search can return zero, one or several bundles, and every following module runs once per bundle.
Nozbe11

Search Tasks

Search

In Make“Searches for tasks.”

Finding tasks from inside the scenario is the usual first move before any update or deletion, because it gives later modules the exact task to act on.

When to use it
an event in another app mentions a client or a project, and you need the Nozbe tasks linked to it.
Watch out
expect zero, one or many results; with many, each next module runs for every task found and uses more operations.
Need help

Need help automating Nozbe with Make?

A person reads every message.

FAQ

Nozbe and Make: common questions

01Is the Nozbe Make integration free?
Yes, on the Make side. Nozbe is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios and lower the interval to 1 minute. You still need an active Nozbe account, whose subscription is handled on the Nozbe side.
02What do you need to connect Nozbe to Make?
An active Nozbe account and an API token. In Nozbe, click the gear icon, then Settings, API tokens and Add new token. Name the token, choose the global option only if your setup requires it, generate it and copy it from the screen. In Make, add a Nozbe module, click Create a connection, give the connection a name if you like and paste the token. The same connection then serves every Nozbe module in your scenarios.
03Does the Nozbe Watch Tasks trigger fire instantly in Make?
No. Watch Tasks is a scheduled trigger: Make checks Nozbe for new tasks at the interval set on the scenario, every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; paid plans allow 1 minute. Nozbe has no instant trigger in Make, so a task created right after a check waits for the next one. If timing matters, move to a paid plan and shorten the schedule on the first module.
04What if a Nozbe module you need is missing in Make?
Use Make an API Call. The ready-made modules cover tasks and comments: create, get, update, delete and search, plus Watch Tasks for new tasks. When your scenario needs another part of the Nozbe API, this module sends the request with the connection you already created, so there is nothing new to authorize. Look up in the Nozbe API documentation which request does what you need, then test the call with Run once before switching the scenario on.
05Make or n8n for Nozbe?
It depends on your criteria rather than on the app. On Make, Nozbe comes with 12 ready-made modules, a scheduled trigger for new tasks and Make an API Call for the rest, and it runs on the Free plan. If you already use n8n, check whether a Nozbe node covers the actions you need there before switching. The deciding points are usually which tool your team already knows and which one the rest of your automations live in.
Same platform

Other docs you might need on this stack.

Browse all integrations