TrueList
for LuumenAI
Check email lists, run batch validation jobs, and read past results
Connect TrueList and your agent can see the state of every batch validation job, the progress counts behind it, and the results of addresses you have already checked. Estimate a file before you spend credits on it. Start a batch or validate a single address as an approved step, with the plan shown first. Luumen authenticates with an API key.
The TrueList toolbox
8 tools: 5 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadEstimate BatchEstimate email count, duplicates, and processing time for tabular batch data without creating a batch or consuming batch-validation credits.
- ReadGet AccountReturn the connected TrueList user identity, account name, and payment plan without exposing API tokens or other account users.
- ReadGet BatchGet one TrueList batch-validation job by UUID, including progress counts and completed result download URLs.
- ReadList BatchesList all batch-validation jobs in the connected TrueList account, including their current processing state, progress counts, and available result download URLs.
- ReadList Validation HistoryReturn one page of previously validated email results, optionally filtered by batch, address, state, or sub-state.
- WriteCreate BatchCreate an asynchronous TrueList batch email-validation job from tabular rows. Approval by default
- WriteDelete BatchPermanently delete one completed TrueList batch and its validation results. Approval by default
- WriteValidate EmailValidate one email address synchronously, consume validation capacity, and add the result to TrueList validation history. Approval by default
One prompt, start to finish
What a governed TrueList 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.
Read actions answer immediately. Anything that writes — create batch, delete batch, validate email — 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 TrueList — 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.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut TrueList to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.