Nozbe Zapier integrationAutomate Nozbe with Zapier.
The Nozbe Zapier integration gives you 2 triggers, 5 actions and 2 searches. Enough to push work into Nozbe from your other tools and to hear about task changes elsewhere. Here is what each one does, what it costs and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the Nozbe Zapier integration does for you
It connects Nozbe, where you and your team keep tasks and projects, to the rest of your apps. You build a Zap (the automation you set up on Zapier: one trigger, then one or more actions that run each time that event happens), and Nozbe can sit at either end.
Three results teams usually want. Requests that land as tasks: an email or a form entry becomes a Nozbe task through Create Task, so nothing lives only in an inbox. Context attached where the work happens: Create Comment and Create Attachment add a note or a file link to an existing task, often found first with Find Task by Name. Changes that travel: New Task and Updated Task tell another app when work appears or moves.
What Zapier does not do here: there is simply no action to delete a task, close a project or move one, and no trigger for comments or new projects. Both triggers are polling triggers, so nothing reaches the next app instantly: on the free plan, Zapier checks every 15 minutes. And the moment you chain a search and an action, you are on a multi-step Zap, which the free plan does not allow.
If you are still choosing a platform, Make vs Zapier and n8n vs Zapier lay out the criteria without picking a winner for you.
Zapier vocabulary in one minute
Eight words you will meet in the editor. Each one comes back further down this page.
- Zap
- Your automation on Zapier. One trigger starts it, then one or more actions run every time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, here often in Nozbe.
- Task
- What Zapier bills. One Zapier task is one action that completed successfully, not to be mixed up with a Nozbe task.
- Polling vs instant
- Polling: Zapier checks the app on a timer. Instant: the app tells Zapier right away. Both Nozbe triggers poll.
- Filter
- A step that lets the Zap continue only when the incoming item meets your condition. Otherwise the run stops there.
- Search step
- A step that looks up something already in an app, so the next steps can use what it found, like an existing task.
- Multi-step Zap
- Anything beyond one trigger plus one action. A filter, a search or a second action makes one, and it needs a paid plan.
What it really costs you
Nozbe is not a premium app, so it runs on the free plan. Its two triggers never cost a task, however often Zapier checks for new or updated tasks.
- Trigger checksFree, always
- Free plan100 tasks a month
- Free plan Zap sizeTwo steps
- Premium appNo
You pay for actions. Each action that succeeds counts as one task, and one that fails counts for nothing. The free plan gives you 100 tasks a month and Zaps of two steps: one trigger, one action. Put a search before Create Comment, or add a filter, and the Zap turns multi-step, which needs a paid plan. A Zap with a search and an action that both run bills you for the action, and only when it goes through.
Connect your Nozbe account
- 01
Open your Apps page
In Zapier, go to Apps and click + Add connection. You need a Nozbe account first, plus access to any team project you do not own but want a Zap to read or write.
- 02
Pick Nozbe
Type the app name in the dialog, select Nozbe from the results, then click Add connection. A new browser tab opens on the Nozbe side for the sign-in.
- 03
Sign in and allow access
Log in to Nozbe in that tab and grant Zapier access to the account. The connection now appears in your list, and every Zap that uses Nozbe can reuse it.
Your first Zap: announce each new Nozbe task and log it on the task
GoalEvery new Nozbe task is posted in a team channel, then a comment on the task records that it was shared.
- 01
Create the Zap
Start a new Zap, choose Nozbe as the trigger app and New Task as the event. Then pick the Nozbe connection you set up above.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent tasks from your account, so you map the next steps on a real task instead of an empty sample.
- 03
Add the Slack message
Add Slack and map the task name into the message text. Pick the channel where your team looks for new work, so each task lands in front of the people who can take it.
- 04
Add Create Comment
Add Nozbe with Create Comment. Map the task from the trigger into Task and write a short Body such as a note that the task went to the channel. Two actions make this a multi-step Zap, so it needs a paid plan.
- 05
Test, then publish
Test each action once and check the comment in Nozbe. When it looks right, click Publish to switch the Zap on for the next new task.
The 2 Nozbe triggers
2 events start a Zap when something happens in Nozbe. Zapier checks for them at the interval your plan allows.
New Task
Polling triggerIn Zapier“Triggers when a new task is created.”
Starts the Zap whenever a task is created in Nozbe, whoever added it. It is the trigger Zapier puts forward for this app, and the simplest way to let another tool know that work has just landed.
Updated Task
Polling triggerIn Zapier“Triggers when a task is updated.”
Reacts when an existing task changes, rather than when it appears. Use it to mirror progress somewhere outside Nozbe, a client tracker or a reporting sheet, without retyping anything by hand.
The 5 Nozbe actions
Nozbe gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Attachment
ActionIn Zapier“Creates a new Attachment”
Hangs a file on an existing task. Two required fields: the Task, and the URL pointing to the file. Zapier lists it among the featured actions for Nozbe.
Create Comment
ActionIn Zapier“Creates a new Comment”
Writes a comment on a task that already exists. It needs the Task and the Body of the comment, both required.
Create Project
ActionIn Zapier“Creates a new Project”
Opens a fresh project in Nozbe. You give it a Name and say whether it is an open project, both required, and can mark it as a favorite.
Create Task
ActionIn Zapier“Creates a new Task or imports many from CSV file”
Adds a new task to Nozbe from whatever started the Zap: an email, a form, a CRM deal. Only Name is required, and an option drops the task straight into Incoming for sorting later.
Update Task
ActionIn Zapier“Updates the Task”
Changes a task that is already in Nozbe instead of creating a duplicate. Pair it with a search step to find the right task first.
The 2 Nozbe searches
2 search steps look for data that already exists in Nozbe, so a later step can use it.
A search step finds a task that already exists and hands it to the next steps. In the editor, Nozbe's searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not the one you expected.
Find Task by ID
SearchFind or createIn Zapier“Finds a task based on id.”
Looks up one task from its ID, the exact identifier Nozbe gives it. Reliable when an earlier step, or another app, already stored that ID.
Find Task by Name
SearchFind or createIn Zapier“Finds a task based on name.”
Finds a task from its name, which is what you usually have when the request comes from an email or a form.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there. Switched on, the Zap carries on without a task.
- Create X if it doesn't exist yet?Ticking this turns the search into a find-or-create: no task found, Zapier creates one with the fields you fill in.
- If multiple search results are found?Three ways out: keep the first match, which is the default, stop the Zap, or hand all matches on at once.
When it breaks
Zapier links no help article to Nozbe, so the traps below are the general ones, applied to how this app works.
Most of them leave no error message: the Zap goes quiet, or runs far more than planned. If something still looks wrong after these checks, the Zapier troubleshooting guide covers the next steps.
Updated Task plus Update Task loops
A Zap that edits the tasks its own trigger watches sets itself off again and again, and burns through your monthly task count fast.Old tasks are never picked up
A Zap only reacts to what happens after you switch it on. Tasks that already existed stay out of reach; moving that backlog is a separate job.A bulk import gets held back
Import a big batch of tasks, from a CSV for example, and the trigger suddenly returns a lot of items. Zapier's flood protection can hold them back.The same task never fires twice as new
Zapier remembers what it already saw on a polling trigger, so a task already picked up by New Task will not start that Zap again.
Need help automating Nozbe with Zapier?
A person reads every message.



