LeadBoxer
for LuumenAI

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.

The LeadBoxer toolbox

9 tools: 5 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet EventsFetch events for specified sessions from LeadBoxer.
  • ReadGet Lead Score FormulaFetch the lead score formula for a specific dataset.
  • ReadGet SessionsFetch sessions for a specified lead ID from LeadBoxer.
  • ReadGet Custom Tracking DomainsFetch custom tracking domain entries for a dataset.
  • ReadGet Lead DetailFetch detailed information about a lead based on filters.
  • WriteAdd or Update Lead TagsAdd or update lead tags in LeadBoxer. Approval by default
  • WriteDelete Custom Tracking DomainDelete a custom tracking domain entry for a dataset. Approval by default
  • WriteLog Server-Side EventTrack server-side events in LeadBoxer. Approval by default
  • WritePost Event DataSend event data for tracking user activities via POST request. Approval by default

One prompt, start to finish

What a governed LeadBoxer run looks like inside Luumen.

Questions

How does LuumenAI connect to LeadBoxer?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in LeadBoxer on its own?

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.

Who gets access to the integration?

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.

Is there an audit trail?

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.

Put LeadBoxer to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.