Nozbe

Nozbe, formerly Nozbe Teams, is the team task and project manager. Agents create projects and sections, add tasks with comments, attachments, reminders, and recurrences, manage tags and project access, and poll for new or changed tasks.

Verified 2 triggers 78 actions API key available

Nozbe website Platform Documentation Capability data verified 2026-08-24

On New Task fires for each task created in Nozbe since the last poll

Get Task reads who it is assigned to, when it is due and what was estimated against it

List Project Accesses confirms the responsible person can actually open the project

List Tags and List Tag Assignments read the contexts already on the task

Assign Tag To Task applies the routing label the rest of the process keys on

Create Comment posts the source context onto the task, pinned so it stays at the top

The project manager confirms the assignment when the task arrived with no responsible person

What This Integration Enables

Nozbe is a team task manager built around a small number of ideas that it applies consistently: a team holds projects, a project holds sections and tasks, tags cut across all of it, and access to a project is an explicit record rather than an assumption. The connector covers that model in full, from teams and businesses down to individual reminders and comment attachments. FlowRunner agents create projects from templates, file tasks into sections, grant and revoke project access, attach files fetched from anywhere, manage tags and recurrences, and read the task event log that records assignments, completions and due date changes.

Two design choices in this API shape how flows should be built against it, and both are worth naming rather than discovering. Project access is a separate record from team membership, so an agent assigning work has to check that the person can open the project rather than assuming a teammate can see everything. And a task's completion is a timestamp rather than a flag, which means Complete Task is reversible in a way Delete Task is not. The pattern that follows is the one FlowRunner's human-in-the-loop design assumes throughout: agents take the reversible path by default, and the operations that leave no record behind wait for somebody to say yes.

Without FlowRunner

Tasks arrive from everywhere and stay unowned Work created by an integration lands in an inbox with no responsible person and waits to be noticed

Access assumed, not checked Somebody is assigned a task in a project they have no access record for, so they never see it

Bulk loading is a one-way door A CSV import goes in, and unpicking it means deleting records one at a time

With FlowRunner

Ownership resolved at creation The agent reads the roster, checks project access, and either assigns or asks

Access verified before assignment The access list is read first, so a task is never routed to somebody who cannot open it

Bulk loading gets a review step The whole set is assembled and shown before a single call writes all of it

Use Case Scenarios

A repeatable engagement that sets itself up

A signed agreement lands, recorded in HubSpot or signed through DocuSign. The agent calls Get Team to check the seat and plan limits before it starts creating anything, then Create Project From Template to copy the standard delivery structure with its sections and tasks intact. Grant Project Access adds the delivery team, using the member identifiers from List Team Members rather than the user identifiers that appear on tasks. Create Task adds the client-specific items the template does not know about, Create Task Recurrence attaches the weekly status pattern, and Create Comment pins the scope summary to the top of the kickoff task where everyone will see it.
A status digest built from the event log, not from opinions

On a schedule, the agent reads List Task Events for the active projects, which is Nozbe's own audit trail of assignments, completions and due date changes. It groups the movement by project, resolves the people involved through List Users, and posts a digest to Slack with the slipped due dates called out separately from the completions. A copy appends to a sheet in Google Sheets so the trend survives the channel scrollback. Nothing in Nozbe is written by this flow, which is what makes it safe to run every morning without a review step.
Attachments that reach the task instead of the inbox

A supplier emails a document. The flow picks it up through Gmail, and the agent calls Upload Attachment, which fetches the file from its URL and attaches it to a Nozbe comment in one step, creating the attachment record and uploading the bytes together. Get Attachment then confirms the upload finished before a later step reads it. When the document has to move the other way, Download Attachment pulls the bytes into FlowRunner file storage and hands back a URL that an archive step or a client portal can use. The task carries the document; nobody forwards an email.

Human-in-Loop Highlight

Import From CSV creates many tasks or many projects in a single call, which is the operation that deserves the pause on this connector, and the reason is what correcting it costs. Nozbe offers no bulk delete. If an import writes two hundred tasks into the wrong project, or with dates parsed from the wrong column, the route back is Delete Task called once per record, and each of those is permanent, taking the task's comments, reminders and tag assignments with it. So the agent does the whole job up to the write. It parses the file, resolves projects and responsible people through List Projects and List Users, checks that each named person has an access record through List Project Accesses, and then stops with the shape of what it is about to do: "Ready to import 214 tasks into Q4 Onboarding. 12 rows name a responsible person with no access to that project. 3 rows have no due date. Import all, import the clean 199, or hold?" A person answers in one message. The alternative is not a faster import, it is a slower cleanup.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

78 actions

Teams

List Teams Returns the Nozbe teams the API token can reach. A team is the top level container, so this is how a flow discovers the team identifier that Create Project and Create Tag require.
Get Team Returns one team including its plan information, seat limits and credit usage. Worth reading before a flow starts creating projects or inviting members.
Update Team Renames a team, changes its avatar color or moves it in the sidebar. Only the fields supplied are changed.

Projects

List Projects Returns projects the token can reach, optionally narrowed to one team. The Filters parameter selects on any project field, so active projects only is a single expression rather than a post-filter.
Get Project Returns one project with its team, color, open or closed state and preferences. The read before deciding whether a flow should reopen or archive it.
Create Project Creates a project inside a team. Name and team are the only required inputs, and a new project is open unless you say otherwise.
Update Project Changes fields on an existing project. Only what is supplied is written, so closing a finished project is a single flag rather than a full record write.
Delete Project Permanently deletes a project and everything inside it, including its tasks, sections and comments. There is no undo through the API, so close the project with Update Project instead when the records should be kept.
Create Project From Template Creates a new project by copying a template project, including its sections and task structure. The source project has to be marked as a template first.

Project Sections

List Project Sections Returns the sections of a project, which are the named groups tasks are filed under. Each carries an archive timestamp, so an active section is distinguishable from an archived one.
Get Project Section Returns one project section with its project, position and archive state.
Create Project Section Adds a named section to a project so tasks can be grouped inside it. Give a position to control where it lands.
Update Project Section Renames a section, moves it within its project or archives it. Archiving hides the grouping without deleting the tasks inside.
Delete Project Section Permanently deletes a project section. Archiving through Update Project Section is the alternative when the grouping should stay in history.

Project Access

List Project Accesses Returns the access records that say which team members can see a project and which of them manage it. A member with no access record cannot open the project, which is why an agent reads this before assigning work.
Get Project Access Returns one project access record, showing which member it grants and whether they manage the project.
Grant Project Access Gives a team member access to a project, optionally as a manager. The member identifier comes from List Team Members, not from the user identifier that appears on tasks.
Update Project Access Promotes or demotes an existing access record, which is how a participant becomes a project manager or stops being one.
Revoke Project Access Removes a member's access to a project. They keep their team membership and any tasks already assigned to them, so revoking access does not tidy up the work.

Tasks

List Tasks Returns tasks the token can reach, optionally narrowed to one project. Filters select on any task field, which is how one person's open work is fetched in a single call.
Get Task Returns one task including its assignee, due date, estimated and spent time, and whether it has been completed.
Create Task Creates a task and returns the stored record. Only a name is required, and a task with no project lands in the caller's own inbox. Dates accept an ISO 8601 string and are converted.
Update Task Changes fields on an existing task. Only what is supplied is written, and setting the end timestamp marks the task complete.
Complete Task Marks a task done by stamping its completion time, which is what Nozbe treats as finished. The reversible way to close work, unlike Delete Task.
Delete Task Permanently deletes a task along with its comments, reminders and tag assignments. Complete Task is the alternative when the record should stay in history.

Task Activity

List Task Events Returns the activity log entries for tasks: assignments, completions, due date changes and the rest of the audit trail. This is the read behind any status reporting flow that should not rely on opinion.
Get Task Event Returns one task activity log entry by its identifier.

Recurrences

List Task Recurrences Returns the recurrence rules that regenerate tasks on a schedule, each with its pattern and the task currently representing it.
Get Task Recurrence Returns one recurrence rule with its pattern and the task it drives.
Create Task Recurrence Attaches a repeating schedule to a task so Nozbe regenerates it. The pattern follows the iCalendar recurrence shape.
Update Task Recurrence Changes a recurrence rule's pattern or the task it drives. Only what is supplied is written.
Delete Task Recurrence Removes a recurrence rule so its task stops regenerating. The task that currently exists is left in place.

Reminders

List Reminders Returns task reminders. A reminder is either absolute or relative to the task's due date, so read the relative flag before interpreting the time.
Get Reminder Returns one reminder with the task it belongs to and whether its time is absolute or relative.
Create Reminder Adds a reminder to a task. With relative off the time is an absolute moment, and with relative on it is an offset before the task's due date.
Delete Reminder Deletes a reminder. Nozbe publishes no update route for reminders, so changing one means deleting it and creating a replacement.

Comments

List Comments Returns comments, optionally narrowed to one task. Filters will read only the pinned ones, which is how a flow finds the summary somebody put at the top.
Get Comment Returns one comment including its body, author, edit time and reaction payload.
Create Comment Posts a comment on a task. Turn the team flag on to make it a team wide note rather than a comment only the task's participants see.
Update Comment Edits a comment's text or its pinned state. Nozbe records an edit timestamp, so an edited comment is visibly different from the original.
Delete Comment Permanently deletes a comment and its attachments. Marking it deleted through Update Comment is the softer alternative, which keeps the record in the task's history.

Attachments

List Comment Attachments Returns the files attached to a comment, each with its name, type, size and upload status.
Get Attachment Returns one attachment's metadata. Used to confirm an upload finished before a later step reads the file.
Upload Attachment Downloads a file from a URL and attaches it to a Nozbe comment in one step, creating the attachment record and uploading the bytes together.
Download Attachment Downloads an attachment's bytes into FlowRunner file storage and returns a URL later steps can use.
Delete Attachment Permanently removes an attachment from a comment. The comment text itself is left in place.

Tag Assignments

List Tag Assignments Returns the join records that attach tags to tasks. Filter by task to read a task's tags, or by tag to find every task carrying a label.
Get Tag Assignment Returns one tag assignment record, naming the tag and the task it joins.
Assign Tag To Task Attaches an existing tag to a task. The tag has to already exist in the task's team.
Unassign Tag From Task Removes a tag from a task. The tag itself is untouched and stays available to other tasks.

Project Groups

List Project Groups Returns project groups, which are the sidebar folders that gather projects or members together.
Get Project Group Returns one project group with its team and privacy setting.
Create Project Group Creates a sidebar folder inside a team that projects or members can be filed into. The privacy flag defaults to off here, which makes the group visible to the whole team.
Update Project Group Renames a project group or changes whether it is private.
Delete Project Group Deletes a sidebar group. The projects and members filed into it are not deleted, they simply stop being grouped.

Group Assignments

List Group Assignments Returns the join records that file projects or members into a sidebar group.
Get Group Assignment Returns one group assignment record by its identifier.
Add To Project Group Files a project or a team member into a sidebar group. The group type has to match what the object identifier refers to, because one route serves both.
Remove From Project Group Removes a project or member from a sidebar group. Neither the group nor the project is deleted.

Team Members

List Team Members Returns team membership records, each joining a user to a team with a role and a status. The member identifier here is what Grant Project Access wants.
Get Team Member Returns one team membership record with its role, status, alias and vacation ranges.
Add Team Member Adds a user to a team with a role and a status. Pair it with Create User to bring in somebody who has no Nozbe account yet.
Update Team Member Changes a member's role, status, alias or color. Setting the status to archived deactivates them while keeping their history.
Remove Team Member Deletes a team membership, which removes the person from the team and frees their seat. Archiving through Update Team Member is the reversible alternative.

Users

List Users Returns the user accounts the token can see, including placeholder users created for people who have not signed up yet.
Get User Returns one user account with their display name, time zone and whether the record is a placeholder awaiting sign up.
Create User Creates a placeholder user so work can be assigned to somebody before they accept an invitation. The placeholder becomes a real account when they sign up.
Update User Changes a user's display name, avatar color or time zone. Only what is supplied is written.

Businesses

List Businesses Returns the businesses the token can reach. A business is the layer above teams, used to group several teams under one organization.
Get Business Returns one business by its identifier.
List Business Members Returns the membership records that join users to a business, each with an organization level role and any vacation ranges.
Get Business Member Returns one business membership record with its role and vacation ranges.
Update Business Member Changes a business member's organization level role, or records their vacation ranges.

Bulk Import

Import From CSV Creates many tasks or many projects in one call from CSV text and returns the created records. The record type decides which field the file is posted under, and Nozbe rejects a mismatch rather than reinterpreting it. This is the operation this page's human gate exists for.

Triggers

2 triggers

Event Triggers

On New Task Fires for each task created since this trigger last polled Nozbe, with a configurable polling interval. Nozbe tracks the read position on its own server, keyed to the API token, and reading advances it. Two flows polling with the same token consume each other's events, so give each trigger its own token.
On Updated Task Fires for each task changed since the last poll, including completions, reassignments and due date changes. It reads a different endpoint from On New Task, so the two do not compete with each other, but the same one-cursor-per-token rule applies to any other flow sharing that token. The first poll after enabling a trigger can return a backlog rather than an empty list, because the cursor starts wherever that token last left it.

Frequently Asked Questions

What can FlowRunner do with Nozbe?

FlowRunner agents can run List Teams, Get Team, and Update Team in Nozbe, plus 75 more actions.

Does connecting Nozbe to FlowRunner require OAuth?

No. Nozbe connects to FlowRunner with an API key, no OAuth flow required.

Can Nozbe trigger a FlowRunner workflow automatically?

Yes. Nozbe supports 2 triggers that can start a FlowRunner workflow automatically.

Start building with Nozbe

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us