Skip to main content
The Apollo.io integration brings company and people data into account research. Ask who leads finance at a prospect, which of your saved contacts at Contoso Retail are already in a sequence, or how large a company’s commercial team is, and Hebno answers from Apollo with each record cited. When a request implies a change, such as adding a person to a prospect list, Hebno shows a confirmation card and writes to Apollo only after you confirm.

​
At a glance

​
Before you start

You need:
  • An Apollo.io user in your team’s Apollo account.
  • Permission to create API keys. Apollo admins control this, so ask an admin if the option is missing.
  • An allowed integration. An owner or admin sets Apollo.io to Allow under Admin → Connectors → Catalogue.
An Apollo API key has the access of the user who created it and can be limited to chosen endpoints. Create a key with these endpoints turned on, or turn on Set as master key to include all of them:

​
Connect Apollo.io

1

Create an API key in Apollo

In Apollo, open Settings → Integrations, find API and select Connect. Under API keys, select Create new key, give it a name such as Hebno, choose the endpoints above and select Create API key. Copy the key.
2

Add the key in Hebno

Open Settings → Connections, find Apollo.io under Company and market data and select Connect. Paste the key and select Connect.
3

Check the connection

The card shows Connected with your Apollo user and team name.
Hebno reads and writes as you, so contacts you add appear with you as the owner. The key is encrypted at rest. Select Disconnect at any time, or ask an admin to revoke the connection under Admin → Connectors → Connections. Deleting the key in Apollo also ends the connection.

​
What Hebno reads

Reads are live. Hebno queries Apollo when a request needs it. Only what a reply used is stored with the conversation as its sources. Hebno does not reveal email addresses or phone numbers from Apollo’s database unless a request asks for them, because Apollo counts each reveal against your account’s limits.
Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including names, titles and contact details from Apollo.

​
What Hebno writes

Every write appears first as a confirmation card. You can change any field before you select Confirm.
Confirmation card for Apollo.io with editable fields

An Apollo.io change pending confirmation. Nothing is written until you confirm.

Hebno never enrols contacts in sequences, sends email, deletes contacts or accounts, or exports data from Apollo. Enrolling a contact in a sequence is a step you take in Apollo. Linking marks which Apollo account belongs to a project, so you can ask “who else should we meet?” without naming the client.
  1. Open the project and select Brain.
  2. Under Linked records, select Link record, then Apollo.io.
  3. Search your saved accounts and select the client. If the company is not saved yet, save it as an account in Apollo first.
In chats tagged to the project, Hebno starts with the linked account for any question about the client’s people, and list cards default to its contacts. See Linked records.

​
Use Apollo.io in chat

  • Attach: open the + menu, choose Sources → Apollo.io, and pick a company, person, contact or list. Or type / and choose Apollo.io.
  • Ask: name the company, title or list in your request. For example:
    List the director-level and above people in pricing, merchandising and finance at Contoso Retail.
    Which of our saved Contoso contacts are in an active sequence, and who owns them?
    Add Priya Nair and Sarah Chen to the Contoso pricing review stakeholders list.
  • Research runs show a Checking Apollo.io step, with a chip for each company, person and list it read.
  • Agents can read Apollo on a schedule, for example a Monday list of new senior hires at linked accounts. Writes an agent proposes appear in agent approvals for review.

​
Troubleshooting