Read Nozbe Teams projects and tasks, then file follow-up work with approval.
Connect Nozbe Teams and Luumen can read your projects, sections, tasks, comments, tags, and team members whenever it needs context. Ask who owns a piece of work, what a task's history looks like, or which section a project uses. When follow-up work needs to exist in Nozbe, Luumen drafts the task or comment and shows it to you before anything is written. Authentication is by API key.
48 tools: 28 read, 20 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Nozbe Teams run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create attachment, create comment, create project section, create reminder, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Nozbe Teams — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.