Ask Claude or ChatGPT to search Clay for the companies and people you want, check what your workspace already holds, and enrich records when you allow it.
Read from Clay when someone asks. Nothing exported, nothing copied, and changes only where you allow them.
Clay CRM & sales 
FrontierOps Permissions, definitions, record 
Any AI The AI your team uses Find heads of growth at B2B software companies in the UK with 50 to 200 employees.
What do we already have in Clay on Acme, and who are our contacts there?
Enrich these ten contacts with Clay and add what it finds to their records.
Both are off until an admin turns them on for the connector, on top of role access: they spend Clay credits, and a subroutine can update a CRM or send messages. Every write is on record.
Clay is where your team builds lists and enriches them, usually one table at a time. Connected once, anyone can describe the accounts or people they want, see what you already have on them and ask a question across your accounts, while the steps that spend the most credits stay off until you turn them on.
An admin connects Clay one time. Nobody hands over a personal login.
Each answer is read at the moment of the question. Nothing is exported or copied, so there is nothing to keep in sync.
What each role can see and do holds in every AI your team uses, and in your own agents.
Every question and every action, by every person and agent, in one audit trail.
Searches and account questions can, because Clay charges for them. Reading your own people, companies and deals in Audiences is the cheaper path. Enrichment spends the most and stays off until an admin turns it on, whatever the AI is asked.
Only if an admin turns subroutines on. A subroutine runs the logic you built in Clay, which can write to a CRM or send messages, so it stays off until you decide, and every run is on record.
An admin signs in to Clay once, with nothing to paste. FrontierOps works through Clay’s own AI connector with that sign-in, so it reaches that user’s Clay workspace, and each person’s role decides which calls they can make.
Yes, and one built for a whole company. FrontierOps gives Claude, ChatGPT and any other MCP client one connection to Clay, set up once by an admin. What each role can read or change is decided in FrontierOps, and every call is on record, instead of each person running their own server with their own login.
A direct connection links one AI to Clay through one person’s login, with that person’s settings. That works for one person. For a team it means no shared definitions, no single place to decide who can see or change what, and starting over when you switch AI. Through FrontierOps, Clay is connected once, for every AI and every agent, under one set of permissions, with every call on record.
HubSpot Ask Claude or ChatGPT about your contacts, companies and their activity in HubSpot, and have the follow-up logged in the CRM. Connect HubSpot to any AI 
Attio Ask Claude or ChatGPT about the people, companies and deals in Attio, custom objects included, and have the note, task or list update made in the CRM. Connect Attio to any AI 
Instantly Ask Claude or ChatGPT how your Instantly campaigns are doing and who replied, and have leads added, campaigns paused or replies sent when you allow it. Connect Instantly to any AI