Menu

Mattering Automations Apollo.io integration

Connect Apollo.io to Mattering Automations: B2B people and company search, credit-spending enrichment, contacts, accounts, deals, and sequence adds as workflow steps, authenticated with an Apollo API key sent as the x-api-key header.

The Mattering Automations Apollo.io integration adds Apollo to your automation canvas: search the B2B people and company database, enrich people and companies, manage the contacts, accounts, and deals in your team's Apollo workspace, read stages, lists, users, and connected mailboxes, and add contacts to sequences.

Setup takes a few minutes: create an API key in Apollo, attach it as a credential in Mattering, and test the connection against Apollo's own auth health endpoint, which costs zero credits. This guide walks through each step and ends with the full node reference.

Two boundaries are worth knowing before you build. First, credits and personal data: Apollo: Search People Database is free and returns no email addresses or phone numbers; enrichment is where credits are spent, and enrichment output is real people's contact data that lands in execution records, so only enrich people your organization has a lawful basis to process. Second, outreach: Apollo: Add Contacts to Sequence (Sends Real Emails) is the single node that can start real email, and it belongs behind a condition, an approval step, or a manual run.

Before you start

  • An Apollo.io account. The free tier can run the health check, people search, and enrichment within tight rate limits; company search, contact search, deal listing, and sequence search are documented as paid-plan endpoints.
  • Permission to create an API key in that Apollo workspace, ideally a master key: several reads are documented as master key only, and scoped keys must pick their endpoints at creation.
  • A Mattering workspace with access to the Automations app.
  • For sequence flows: a sequence in Apollo and a connected sending mailbox, plus the understanding that adding contacts to an active sequence sends real email.

Create an Apollo API key

Mattering authenticates to Apollo with an API key sent as the x-api-key header on every request; the key never rides in a URL, so it cannot leak into links or logged request paths. Apollo keys come in two grades: regular keys are scoped to the endpoints chosen at creation, and a master key unlocks everything. One nuance worth knowing: an Apollo API key identifies the workspace, not a person, and API actions attribute to the workspace's longest-standing active admin.

In your Apollo workspace settings, open the API section and create a new API key (see docs.apollo.io for the current path).
Choose a master key for full coverage, or select the endpoint scopes your automations will need.
Copy the key.
The connection test uses Apollo's auth health endpoint, which works with any key scope, so an under-scoped key passes the test and then gets 403s on the nodes whose scopes it is missing. Apollo: List Users and Apollo: View API Usage and Rate Limits are documented as master key only. If you plan to use the whole catalog, create a master key now rather than debugging scope errors later.

Connect Apollo.io to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Apollo.io from the list.
Click Create new credential, paste your API key, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs. At request time the key is applied as the x-api-key header, and it is registered for redaction so it cannot surface in execution records.
Click Test Connection: Mattering calls Apollo's auth health endpoint, Apollo's own documented key test, which costs zero credits and works with any key scope.
Click Connect. All 30 Apollo nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: an Apollo section should list the query and action nodes. Drop Apollo: Check API Key Health onto the canvas and run a test step. It takes no parameters, costs zero credits, and works with any key scope; a good key returns the healthy and is_logged_in flags both true, and a bad key gets a 401.

To see real data, run Apollo: Search People Database with a job title filter. It costs zero credits and returns profiles without email addresses or phone numbers, so verifying spends nothing and touches no contact data. Everything in the verify path is free; nothing here consumes credits, and nothing here can reach Apollo: Add Contacts to Sequence (Sends Real Emails), the only node that starts outreach.

Node reference

30 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 20

Apollo: Bulk Enrich Companies (Consumes Credits)

apollo_bulk_enrich_organizations

Enrich UP TO 10 COMPANIES in one call (Apollo's documented maximum for this endpoint). Costs 1 credit per company enriched. Company data, not personal data.

Apollo: Check API Key Health

apollo_check_auth_health

Verify the stored Apollo API key works. Apollo's own documented key test: costs nothing, needs no parameters, works with any key scope. Returns healthy and is_logged_in flags; both true means the connector is ready. A bad key gets a 401.

Apollo: Enrich Company by Domain (1 Credit)

apollo_enrich_organization

Look up one company and return firmographics: industry, headcount, revenue, funding, address, socials. Provide at least one of domain, name, website, or linkedin_url (domain gives the best matches). Costs 1 credit per company. Company data, not personal data.

Apollo: Get Company by ID (1 Credit)

apollo_get_organization

Fetch the complete Apollo profile for a known organization ID: firmographics, funding, technology stack, department headcounts. Costs 1 credit per company. Documented as needing the organizations/show scope or a master key.

Apollo: Get Deal

apollo_get_deal

Fetch complete details for one deal: value, stage, ownership, and the associated account. Costs no credits. Documented as needing the deals show scope or a master key.

Apollo: Get Person by ID (1 Credit)

apollo_get_person

Fetch the full Apollo profile for a known person ID. Costs 1 credit per call. For people not saved as contacts, the email field returns the literal placeholder email_not_unlocked@domain.com even when email_status says verified; use the Enrich Person node to actually reveal an address. Output may contain personal data, which lands in execution records.

Apollo: List Account Stages

apollo_list_account_stages

List every account stage in your workspace with its ID and name. Costs no credits. Documented as needing its scope or a master key. Feeds the stage fields on the account nodes.

Apollo: List Company Job Postings (1 Credit per Page)

apollo_list_job_postings

List a company's currently active job postings, a strong buying-intent signal (who is hiring for what, where). Costs 1 credit per page; display limit 10,000 records.

Apollo: List Contact Stages

apollo_list_contact_stages

List every contact stage in your workspace with its ID, name, and pipeline category. Costs no credits. Documented as needing its scope or a master key. Feeds the stage fields on the contact nodes.

Apollo: List Deal Stages

apollo_list_deal_stages

List every deal stage in your workspace with its ID, name, and win probability. Costs no credits. Documented as needing its scope or a master key. Feeds the stage fields on the deal nodes.

Apollo: List Deals

apollo_list_deals

List every deal (opportunity) in your team's Apollo account with amounts, stages, and win probability. Costs no credits. Documented as a paid-plan endpoint (free keys get 403).

Apollo: List Email Accounts

apollo_list_email_accounts

List the email mailboxes linked to your team's Apollo account with their IDs, providers, and sending limits. Costs no credits. Documented as needing its scope or a master key. Feeds the sending-mailbox field on the Add Contacts to Sequence node.

Apollo: List Lists and Labels

apollo_list_lists

List every list/label in your Apollo workspace with its ID, name, record type (modality), and cached record count. Costs no credits. Documented as needing its scope or a master key. Feeds the label filters on the contact search node.

Apollo: List Users

apollo_list_users

List the users (teammates) in your Apollo account with their IDs and emails. Costs no credits. Documented as requiring a MASTER API key (a scoped key gets a 403). Feeds the owner_id fields on the account and deal nodes.

Apollo: Search Accounts

apollo_search_accounts

Search the ACCOUNTS (companies) your team has saved in Apollo, not the global company database (use Search Companies for that). Costs no credits. Display limit 50,000 records.

Apollo: Search Companies (1 Credit per Page)

apollo_search_organizations

Search Apollo's company database by name, domain, location, headcount, technology stack, and keywords. Costs 1 CREDIT PER PAGE (up to 100 results per page) and is documented as available on PAID Apollo plans only (free keys get 403). Display limit 50,000 records. Funding and revenue range filters use bracketed wire names; pass them via extra_query, e.g. {"revenue_range[min]": 1000000}.

Apollo: Search Contacts

apollo_search_contacts

Search the CONTACTS your team has saved in Apollo (your CRM records, not the global database; use Search People Database for that). Costs no credits. Documented as a paid-plan endpoint (free keys get 403). Display limit 50,000 records.

Apollo: Search People Database

apollo_search_people

Search Apollo's B2B people database by title, seniority, location, employer, and more. Costs NO credits and returns NO email addresses or phone numbers (last names are partially obfuscated for non-contacts); pipe a result's id into the Enrich Person node to reveal contact data, which is where credits are spent. Display limit 50,000 records (100 per page, 500 pages).

Apollo: Search Sequences

apollo_search_sequences

Find sequences (outreach campaigns) in your team's Apollo account by name, with step counts and performance stats. Costs no credits. Documented as a paid-plan endpoint needing its scope or a master key. Reading a sequence sends nothing; only the Add Contacts to Sequence node starts outreach.

Apollo: View API Usage and Rate Limits

apollo_view_api_usage

Report your team's per-endpoint API usage against its minute, hour, and day rate limits. Costs no credits. Documented as requiring a MASTER API key (a scoped key gets a 403). Useful as a guard step before large search or enrichment batches.

Action nodes 10

Apollo: Add Contacts to Sequence (Sends Real Emails)

apollo_add_contacts_to_sequence

Add saved contacts to a sequence. THIS STARTS REAL OUTREACH: if the sequence is active, Apollo begins sending its emails to these real people from the connected mailbox on the sequence's schedule, and a sent email cannot be unsent. Only wire this into automations that are meant to contact people, and test against a paused or test sequence first. Costs no credits. Get the mailbox ID from the List Email Accounts node and contact IDs from the contact nodes.

Apollo: Bulk Enrich People (Consumes Credits)

apollo_bulk_enrich_people

Enrich UP TO 10 PEOPLE in one call (Apollo's documented maximum for this endpoint; this node does not batch beyond it). Each entry in details is matched like the single Enrich Person node. Honesty notes: (1) setting the reveal options consumes Apollo credits when data is found (1 credit for demographics or an email, plus 8 credits when a mobile number is returned); (2) the output contains personal contact data and node outputs are stored in execution records, so only enrich people your organization has a lawful basis to process. Credits are charged per person found, so a full batch with reveals enabled can consume up to 9 credits per person.

Apollo: Create Account

apollo_create_account

Create a new account (company record) in your team's Apollo workspace. Provide at least a name or a domain. Costs no credits. Note: Apollo does NOT dedupe accounts created via the API, so creating the same company twice makes two records.

Apollo: Create Contact

apollo_create_contact

Create a new contact record in your team's Apollo workspace. Costs no credits. With run_dedupe on, a matching existing contact (by ID, email, or name plus company) is updated in place instead of duplicated; off by default.

Apollo: Create Deal

apollo_create_deal

Create a new deal (opportunity) in your team's Apollo account. Costs no credits.

Apollo: Enrich Person (Consumes Credits)

apollo_enrich_person

Match one person against Apollo's database and enrich them with employment, location, and contact data. Provide at least one identifier (name, email, domain, LinkedIn URL, or Apollo person ID); more identifiers give better matches. Honesty notes: (1) setting the reveal options consumes Apollo credits when data is found (1 credit for demographics or an email, plus 8 credits when a mobile number is returned); (2) the output contains personal contact data and node outputs are stored in execution records, so only enrich people your organization has a lawful basis to process. Phone reveals are asynchronous: Apollo posts the number to your webhook_url, not into this node's output.

Apollo: Update Account

apollo_update_account

Update an existing account record. Only the fields you fill are changed. Costs no credits.

Apollo: Update Contact

apollo_update_contact

Update an existing contact record. Only the fields you fill are changed, EXCEPT label_names: passing it OVERWRITES the contact's list membership with exactly the names given. Costs no credits.

Apollo: Update Contact Stage (Bulk)

apollo_update_contact_stage

Move one or many contacts to a different contact stage in one call. Costs no credits. Get stage IDs from the List Contact Stages node.

Apollo: Update Deal

apollo_update_deal

Update an existing deal: rename it, change the amount, move it to another stage, or reassign the owner. Only the fields you fill are changed. Costs no credits.

Using the integration

On the automation canvas

Apollo nodes chain with every other node: a scheduled Apollo: Search People Database sweep can feed a shortlist into Mattering Sales or a Mattering database, Apollo: List Company Job Postings (1 Credit per Page) can flag accounts that are hiring, and an approval task in Mattering Productivity can sit between enrichment and any sequence add. There is no inbound Apollo trigger, so reacting to changes means polling a read node on a schedule and acting on the difference.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can search the database, read CRM records, and check usage through the same nodes your workflows use. The zero-credit search and list nodes are the safest surface to hand an agent; the enrichment and sequence nodes deserve the same gating an automation would give them.

Search is free, enrichment spends

Apollo: Search People Database costs zero credits and returns profiles without emails or phone numbers; that is Apollo's boundary, not a limitation of the integration. Apollo: Enrich Person (Consumes Credits) is where contact data is revealed and credits are spent: 1 credit when demographics or an email is found, plus 8 credits when a mobile number is returned, and phone reveals arrive asynchronously at your webhook URL rather than in the node output. Apollo: Bulk Enrich People (Consumes Credits) enriches up to 10 people per call, Apollo's documented maximum, and the integration does not loop or fan out beyond it. Enrichment output is personal data and lands in execution records: only enrich people your organization has a lawful basis to process.

The one node that sends email

Apollo: Add Contacts to Sequence (Sends Real Emails) is the integration's single destructive node. If the sequence is active, Apollo begins sending its emails to those real people from the connected mailbox on the sequence's schedule, and a sent email cannot be unsent. Its safety booleans default to off, mirroring Apollo's own defaults, so contacts already active in other campaigns are skipped rather than emailed twice. Get the mailbox ID from Apollo: List Email Accounts, test against a paused sequence first, and keep the node behind a condition, an approval task, or a manual run.

Scoped keys, master keys, and plan gates

Two different gates produce 403s on a working key. Key grade: Apollo: List Users and Apollo: View API Usage and Rate Limits are documented as master key only, and several other reads need their scope chosen when the key is created; a master key clears all of it. Plan: Apollo: Search Companies (1 Credit per Page), Apollo: Search Contacts, Apollo: List Deals, and Apollo: Search Sequences are documented as paid-plan endpoints, so free-tier keys get 403 there regardless of key grade. Apollo: View API Usage and Rate Limits doubles as a free guard step before large search or enrichment batches.

CRM records and their gotchas

The contact, account, and deal nodes read and write your team's own Apollo records for zero credits. Three behaviors to know: Apollo does not dedupe accounts created through the API, so running Apollo: Create Account on the same company twice makes two records; Apollo: Create Contact has a run_dedupe option that updates a matching existing contact in place, off by default; and on Apollo: Update Contact, passing label_names overwrites the contact's list membership with exactly the names given. Stage IDs come from Apollo: List Contact Stages, Apollo: List Account Stages, and Apollo: List Deal Stages, and bracketed filters such as revenue_range[min] ride the extra_query field under their exact wire names.

Troubleshooting

Test Connection fails with a 401
The key is invalid, was revoked, or picked up stray whitespace when pasted. The auth health endpoint works with any key scope, so a 401 here means the key itself is bad rather than under-scoped. Create a fresh key in Apollo and update the credential on the connector.
Test Connection passes but a node returns a 403
Two possibilities, both on Apollo's side. If the node is Apollo: List Users or Apollo: View API Usage and Rate Limits, the key is not a master key: those are documented as master key only, and other reads fail the same way when their scope was not selected at key creation. If the node is Apollo: Search Companies (1 Credit per Page), Apollo: Search Contacts, Apollo: List Deals, or Apollo: Search Sequences, the workspace is on a free plan: those are documented as paid-plan endpoints. The connection test cannot catch either case because the health endpoint accepts any key scope.
People search results contain no email addresses or phone numbers
That is the design working, on Apollo's side and this integration's. Apollo: Search People Database costs zero credits precisely because it returns no contact data, and last names are partially obfuscated for people who are not already contacts. To reveal contact data, pipe a result's id into Apollo: Enrich Person (Consumes Credits), which is where credits are spent.
A person lookup returns email_not_unlocked@domain.com
That literal placeholder is what Apollo: Get Person by ID (1 Credit) returns in the email field for people not saved as contacts, even when email_status says verified. It is not a bug in the workflow and not a real address. Run Apollo: Enrich Person (Consumes Credits) with the reveal options set to actually unlock an email.
An enrichment ran but no phone number came back
Phone reveals are asynchronous by design: Apollo posts the mobile number to the webhook_url you provide on Apollo: Enrich Person (Consumes Credits), not into the node's output. Check that a webhook URL was supplied and that the receiving endpoint logged the delivery. When a mobile number is returned, Apollo charges 8 credits on top of the match, so a missing webhook also means the reveal cannot complete.
A bulk enrichment call rejects the batch
Apollo: Bulk Enrich People (Consumes Credits) and Apollo: Bulk Enrich Companies (Consumes Credits) carry Apollo's documented maximum of 10 records per call, and the integration deliberately does not loop or fan out beyond it. Split larger lists into batches of 10, and consider running Apollo: View API Usage and Rate Limits first as a free guard step before a long run.
Contacts were added to a sequence but some were skipped
The response from Apollo: Add Contacts to Sequence (Sends Real Emails) includes skipped_contact_ids, and the node's safety booleans default to off, mirroring Apollo's own defaults: contacts already active in other campaigns, among other guarded cases, are skipped rather than emailed twice. Enable a safety bypass only when you specifically mean to override it. Also note that a paused sequence accepts contacts without sending anything, which is exactly why testing against a paused sequence is the recommended first run.
Duplicate companies or contacts are piling up in Apollo
Apollo does not dedupe accounts created through the API, so a workflow that runs Apollo: Create Account without checking first will mint a new record every time; put Apollo: Search Accounts in front of it and branch on whether the company already exists. For people, turn on the run_dedupe option on Apollo: Create Contact, which updates a matching existing contact in place instead of duplicating it; it is off by default.

Apollo.io is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products