> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # Apollo.io > Read Apollo.io companies, people, saved contacts and sequence status in Hebno, and add contacts to a list after you confirm. 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 | | | | - | - | | **Connection** | Personal connection. Each member connects with their own Apollo.io API key. | | **Default access** | Read and write | | **Attach** | Companies, people, saved contacts, lists | | **Search** | Hebno searches Apollo when a request mentions a target company, a job title, a buyer, a prospect list or a sequence | | **Link** | A project links to an Apollo account | | **Write** | Add a contact to a list. Every write needs a person to confirm. | ## 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: | Apollo API endpoint | Why Hebno needs it | | - | - | | **People Search** and **People Enrichment** | Find people by company, title, seniority or location, and read their profile | | **Organization Search** and **Organization Enrichment** | Find companies and read firmographic details | | **Search for Contacts** and **Search for Accounts** | Read the contacts and accounts your team has saved | | **Search for Sequences** | Read sequence names, status and which saved contacts are enrolled | | **Create a Contact** and **Update a Contact** | Save a person as a contact and add them to a list after you confirm | | **Get a List of Users** | Show contact and account owners by name | ## 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 | Apollo object | Fields Hebno uses | Typical questions | | - | - | - | | **Organisation** | Name, website, industry, employee count, estimated revenue, headquarters, technologies, departmental headcount | "How big is Contoso Retail's finance function?" | | **Person** | Name, title, seniority, department, company, location, LinkedIn URL, employment history | "Who are the pricing leaders at Contoso Retail?" | | **Contact** | A person your team saved, with owner, stage, lists and last activity | "Which Contoso contacts have we already saved?" | | **Account** | A company your team saved, with owner, stage and contacts | "Who owns the Contoso account in Apollo?" | | **List** | List name and the contacts or accounts on it | "Who is on the UK retail CFOs list?" | | **Sequence** | Name, active flag, number of steps, enrolled contacts and their status | "Is anyone at Contoso in an active sequence?" | 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. > [!WARNING] > > 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**. | Action | Apollo object | Fields on the card | | - | - | - | | **Add a contact to a list** | Contact | Person, list, contact owner, contact stage. If the person is not saved, Hebno creates the contact first. | ![Confirmation card for Apollo.io with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-apollo.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=1b26daca5cae8d129252a1410475bd3d) 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. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Apollo You->>Hebno: Add Contoso's head of pricing to the UK retail CFOs list Hebno->>Apollo: Search people at Contoso Retail with title pricing Apollo-->>Hebno: Person, Head of Pricing, not saved Hebno-->>You: Confirmation card with person, list, owner You->>Hebno: Confirm Hebno->>Apollo: Create the contact with the list as you Apollo-->>Hebno: Contact created Hebno-->>You: Done, with a link to the contact ``` ## Link a project to an account 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](https://hebno.com/docs/projects/linked-records.md). ## 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](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | **Connect** fails with **401 Unauthorized** | The key is wrong or was deleted in Apollo. Create a new key and connect again. | | A request fails with **403** and a message about the API key | The key does not include that endpoint. Edit the key in Apollo to add it, or turn on **Set as master key**. | | Contacts appear without email or phone | Hebno did not reveal them. Ask for the contact details by name, and check your Apollo account has reveals remaining. | | A list is missing from the card | The list belongs to another user and is not shared with you in Apollo. | | A write fails with **422** | A field on the card does not match Apollo, often a contact stage. Pick a valid value and select **Confirm** again. | | Requests fail with **429 Too Many Requests** | Apollo limits requests per minute, hour and day for each key. Wait and retry. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Linked records](https://hebno.com/docs/projects/linked-records.md) * [ZoomInfo](https://hebno.com/docs/integrations/zoominfo.md) * [LinkedIn Sales Navigator](https://hebno.com/docs/integrations/linkedin-sales-navigator.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.