Apollo.io Audit in Claude
Ask Claude to audit your Apollo.io workspace and read the findings in the chat. The free GTM Works Apollo.io audit as a Claude connector: read-only, no credits, and your key never enters the chat.
What the Apollo.io audit connector does
It runs the same free Apollo.io audit as the website, from inside Claude. Type "audit my Apollo.io workspace", connect once, and the chat starts the scan, reads the findings and walks you through the fixes.
It checks contacts in two sequences at once, workflows that can put someone in a second sequence, emails that will go out blank or fail, Not sent emails from the last 30 days, mailboxes that cannot send with live sequences behind them, sequences Apollo.io paused, workflows feeding a sequence that is off or stopped by their lifetime limit, deactivated users who still own records, and duplicate accounts, the same free scan as Apollo.io account dedupe.
Apollo.io's own connector searches and works your records from a chat. This one audits them. They do different jobs and you can connect both.
How to add the Apollo.io audit to Claude
Claude (web and desktop)
- Open Settings > Connectors and click Add custom connector.
- Name it GTM Works Apollo.io Audit and paste this URL:
https://app.gtmworks.ai/mcp - Click Connect. A GTM Works page opens: enter your work email and paste an Apollo.io master API key (Settings > Integrations > API in Apollo.io, Create new key, turn on Master API Key).
- Back in the chat, type "Audit my Apollo.io workspace."
Claude Code
Add the server, then type /mcp in Claude Code to connect. The same GTM Works page opens in your browser for the key.
claude mcp add --transport http gtmworks-audit https://app.gtmworks.ai/mcpFirst findings arrive in minutes, up to about 10 on a big workspace. The duplicate scan takes longer and we email you when it is done.
The five tools
Every input is an audit id, a check name or a number. No tool takes free text, and none writes to Apollo.io.
List my Apollo.io audits
list_apollo_audits
The audits this connection can see, newest first, with status, finding count, when each expires and a link to its results page.
Start an Apollo.io audit
start_apollo_audit
Starts the audit on the workspace whose key you pasted when you connected. It reads your workspace and changes nothing in Apollo.io. Run it twice and you get the same scan back, not a second one. Claude asks you before running it.
Get Apollo.io audit findings
get_apollo_audit
Every finished check: what it found, how many records, why it matters and how to fix it, with a link into your own Apollo.io where Apollo.io has the fix. While checks are still running it says which ones are left.
List the records behind one finding
get_audit_finding_rows
The contacts, sequences, workflows, mailboxes or users behind one finding, 25 at a time (up to 100). These are your own records, shown in your own chat because you asked for them.
Check the duplicate account scan
get_duplicate_account_scan
Progress on the duplicate account scan while it runs. When it is done: accounts scanned, companies with duplicates, records to clean up and what created them.
Example prompts
- "Audit my Apollo.io workspace."
- "What is the most serious problem in my Apollo.io audit, and how do I fix it?"
- "Show me the contacts who are in two sequences at once."
- "Which deactivated users still own contacts or accounts in my Apollo.io?"
- "Why did Apollo.io not send emails last month? Group them by what I need to fix."
- "How far along is my duplicate account scan?"
How your Apollo.io key is handled
- Pasted on app.gtmworks.ai, never in the chat. The connect screen is our page. Claude never sees the key.
- Stored encrypted, used only for your audit and any fix you buy.
- Deleted after 7 days, or 30 if you buy a fix. You can delete it in Apollo.io any time.
- Never logged. Connection tokens are stored hashed, expire after an hour and renew for up to 30 days.
- Results only to you and into the chat you asked from. Nothing is pooled or compared across customers.
The audit is free. Two fixes are paid.
- Free: the audit, the duplicate scan and a CSV of every finding on the results page.
- Duplicate cleanup: merges the duplicates you tick. $299 for up to 1,000 accounts, $499 up to 5,000. How Apollo.io account dedupe works.
- Rep handoff: moves a departed rep's sequences, contacts, accounts and tasks to someone still on the team. $99 per rep.
- Paid on the results page on gtmworks.ai. The chat shows what each fix costs next to the finding it fixes. It never takes payment.
How to disconnect
- In Claude: Settings > Connectors, open GTM Works Apollo.io Audit and click Disconnect or Remove.
- On app.gtmworks.ai: open your scans and click Disconnect next to the app under Connected AI apps. Its tokens stop working at once.
- In Apollo.io: delete the API key under Settings > Integrations > API. We delete our copy after 7 days either way.
Troubleshooting
The chat says it needs a key
Keys are deleted 7 days after a scan. The chat gives you a link to app.gtmworks.ai to paste a fresh one. The link works for 30 minutes. Paste the key there, never in the chat.
The key is rejected
The audit needs a master API key. In Apollo.io, open Settings > Integrations > API, click Create new key and turn on Master API Key.
A check says "could not check"
That check hit an error or a permission it does not have. The other checks still run. A master key gives the full audit.
The duplicate scan is still running
It reads every saved account, so it can take hours on a big workspace. We email you when it is done. Ask the chat again later; it checks no more than once a minute.
The audit has expired
Free results are deleted 7 days after the scan. Ask the chat to start a new audit.
It will not start another scan
New scans are limited to 5 per email and 3 per key a day. Ask the chat for your existing audit instead.
You ran an audit on the website first
Sign in on app.gtmworks.ai in the same browser (we email you a link), then connect again from your chat. Your website audits then show in the chat.
Still stuck? Email jeremy@gtmworks.ai.
Apollo.io Audit in Claude: Frequently Asked Questions
How is this different from Apollo.io's own connector?
Apollo.io's own connector searches and works your Apollo.io records from a chat. This one is a free audit by GTM Works that finds what is broken in your workspace. You can use both.
Is the Apollo.io audit in Claude free?
Yes. The audit, the duplicate scan and every finding are free. Two fixes are paid, on the results page on gtmworks.ai: duplicate account cleanup ($299 up to 1,000 accounts, $499 up to 5,000) and handing a departed rep's records to someone still on the team ($99 per rep). Nothing is ever charged in the chat.
What is the connector URL?
https://app.gtmworks.ai/mcp. Add it as a custom connector in Claude, or with claude mcp add in Claude Code.
Can it change anything in my Apollo.io?
No. Every tool reads. Starting an audit queues a read-only scan. Nothing in Apollo.io changes unless you buy a fix on the website and click to run it.
Does it use Apollo.io credits?
No. It reads records already saved in your workspace, which costs no credits. It does use some of your team's hourly API limit, paced so your own tools keep working.
Does it work with Claude Code?
Yes. Run claude mcp add --transport http gtmworks-audit https://app.gtmworks.ai/mcp, then type /mcp to connect.
Do I paste my Apollo.io API key into Claude?
No. You paste it on app.gtmworks.ai when you connect. No tool has a field that takes a key, so it never enters the chat, the model or the connector.
Audit your Apollo.io workspace from Claude
Read-only. Uses no Apollo.io credits. First findings in minutes.
Add the connectorStill exploring?