Read LeadBoxer leads and sessions, then tag them as an approved step
Connect LeadBoxer with an API key and your agent can look up a lead, walk its sessions, and read the events behind a score without opening the dashboard. When something needs to change — a tag applied, a server-side event logged — the agent shows the call first and waits for your approval by default.
9 tools: 5 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed LeadBoxer 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.
Read actions answer immediately. Anything that writes — add or update lead tags, delete custom tracking domain, log server-side event, post event data — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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 LeadBoxer — 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.