Apollo.io
Search Apollo.io's people and company database, enrich leads and manage contacts and sequences.
Connect it with: API key. Apollo.io's own documentation: https://docs.apollo.io/reference/authentication.
What agents can do
Connect Apollo.io so the agents working your tasks can reach it. With it connected, they can:
- Search Apollo's database for people by title, seniority, company or location, and for companies by industry or size.
- Enrich a person or company from an email address or domain.
- Create and update contacts and accounts in your Apollo workspace.
- Add contacts to sequences and read sequence and email activity.
Before you start
- An Apollo.io account on a plan that includes API access, and permission to create API keys (admins by default).
- Enough Apollo credits for enrichment: each enrichment that returns an email or phone number spends credits.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Apollo.io
Jaah connects to Apollo.io with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- API key: In Apollo, open Settings > Integrations > API Keys, select Create new key, name it Jaah, tick the endpoints agents need or turn on Set as master key, select Create API key and copy the key.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Apollo.io card.
- Name the secret and choose who can use it.
- Fill in API key.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Apollo.io with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah calls Apollo.io's API once (GET https://api.apollo.io/api/v1/auth/health) with the stored values, and shows whether Apollo.io accepted it, or which value Apollo.io refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: api_key.
Tell the agent in your task description which secret to use, for example “use the Apollo.io secret org/apollo”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Apollo.io once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Apollo.io's side too, revoke or delete the key at Apollo.io.
Limitations
- A key works only on the endpoints ticked when it was created; a master key reaches every endpoint, including user lists and sequence management.
- People search, enrichment and phone reveals spend your Apollo credits like they do in the app.
- Apollo rate-limits each key per minute, hour and day according to your plan.
- Agents can do only what the connected Apollo.io account allows.
Troubleshooting
Test says Apollo.io rejected the API key (401) or did not accept it
The key was deleted or mistyped. Create a new key under Settings > Integrations > API Keys and select Replace on the secret.
Test passes but an agent gets 403 on a call
The key was not created with that endpoint ticked. Create a new key with the endpoint ticked (or as a master key) and replace the secret.
An agent gets 422 'insufficient credits'
Your workspace has used its credits for the billing period. Add credits in Apollo under Settings > Plans & Billing.
Still stuck? Select Test and read the result: it names the value Apollo.io refused and the status it answered.
FAQ
Does Test spend credits?
No. Test calls Apollo's auth health check, which reads nothing and spends no credits.
Should I use a master key?
Only if agents need user lists or sequence management. A key limited to the endpoints you use is safer.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Apollo.io account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.