Check BrowserAct runs, then start or resume a workflow as an approved step
Connect BrowserAct with an API key and Luumen can read your workspace directly: which workflows exist, what inputs they expect, which tasks are running, paused, or failed, and what each run produced. When a run needs to be started, resumed, or canceled, that step is previewed and approved first, then recorded.
11 tools: 7 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed BrowserAct 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 cancel task, resume task, run workflow, run workflow template. 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 BrowserAct — 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.