Clay
for LuumenAI
Clay is a go-to-market data enrichment and workflow automation platform for searching people and companies, running routines, and querying workspace tables.
Operate Clay from the same conversation as the hosts it runs on. Check jobs, queues, and interfaces without a second console; run diagnostic reports; and restart or update with the change previewed, approved, and logged.
The Clay toolbox
6 tools: 3 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Current UserReturn the Clay user and workspace associated with the connected Public API key.
- ReadGet Routine Run ResultsCheck progress or fetch one page of results for an existing inline Clay routine run.
- ReadGet Search Query ReferenceReturn Clay's current advanced-search field and grammar reference for composing people or company queries.
- WriteContinue SearchConsume one next page from an existing Clay query-mode search. Approval by default
- WriteRun RoutineStart a Clay routine for 1-100 items, poll it for a bounded time, and return completed item results or the current run ID and progress. Approval by default
- WriteSearch People or CompaniesCreate a Clay query-mode people or company search and consume its first result page. Approval by default
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 — continue search, run routine, search people or companies — 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 Clay — 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
SAP BTPGateways, jobs, and subaccounts operated from one governed chat.
SalesforceRecords and integration jobs checked without a second console.
SAP S/4HANAJobs, queues, and records in SAP S/4HANA without a second console.
SAP SuccessFactorsJobs, queues, and records in SAP SuccessFactors without a second console.Put Clay to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.