Read Teamwork projects, tasks, and time. Create and update work as approved steps.
Connect Teamwork and the agent can see the same board your team works from: projects, task lists, tasks, milestones, people, tags, and logged time. Ask who owns the migration work or what is overdue this week, and the answer comes back from live data. Creating a task, updating one, or logging time is proposed first and waits for your approval.
12 tools: 8 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Teamwork 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 tag, create task, log time entry, update task. 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 Teamwork — 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.