CheckFlow
for LuumenAI
Read CheckFlow runbooks, tasks, and teams, and tag work with approval
Connect CheckFlow and the agent can see how your repeatable work is actually running. It reads templates and their task keys, pulls full checklist instances with controls and comments, checks who is on which team, and reports activity over a date range. Tag creation is a write, so it comes to you as a previewed step first.
The CheckFlow toolbox
10 tools: 9 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadFind ChecklistsFind checklist summaries for a template, optionally filtered by name, tag, or lifecycle status.
- ReadGet AnalyticsReturn checklist and task activity analytics for a date range.
- ReadGet Task DetailsGet one checklist task with its controls, comments, and assignees.
- ReadGet Team DirectoryReturn active team members and groups, including each group's membership, optionally filtered by name.
- ReadList Checklist DetailsReturn one page of full checklist instances, including tasks and controls, with a cursor for the next page.
- ReadList TagsList the tags available to the connected CheckFlow team.
- ReadList TemplatesList active checklist templates and their keys for creating or finding checklists.
- ReadList Template TasksList the task keys and names defined by one checklist template.
- ReadList Webhook SubscriptionsList webhook subscriptions, optionally filtered by source and event type.
- WriteCreate TagCreate a team tag by name, or return the existing same-name tag without creating a duplicate. Approval by default
One prompt, start to finish
What a governed CheckFlow run looks like inside Luumen.
Questions
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. 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 CheckFlow — 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.
Put CheckFlow to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.