Read your Motion workspace, then create tasks and projects as approved steps.
Connect Motion and Luumen can read your workspaces, projects, tasks, statuses, and schedules without stopping to ask. When the work needs a change — a new task on the migration project, a recurring check-in, a comment for the on-call handover — Luumen shows the plan first and waits for your approval before it writes.
27 tools: 12 read, 15 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Motion 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 add custom field to project, add custom field to task, create comment, create custom field, 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 Motion — 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.