An Apollo.io MCP where search is free and sending email is a deliberate step
Connect one Apollo API key and 30 nodes for people and company search, enrichment, CRM records, and sequences become workflow steps for visual automations and AI agents. People search costs no credits and returns no contact data; enrichment is where credits are spent, and the nodes say so. Exactly one node can start real outreach email, and it is labeled and built to be gated.
What the Apollo.io MCP connector does
The Apollo.io connector for Mattering Automations is 30 nodes across Apollo's three surfaces: the global B2B database (people search, person and company enrichment, company search, and job postings), the CRM layer (contacts, accounts, and deals with their stage lists, lists and labels, users, and connected mailboxes), and the outreach engine (finding sequences and adding contacts to them). Reads and writes on your team's own CRM records cost nothing; database enrichment and a few searches consume Apollo credits, and every node that spends credits says so in its name or description.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can build a prospect list, check which companies are hiring, and read deal stages without anyone opening Apollo, and the zero-credit search nodes make that safe to do all day.
The credit and data boundary is stated, not hidden. Apollo: Search People Database costs no credits and returns no email addresses or phone numbers; enrichment is where credits are spent, and the enrichment nodes explain the mechanism before you run them. Enrichment output is real people's contact data, and node outputs land in execution records, so the nodes carry the same reminder this page does: only enrich people your organization has a lawful basis to process. Phone reveals are asynchronous, delivered to a webhook URL you provide rather than into the node's output.
The outreach boundary is a single node. Apollo: Add Contacts to Sequence (Sends Real Emails) is the connector's one destructive node: adding a contact to an active sequence starts real emails 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, and the intended pattern is to keep it behind a condition, an approval task, or a manual run, with enriched leads reviewed in Mattering Sales or a Mattering database first.
One connection, three surfaces
- Visual automations. Drag Apollo.io nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Apollo.io node, ready to drop on the canvas
30 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 20
Apollo: Bulk Enrich Companies (Consumes Credits)
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
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)
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)
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
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)
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
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)
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
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
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
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
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
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
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
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)
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
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
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
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
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)
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)
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
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
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
Create a new deal (opportunity) in your team's Apollo account. Costs no credits.
Apollo: Enrich Person (Consumes Credits)
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
Update an existing account record. Only the fields you fill are changed. Costs no credits.
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)
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
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.
Connecting Apollo.io takes one credential
Apollo issues API keys from the API settings inside your Apollo workspace; see docs.apollo.io for the current path. Keys come in two grades: regular keys are scoped to the endpoints chosen at creation, and a master key unlocks everything. A master key is recommended for full node coverage, because several workspace reads are documented as master key only. The key is sent as the x-api-key header on every request, and it identifies the workspace rather than a person: API actions attribute to the workspace's longest-standing active admin.
In your Apollo workspace, create an API key. Choose a master key if you want all 30 nodes: Apollo: List Users and Apollo: View API Usage and Rate Limits are documented as master key only, and several other reads need their scope selected at creation.
In Mattering Automations, open Connectors, click Add Connector, choose Apollo.io, and create a credential with the key.
Click Test Connection. Mattering calls Apollo's own auth health endpoint, which costs zero credits and works with any key scope; a good key reports healthy.
All 30 Apollo nodes appear in the canvas palette. Apollo: Search People Database is a good first run: it costs no credits and returns no contact data, so exploring is free.
Common uses for the Apollo.io MCP
Prospect research that costs nothing
Apollo: Search People Database searches Apollo's B2B database by title, seniority, location, and employer for zero credits, returning profiles without email addresses or phone numbers. Apollo: Search Accounts and Apollo: Search Contacts read the records your team has already saved. An agent can build and refine target lists all day without spending a credit or touching contact data.
Enrichment where the spend is explicit
Apollo: Enrich Person (Consumes Credits) matches one person and, when the reveal options are set, spends credits to return contact data: 1 credit when demographics or an email is found, plus 8 credits when a mobile number is returned. Apollo: Bulk Enrich People (Consumes Credits) does the same for up to 10 people per call, Apollo's documented maximum for the endpoint. Both nodes state that their output is personal data that lands in execution records, so enrich only people your organization has a lawful basis to process.
Company intelligence and buying signals
Apollo: Enrich Company by Domain (1 Credit) returns firmographics for one company, Apollo: Search Companies (1 Credit per Page) searches the global company database on paid Apollo plans, and Apollo: List Company Job Postings (1 Credit per Page) lists a company's active job postings, a strong signal of who is hiring for what. All of it is company data, not personal data.
CRM records kept in sync for free
Apollo: Create Contact, Apollo: Update Contact, Apollo: Create Account, Apollo: Update Account, Apollo: Create Deal, and Apollo: Update Deal read and write your team's own Apollo records for zero credits. Apollo: Update Contact Stage (Bulk) moves one or many contacts in a single call, with stage IDs supplied by Apollo: List Contact Stages, Apollo: List Account Stages, and Apollo: List Deal Stages.
Enriched leads landing in Mattering Sales
Because Mattering is a work platform rather than middleware, an enrichment run does not end in a JSON blob: enriched leads can flow into Mattering Sales or a Mattering database as records a person can actually read, with a review task in Mattering Productivity attached so a human decides what happens next. That review gate is the natural place to sit between enrichment and any sequence add.
Sequences with a person in the loop
Apollo: Search Sequences reads campaign names, step counts, and stats without sending anything, and Apollo: List Email Accounts supplies the sending mailbox ID. The only node that starts outreach is Apollo: Add Contacts to Sequence (Sends Real Emails), and the working pattern is to run it behind an approval step, testing against a paused sequence first.
Example: Free search finds the leads, credits are spent deliberately, and a person approves before any email
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a weekly schedule runs the prospecting sweep.
Apollo: Search People Database finds people matching the target titles, seniority, and locations. Zero credits, and no contact data is returned or stored.
A condition keeps only the strongest matches, and Apollo: Enrich Person (Consumes Credits) reveals contact data for that shortlist, spending credits only on people who passed the filter.
The enriched leads land in Mattering Sales, or a Mattering database, as records a person can read.
A review task in Mattering Productivity holds the batch: someone checks the list and approves the people outreach should actually contact.
Only after approval, Apollo: Create Contact saves each lead and Apollo: Add Contacts to Sequence (Sends Real Emails) adds them to the campaign, which is the moment real outreach begins.
Apollo.io MCP questions, answered
What Apollo.io operations are supported?
30 nodes: people search and enrichment (single and bulk, capped at Apollo's documented 10 records per call), company search, enrichment, and job postings, contacts, accounts, and deals with their stage lists, lists and labels, users and connected mailboxes, API key health and usage reporting, sequence search, and adding contacts to a sequence. Deliberately not shipped: sequence lifecycle writes (create, activate, deactivate, archive), email drafts and send-email-now, waterfall enrichment, and the tasks, calls, and notes surface. The connector ships exactly one send-capable node by design.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
What consumes Apollo credits?
Nothing hidden, and the numbers are Apollo's own credit charges, not ours. Apollo: Search People Database, the CRM reads and writes, the stage, list, user, and mailbox nodes, and adding contacts to a sequence cost zero credits. Person enrichment charges when data is found: 1 credit for demographics or an email, plus 8 credits when a mobile number is returned. Company enrichment and lookups cost 1 credit per company, and Apollo: Search Companies (1 Credit per Page) and Apollo: List Company Job Postings (1 Credit per Page) charge per page. Apollo: View API Usage and Rate Limits is a free guard step to run before large batches.
Why does people search return no email addresses?
By design, on Apollo's side and ours. Apollo: Search People Database costs zero credits precisely because it returns profiles without emails or phone numbers, with last names partially obfuscated for people who are not already your contacts. The same boundary shows up on Apollo: Get Person by ID (1 Credit): for people not saved as contacts, the email field returns the literal placeholder email_not_unlocked@domain.com even when the status says verified. Revealing real contact data is what Apollo: Enrich Person (Consumes Credits) is for, and that is where credits are spent.
Can this connector send emails by accident?
It is built so it cannot do so silently. Exactly one node starts outreach: Apollo: Add Contacts to Sequence (Sends Real Emails). Adding a contact to an active sequence starts real emails from the connected mailbox on the sequence's schedule, and a sent email cannot be unsent. The node's safety booleans default to off, mirroring Apollo's own defaults, and the warning is in the label so it is visible on the canvas. Keep it behind a condition, an approval task, or a manual run, and test against a paused sequence first.
What about the personal data enrichment returns?
Enrichment output is real people's contact data, and node outputs are stored in execution records, so it does not vanish after the run. The enrichment nodes carry the reminder in their own descriptions: only enrich people your organization has a lawful basis to process. Phone reveals are asynchronous: Apollo posts the number to the webhook URL you provide rather than returning it inline, so mobile numbers arrive at an endpoint you control, not in the node output.
Why does a valid key get 403 errors on some nodes?
Two separate gates, both on Apollo's side. First, key grade: Apollo keys are either scoped to chosen endpoints or master keys, and Apollo: List Users and Apollo: View API Usage and Rate Limits are documented as master key only, with several other reads needing their scope selected at creation; a master key clears all of these. Second, 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 a free-tier key gets 403 there regardless of grade. The connection test uses Apollo's auth health endpoint, which works with any key scope, so a passing test does not guarantee every node.
Can an Apollo event trigger a workflow?
Not as a trigger node in this connector: there is no inbound Apollo trigger. The honest pattern today is polling: run Apollo: Search Contacts or Apollo: List Deals on a schedule, compare against the previous run, and act on what changed. The one webhook in the connector points the other way: it is the URL you give Apollo: Enrich Person (Consumes Credits) so asynchronous phone reveals have somewhere to land.
Put Apollo.io to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Apollo.io is a product of its respective owner; Mattering is an independent platform.