Read Timely timesheets for context, then lock or adjust periods with approval
Connect Timely and the agent can read your account the way you would: timesheets, projects, clients, labels, teams, user capacities, permissions, and the activity audit trail. Ask what a person logged last week or which projects carry unbilled hours, and you get an answer. Changes like locking a closed month or renaming a billing label are previewed first, then applied on your approval.
41 tools: 26 read, 15 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Timely run looks like inside Luumen.
Authorize once with OAuth 2.0. 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 client, create day locking, create label, create team, 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 Timely — 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.