- Two routes catalogued: run a routine and get the results of a run
- Runs a routine from your own Clay workspace, so the returned fields are the ones you designed
- Iris reads job title, LinkedIn URL, e-mail and phone from the result when present and stores the full answer on the contact
- Iris waits about 25 seconds for the routine, then asks you to retry shortly
- Runs on your own Clay API key and routine ID; Apivom Atlas stores nothing
Clay Routines Connector
Clay's Routines API connected to Apivom Iris with your own Clay API key and routine ID: run an enrichment routine from your own Clay workspace for a contact, collect the result, and let Iris fill only the empty fields on the record.
What you can do
Use cases
- Run your own enrichment routine from the CRM — Build the routine in Clay with the providers and logic you choose, then trigger it from a contact in Iris with Enrich via Clay.
- Keep the full routine answer — Iris stores the whole result of the run on the contact, so fields your routine returns beyond the standard ones stay available for your team.
Clay is a data workflow platform where you build enrichment routines in your own workspace. The routes catalogued in Apivom Atlas start a routine run and fetch its results. Apivom Iris starts your routine for a contact, passing the name, e-mail, company and LinkedIn URL it has, then waits about 25 seconds for the result before asking you to retry shortly. Because the routine is yours, the fields that come back are the ones you built it to return: Iris reads job title, LinkedIn URL, e-mail and phone when they are present, fills only empty contact fields and stores the full answer on the contact. The connector uses your Clay API key, sent as the clay-api-key header, and your own routine ID; Apivom Atlas stores nothing.
Authentication
Your own Clay API key (Clay Settings → API & CLI), sent as the clay-api-key header, and the routine ID of a routine in your workspace. The key is stored encrypted in your Apivom Iris tenant; Apivom Atlas stores no credentials.
Frequently asked questions
Which Clay endpoints are covered?
Two: starting a routine run and getting the results of a run. Other Clay endpoints are not catalogued.
Which fields come back?
Whatever your routine returns. Iris sends name, e-mail, company and LinkedIn inputs, reads job title, LinkedIn URL, e-mail and phone from the result when present, and stores the whole answer on the contact.
Does Apivom sell Clay data or charge per lookup?
No. Apivom does not sell or resell Clay data. You connect your own Clay account, and Clay's terms, quotas and pricing apply to every lookup. Apivom adds no per-lookup fee for this connector.
Where are my Clay credentials stored?
In your Apivom Iris tenant, encrypted. Apivom Atlas is a stateless gateway: it forwards each call to the provider and stores no credentials.
Can I use this connector from my own application?
Apivom Iris connects it today, and every route is catalogued in Apivom Atlas. Connecting it to your own applications is scoped per customer: tell us the use case and we plan it with you.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.