Look up contacts and company data in Hunter, then add leads as approved steps
Connect Hunter and your agent can search a domain for published email addresses, verify deliverability, and pull company details without leaving the terminal. When you want a contact saved, the agent drafts the lead record and shows it to you first. Changes to leads, lists, and custom attributes run as approved steps by default.
26 tools: 16 read, 10 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Hunter 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 — create custom lead attribute, create lead, create leads list, delete custom attribute, and more — is shown as a plan and requires approval by default, including the 3 actions 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 Hunter — 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.