← Back to all apps

Apollo.io

Businessby Apollo.io
Open in ChatGPTOpen in ClaudeWebsite
Launched May 27, 2026 on ChatGPTLaunched Feb 20, 2026 on Claude

Connect Apollo to Claude so you can prospect and take action from a single conversation. Search Apollo's database to find the right people and companies, then enrich records to reveal verified contact details when you're ready. Create or update contacts, and add or remove contacts from existing sequences to keep outbound moving.

27ChatGPT Tools
13Claude Tools
Apollo.ioDeveloper
BusinessCategory

Use Cases

sales-and-marketing

Available Tools

Bulk Create Accounts

apollo_accounts_bulk_create
Full Description

Create many accounts (companies) in a single call. Pass an array of account objects under accounts. No deduplication is applied: each object becomes a new record even if it matches an existing account by name or domain. Use the single Create an Account endpoint when adding only one account; use Update an Account to modify an existing account. Once created, accounts are not removed by subsequent calls — review the array before sending.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (1 required, 2 optional)
Required
accountsarray

Array of account objects to create. Each object accepts the same fields as the single Create an Account endpoint.

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

Create an Account

apollo_accounts_create
Full Description

Use the Create an Account endpoint to add a new account to your team's Apollo account. Use this when adding a single account; to add several at once, use the Bulk Create Accounts tool (apollo_accounts_bulk_create). In Apollo terminology, an account is a company that your team has explicitly added to your database. Apollo does not apply deduplication processes when you create a new account via the API. If your entry has the same name, domain, or other details as an existing account, Apollo will create a new account instead of updating the existing account. To update an existing account, use the Update an Account endpoint instead.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 6 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

domainstring

The domain of the account. Example: apollo.io

namestring

The name of the account (company). Example: Apollo

phonestring

The phone number for the account. Example: 555-303-1234

raw_addressstring

The address of the account. Example: 535 Mission St, Suite 1100, San Francisco, CA 94105

Update an Account

apollo_accounts_update
Full Description

Use the Update an Account endpoint to update existing accounts in your team's Apollo account. In Apollo terminology, an account is a company that your team has explicitly added to your database. To create a new account, use the Create an Account endpoint instead.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (1 required, 6 optional)
Required
idstring

The Apollo ID for the account that you want to update. Example: 63f53afe4ceeca00016bdd2f

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

domainstring

Update the domain. Example: apollo.io

namestring

Update the account name. Example: Apollo

phonestring

Update the phone number. Example: 555-303-1234

raw_addressstring

Update the address. Example: 535 Mission St, Suite 1100, San Francisco, CA 94105

Query Analytics Data

apollo_analytics_sync_report
Full Description

Query Apollo's sales analytics data with flexible filtering, grouping, and aggregation. Supports metrics across emails, calls, meetings, tasks, opportunities, and conversation intelligence. Break down by 55+ dimensions including time, user, contact stage, account details, and more.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (1 required, 7 optional)
Required
metricsarray

Select 1-15 metrics. Categories: Email, Phone Calls, Meetings, Tasks, Contacts/Accounts, Opportunities, Sequences, Conversation Intelligence, LinkedIn. Key distinctions: - Phone: num_phone_calls_completed (all attempts) vs num_phone_calls_connect (recipient answered), num_phone_calls_connect_positive/negative/neutral (outcome sentiment), percent_phone_calls_connect (connection rate) - Meetings: num_all_meetings_scheduled (includes cancelled) vs num_meetings_held (actually occurred), num_all_meetings_rescheduled (rescheduled meetings), num_calendar_events_scheduled/cancelled (calendar events created/cancelled), num_all_meetings_scheduled_via_email/call (booked via email/call) - Tasks: overdue_tasks (all overdue including completed late) vs unfinished_overdue_tasks (still pending), percent_unfinished_overdue_tasks (share of scheduled tasks that are overdue and unfinished), percent_tasks_completed (completion rate), percent_tasks_completed_on_time (on-time completion rate) - Opportunities: avg_salescycle_days (days from creation to close) - Conversation: avg_talk_ratio (rep vs customer talk time), avg_question_rate (questions per conversation), avg_longest_monologue (longest uninterrupted speech), speaker_switches (times speaker changed) - Email: email_daily_limit is the configured daily outbound send limit per bucket (mailbox-level settings). Combine with num_emails_sent and/or other email metrics on the same query; use group_by or pivot_group_by on smart_user_id, smart_subteam_id, email_account_id, or smart_datetime_day/week to relate activity to the limit.

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

date_rangeobject

Time period. Use preset modality OR range_start + range_end (not both).

filtersobject

Optional filters to narrow down data. All filters are AND'ed together.

group_byarray

Primary breakdown dimension. For time series use smart_datetime_* options. For user analysis use smart_user_id or smart_subteam_id. Key email dimensions: - emailer_message_type: Email type (manual, sequence, reply, forwarded, etc.) - emailer_step_id: Breakdown by sequence step (by step ID) - emailer_touch_id: Breakdown by sequence step (by touch number/variant)

pivot_group_byarray

Optional second dimension for cross-tab/pivot table. Requires group_by. Use low-cardinality dimensions for best results.

sortobject

Sort grouped results by metric value. Only applies with group_by.

Bulk Create Contacts

apollo_contacts_bulk_create
Full Description

Create many contacts in a single call. Pass an array of contact objects under contacts. No deduplication is applied: each object becomes a new record even if it matches an existing contact by name or email. Use the single Create Contact endpoint when adding only one contact; use Update Contact to modify an existing contact. Once created, contacts are not removed by subsequent calls — review the array before sending.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (1 required, 2 optional)
Required
contactsarray

Array of contact objects to create. Each object accepts the same fields as the single Create Contact endpoint.

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

Create Contact

apollo_contacts_create
Full Description

Create a new contact in Apollo. Use this when adding a single contact; to add several at once, use the Bulk Create Contacts tool (apollo_contacts_bulk_create). By default, Apollo does not apply deduplication. If an entry has the same name, email, or other details as an existing contact, a new contact is created. Set run_dedupe to true to prevent duplicates.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 17 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

account_idstring

The Apollo ID for the account. Example: 63f53afe4ceeca00016bdd2f

corporate_phonestring

The work/office phone number. Example: +44 7911 123456

direct_phonestring

The primary phone number. Example: 555-303-1234

emailstring

The email address of the contact. Example: example@email.com

first_namestring

The first name of the contact. Example: Tim

home_phonestring

The home phone number. Example: 555-303-1234

label_namesarray

Lists to which the contact belongs

last_namestring

The last name of the contact. Example: Zheng

mobile_phonestring

The mobile phone number. Example: 555-303-1234

organization_namestring

The name of the contact's employer (company). Example: apollo

other_phonestring

Alternative phone number. Example: 555-303-1234

present_raw_addressstring

The personal location for the contact. Example: Atlanta, United States

run_dedupeboolean

Set to true to enable deduplication logic that prevents creating duplicate contacts. Default is false.

Default: False
titlestring

The current job title that the contact holds. Example: senior research analyst

website_urlstring

The corporate website URL. Example: https://www.apollo.io/

Search for Contacts

apollo_contacts_search
Full Description

Use the Search for Contacts endpoint to search for the contacts that have been added to your team's Apollo account. In Apollo terminology, a contact is a person that your team has explicitly added to your database. A contact will have their data enriched in some way, such as accessing an email address or a phone number. This endpoint only returns contacts in the search results. To search for people in the Apollo database, call the People API Search endpoint. To protect Apollo's performance for all users, this endpoint has a display limit of 50,000 records (100 records per page, up to 500 pages). Add more filters to narrow your search results as much as possible. This limitation does not restrict your access to Apollo's database; you just need to access the data in batches.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 7 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

pageinteger

The page number of the Apollo data that you want to retrieve. Use this parameter in combination with the per_page parameter to make search results navigable and improve the performance of the endpoint. Example: 4

per_pageinteger

The number of search results that should be returned for each page. Limiting the number of results per page improves the endpoint's performance. Use the page parameter to search the different pages of data. Example: 10

q_keywordsstring

Add keywords to narrow the search of the contacts in your team's Apollo account. Keywords can include combinations of names, job titles, employers (company names), and email addresses. Examples: tim zheng; senior research analyst; microsoft

sort_ascendingboolean

Set to true to sort the matching contacts in ascending order. This parameter must be used with sort_by_field. Otherwise, the sorting logic is not applied. Example: true. Defaults to false.

sort_by_fieldstring

Sort the matching contacts by 1 of the following options: contact_last_activity_date (The most recent activity date recorded first), contact_email_last_opened_at (The most recent email opened date first), contact_email_last_clicked_at (The most recent email clicked first), contact_created_at (The most recently created first), contact_updated_at (The most recently updated first).

Update Contact

apollo_contacts_update
Full Description

Update an existing contact in your team's Apollo account. In Apollo terminology, a contact is a person that your team has explicitly added to your database. A contact will have their data enriched in some way, such as accessing an email address or a phone number. To create a new contact, use the Create a Contact endpoint instead.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (1 required, 16 optional)
Required
idstring

The Apollo ID for the contact that you want to update. To find contact IDs, call the Search for Contacts endpoint and identify the id value for the contact. Example: 66e34b81740c50074e3d1bd4

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

account_idstring

Update the account ID. Example: 63f53afe4ceeca00016bdd2f

corporate_phonestring

Work/office phone.

direct_phonestring

Primary phone.

emailstring

Update the contact email. Example: example@email.com

first_namestring

Update the contact's first name. Example: Tim

home_phonestring

Home phone.

label_namesarray

Replace lists this contact belongs to. (Passing new values will overwrite existing lists.)

last_namestring

Update the contact's last name. Example: Zheng

mobile_phonestring

Mobile phone.

organization_namestring

Update the employer (company) name. Example: apollo

other_phonestring

Alternate phone.

present_raw_addressstring

Update location (city/state/country). Example: Atlanta, United States

titlestring

Update the job title. Example: senior research analyst

website_urlstring

Update the employer website URL. Example: https://www.apollo.io/

Get a List of Email Accounts

apollo_email_accounts_index
Full Description

Use the Get a List of Email Accounts endpoint to retrieve information about the linked email inboxes that your teammates use in your Apollo account. In particular, this endpoint returns IDs for each of your team's linked email accounts, which can be used with the Add Contacts to a Sequence endpoint. Always call this endpoint before adding contacts to a sequence. Never guess or fabricate email account IDs — use only IDs returned by this endpoint. If the user's intended sender is ambiguous (e.g., multiple team members share a first name), present all matching email accounts to the user and ask them to select the correct one before proceeding.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 2 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

Add Contacts to a Sequence

apollo_emailer_campaigns_add_contact_ids
Full Description

Use the Add Contacts to a Sequence endpoint to add contacts to existing sequences in your team's Apollo account. This action sends real emails from a real person's mailbox and is irreversible once emails are dispatched.

Before calling this endpoint, follow these steps in order: 1. Call the Search for Sequences endpoint to find the target sequence by name. If multiple sequences match, present all matches to the user and ask them to confirm which sequence they intend. Do not assume. 2. Call the Get a List of Email Accounts endpoint to retrieve valid sender email account IDs. Never guess or fabricate send_email_from_email_account_id — always use id(s) returned by Get a List of Email Accounts (one id as a string, or multiple as an array of strings). If the user's request is ambiguous (e.g., "Sarah's account" matches multiple email accounts), list all matching options and ask the user to choose. 3. Present the user with a confirmation summary that includes: the sender email address, the sequence name, the number of contacts to be added, and the enrollment status (active or paused). Wait for the user to explicitly confirm before proceeding. Do not enroll contacts without explicit user approval, even if the user says "just do it" — always show the summary first. 4. Only after the user explicitly confirms, call this endpoint to enroll the contacts.

In Apollo terminology, a contact is a person that your team has explicitly added to your database. Only contacts can be added to sequences. To enrich a person's data, call the People Enrichment endpoint. Then, to add the person as a contact in your database, call the Create a Contact endpoint.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (3 required, 16 optional)
Required
emailer_campaign_idstring

The same ID as the id field above. Must be the exact id value returned by apollo_emailer_campaigns_search in this session. Never use an ID from memory, prior sessions, or assumptions. Example: 66e9e215ece19801b219997f

idstring

The Apollo ID for the sequence to which you want to add contacts. Must be the exact id value returned by apollo_emailer_campaigns_search in this session. Never use an ID from memory, prior sessions, or assumptions. Example: 66e9e215ece19801b219997f

send_email_from_email_account_idstring

The Apollo ID(s) for the email account(s) used to send to contacts you add to the sequence. Accepts either one id as a string, or multiple ids as an array of strings (multi-mailbox / rotation). To find ids, call the Get a List of Email Accounts endpoint. Examples: 6633baaece5fbd01c791d7ca (string) or ["6633baaece5fbd01c791d7ca", "6633baaece5fbd01c791d7cb"] (array).

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

add_if_in_queueboolean

Set to true if you want to add contacts even if they are currently in the queue for processing. Defaults to false.

Default: False
auto_unpause_atstring

DateTime when paused contacts should be automatically unpaused. Must be used with status=paused. Format: ISO 8601 datetime string.

contact_idsarray

The Apollo IDs for the contacts to add to the sequence. Every ID must be a real 24-character hex string returned by a tool call in this session (e.g. apollo_contacts_create or apollo_contacts_search). Never use placeholders like <CONTACT_ID_1>, template strings, or IDs from memory or prior sessions. If you do not have real IDs from a tool result in this conversation, call apollo_contacts_search first. Note: Either contact_ids or label_names must be provided. Example: 66e34b81740c50074e3d1bd4

contact_verification_skippedboolean

Set to true if you want to skip contact verification during the addition process. Defaults to false.

Default: False
contacts_without_ownership_permissionboolean

Set to true if you want to add contacts even if you don't have ownership permission for them. Defaults to false.

Default: False
label_namesarray

Alternative to contact_ids. Array of label names to identify contacts to add to the sequence. Contacts with these labels will be added to the sequence. Note: Either contact_ids or label_names must be provided.

send_email_from_email_addressstring

Optional specific email address to send from within the email account.

sequence_active_in_other_campaignsboolean

Set to true if you want to add contacts to the sequence even if they have been added to other sequences. This parameter does not differentiate between active and paused sequences. Defaults to false.

Default: False
sequence_finished_in_other_campaignsboolean

Set to true if you want to add contacts to the sequence if they have been marked as finished in another sequence. Defaults to false.

Default: False
sequence_job_changeboolean

Set to true if you want to add contacts to the sequence even if they have recently changed jobs. Defaults to false.

Default: False
sequence_no_emailboolean

Set to true if you want to add contacts to the sequence even if they do not have an email address. Defaults to false.

Default: False
sequence_same_company_in_same_campaignboolean

Set to true if you want to add contacts to the sequence even if other contacts from the same company are already in the sequence. Defaults to false.

Default: False
sequence_unverified_emailboolean

Set to true if you want to add contacts to the sequence if they have an unverified email address. Defaults to false.

Default: False
statusstring

Initial status for added contacts. When set to paused along with auto_unpause_at, enables scheduled addition of contacts.

Options:activepaused

Activate a Sequence

apollo_emailer_campaigns_approve
Full Description

Activate (turn on) an existing sequence so that contacts enrolled in it begin receiving emails and tasks. This is the toggle that flips active=false to active=true.

THIS ACTION HAS REAL-WORLD CONSEQUENCES. Once active, Apollo will start sending emails from the user's mailbox on the configured schedule. Activation is irreversible for emails already dispatched.

BEFORE calling this tool you MUST: 1. Confirm the user has reviewed the sequence's steps and message bodies (e.g. by surfacing a step-by-step summary). 2. Confirm the user has selected a sender email account (apollo_email_accounts_index) and added contacts (apollo_emailer_campaigns_add_contact_ids), if relevant. 3. Get explicit user confirmation in the same turn — do not assume prior consent.

The sequence must have at least one step. The team must not have hit its sequence limit.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (1 required, 2 optional)
Required
idstring

The Apollo ID of the sequence to activate. Must be the exact id value returned by apollo_emailer_campaigns_search or apollo_sequences_create in this session. Never use an ID from memory, prior sessions, or assumptions. Example: 66e9e215ece19801b219997f

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

Remove Contacts from Sequences

apollo_emailer_campaigns_remove_or_stop_contact_ids
Full Description

Use the Remove or Stop Contacts from one or more existing sequences in your Apollo Account

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (3 required, 3 optional)
Required
contact_idsarray

The Apollo IDs for the contacts that you want to remove from the sequences. To find contact IDs, call the Search for Contacts endpoint and identify the id value for the contact. Example: 66e34b81740c50074e3d1bd4

emailer_campaign_idsarray

The Apollo IDs for the sequences that you want to remove the contacts from. To find sequence IDs, call the Search for Sequences endpoint and identify the id value for the sequence. Example: 66e9e215ece19801b219997f

modestring

The mode for the removal or stopping of the contacts. Possible values are remove and stop. Defaults to remove.

Options:removestop
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

stop_reasonstring

The reason for stopping / removing the contacts. This is only used if the mode is stop. Example: Contact requested removal

Search for Sequences

apollo_emailer_campaigns_search
Full Description

Use the Search for Sequences endpoint to search for the sequences that have been created for your team's Apollo account. This endpoint should be called before adding contacts to a sequence to retrieve the correct sequence ID. If multiple sequences match the search query, you must present all matching sequences to the user and ask them to confirm which one they intend before proceeding. Do not assume or pick one on their behalf.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 5 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

pagestring

The page number of the Apollo data that you want to retrieve. Use this parameter in combination with the per_page parameter to make search results for navigable and improve the performance of the endpoint. Example: 4

per_pagestring

The number of search results that should be returned for each page. Limiting the number of results per page improves the endpoint's performance. Use the page parameter to search the different pages of data. Example: 10

q_namestring

Add keywords to narrow the search of the sequences in your team's Apollo account. Keywords should directly match at least part of a sequence's name. For example, searching the keyword marketing might return the result NY Marketing Sequence, but not NY Marketer Conference 2025 attendees. This parameter only searches sequence names, not other sequence fields. Example: marketing conference attendees

List Sending Schedules

apollo_emailer_schedules_index
Full Description

List all sending schedules available in the user's team. A schedule defines the time windows (days of week, hours of day, time zone) during which Apollo will send emails for a sequence.

Use this tool when the user wants to pick a non-default schedule for a new sequence (apollo_sequences_create accepts emailer_schedule_id). If the user does not specify a schedule preference, omit emailer_schedule_id when creating the sequence and Apollo will use the user's default.

Returns an array of schedules, each with id, name, default flag, time_zone, and the per-day windows. Echo only id and name back to the user when presenting choices.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 2 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

Log Feedback

apollo_feedback_log
Full Description

Call this tool to report when a previous Apollo tool returned an unexpected, empty, or unhelpful result — for example, when a search returned no results despite valid inputs, a record was not found when it should exist, or a tool response was ambiguous or unclear. Include the name of the tool that failed and a clear description of what went wrong. Do NOT call this for successful tool results or expected empty states (e.g. a deliberate empty search).

Parameters (2 required, 2 optional)
Required
client_namestring

Your name as the MCP client calling this tool (e.g. claude, chatgpt, cursor). This helps identify which AI assistant generated the feedback.

messagestring

A clear description of what you attempted, what tool you called, and what went wrong or was unexpected. Include the result you received and what you expected instead. Example: "Called apollo_contacts_search with a valid contact filter — returned 0 results, expected at least 1 match."

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

Organization Search

apollo_mixed_companies_search
Full Description

Use the Organization Search endpoint to find companies in the Apollo database. Several filters are available to help narrow your search. To protect Apollo's performance for all users, this endpoint has a display limit of 50,000 records (100 records per page, up to 500 pages). Add more filters to narrow your search results as much as possible. CREDIT COST: Exactly 1 credit per request that returns at least one result. 0 credits if there are no matches. Before calling this tool, you MUST confirm with the user using these EXACT words: "This will consume 1 credit. Do you want to proceed?" Do NOT proactively show remaining credit balance. Only show it if the user asks. Do NOT paraphrase. Do NOT say "consumes credits" — say "1 credit". If this search is part of a larger batch, confirm the TOTAL count and credit cost upfront.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 20 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

currently_using_any_of_technology_uidsarray

Find organizations based on the technologies they currently use. Use underscores (_) to replace spaces and periods for technology names. Example: ['salesforce', 'google_analytics', 'wordpress_org']

latest_funding_amount_rangeobject

Filter by the amount the company received with its most recent funding round. Do not enter currency symbols, commas, or decimal points in the figure.

latest_funding_date_rangeobject

Filter by the date when the company received its most recent funding round.

organization_idsarray

An array of Apollo organization IDs to look up. Example: ['5e66b6381e05b4008c8331b8']

organization_job_locationsarray

The locations of the jobs being actively recruited by the company. Example: ['atlanta', 'japan']

organization_job_posted_at_rangeobject

Filter by the date when jobs were posted by the company.

organization_locationsarray

An array of strings of organization locations to filter by. Example: ['San Francisco, CA', 'United States']

organization_not_locationsarray

An array of strings of organization locations to exclude from the search. Useful for ensuring that you are excluding prospects in undesirable territory. Example: ['Ireland']

organization_num_employees_rangesarray

An array of intervals to include organizations of this size. Example: ['1,10', '11,50', '51,200', '201,500', '501,1000']

organization_num_jobs_rangeobject

Filter by the number of job postings active at the company.

pageinteger

The page number. Use with per_page for pagination. Example: 1

per_pageinteger

The number of results per page. Default is 10. Max is 100. Example: 25

q_organization_domains_listarray

An array of domains to filter by. Example: ['apollo.io', 'google.com']

q_organization_job_titlesarray

The job titles that are listed in active job postings at the company. Example: ['sales manager', 'research analyst']

q_organization_keyword_tagsarray

An array of organization keyword tags to filter by. Example: ['SaaS', 'fintech']

q_organization_namestring

The name of the organization to search for. Example: Apollo

revenue_rangeobject

Search for organizations based on their revenue. Set min and max to define a revenue range. Do not enter currency symbols, commas, or decimal points in the figure.

total_funding_rangeobject

Filter by the total amount the company received during all of its funding rounds combined. Do not enter currency symbols, commas, or decimal points in the figure.

People API Search

apollo_mixed_people_api_search
Full Description

Use the People API Search endpoint to find people in the Apollo database. Several filters are available to help narrow your search. This endpoint is primarily designed for prospecting net new people. This endpoint does not return email addresses or phone numbers. Use the People Enrichment or Bulk People Enrichment endpoints to enrich data. Some contact fields, including last names, may be masked or partially obfuscated in search results depending on the user's plan type. When displaying masked values, always inform the user that enrichment is required to reveal the full value, and offer to run the People Enrichment endpoint. To protect Apollo's performance for all users, this endpoint has a display limit of 50,000 records (100 records per page, up to 500 pages). Add more filters to narrow your search results as much as possible.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 23 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

contact_email_statusarray

Filter by email status. Example: ['verified', 'likely to engage', 'unverified', 'unavailable']

currently_not_using_any_of_technology_uidsarray

Exclude people from search based on any of the technologies their current employer uses. Use underscores to replace spaces and periods. Examples: ['salesforce', 'google_analytics', 'wordpress_org']

currently_using_all_of_technology_uidsarray

Find people based on all of the technologies their current employer uses. Use underscores to replace spaces and periods. Examples: ['salesforce', 'google_analytics', 'wordpress_org']

currently_using_any_of_technology_uidsarray

Find people based on any of the technologies their current employer uses. Use underscores to replace spaces and periods. Examples: ['salesforce', 'google_analytics', 'wordpress_org']

include_similar_titlesboolean

Set to false to return only strict matches for job titles defined in person_titles. Defaults to true.

organization_idsarray

An array of Apollo organization IDs to include in search results. To find IDs, call the Organization Search endpoint. Example: ['5e66b6381e05b4008c8331b8']

organization_job_locationsarray

Locations of jobs being actively recruited by the person's employer. Examples: ['atlanta', 'japan']

organization_job_posted_at_rangeobject

Filter by the date when jobs were posted by the person's current employer.

organization_locationsarray

An array of strings of organization locations to filter by. Example: ['San Francisco, CA', 'New York, NY']

organization_num_employees_rangesarray

An array of intervals to include people belonging to companies of this size. Example: ['1,10', '11,50', '51,200']

organization_num_jobs_rangeobject

Filter by the number of job postings active at the person's current employer.

pageinteger

The page number. Use with per_page for pagination. Example: 1

per_pageinteger

The number of results per page. Default is 10. Max is 100. Example: 25

person_locationsarray

An array of strings of person locations to filter by. Example: ['San Francisco, CA', 'United States']

person_senioritiesarray

An array of seniority levels. Example: ['senior', 'manager', 'director', 'vp', 'c_suite']

person_titlesarray

An array of job titles to filter by. Example: ['sales director', 'account executive']

q_keywordsstring

Add keywords to narrow the search. Keywords can include combinations of names, job titles, employers (company names), and email addresses. Examples: tim zheng; senior research analyst; microsoft

q_organization_domains_listarray

An array of organization domains to filter by. Example: ['apollo.io', 'google.com']

q_organization_job_titlesarray

Job titles listed in active job postings at the person's current employer. Examples: ['sales manager', 'research analyst']

q_organization_keyword_tagsarray

An array of organization keywords tags. Example: ['SaaS', 'fintech']

revenue_rangeobject

Filter by the revenue of the person's current employer. Set min and max to define a revenue range. Do not enter currency symbols, commas, or decimal points in the figure.

Bulk Organization Enrichment

apollo_organizations_bulk_enrich
Full Description

Use the Bulk Organization Enrichment endpoint to enrich data for up to 10 companies with a single API call. Provide a list of domains to enrich. Enriched data potentially includes industry information, revenue, employee counts, funding round details, and corporate phone numbers and locations.

CREDIT COST: Exactly 1 credit per matched company. 0 credits if not found. For N companies, maximum cost is N credits.

MANDATORY CONFIRMATION — You MUST say this EXACT message to the user before calling this endpoint: "This will enrich [N] companies and consume up to [N] credits (1 credit per match, no charge for unmatched). Do you want to proceed?" Do NOT paraphrase. Always state the exact count and exact credit cost. OPEN-ENDED / SEARCH-THEN-ENRICH: If enriching results from a prior search (e.g. "find and enrich SaaS companies"), you MUST: 1. Call the Profile endpoint with include_credit_usage=true to get the user's remaining credit balance. 2. Confirm the TOTAL scope UPFRONT with remaining balance: "Found [N] companies. Enriching all will use up to [N] credits. You have [X] credits remaining. Want to proceed, or narrow the scope?" 3. Do NOT start enriching in batches and confirm incrementally — confirm the full scope first. For "enrich everyone" or unbounded requests, ask the user to narrow scope or confirm total count before starting. Do NOT call this endpoint without explicit user approval.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (1 required, 2 optional)
Required
domainsarray

An array of company domains to enrich. Maximum 10 domains per request. Example: ['apollo.io', 'google.com']

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

Organization Enrichment

apollo_organizations_enrich
Full Description

Use the Organization Enrichment endpoint to enrich data for 1 company. Enriched data potentially includes industry information, revenue, employee counts, funding round details, and corporate phone numbers and locations.

CREDIT COST: Exactly 1 credit if found. 0 credits if not found.

MANDATORY CONFIRMATION — You MUST say this EXACT message to the user before calling this endpoint: "Enriching [domain] will consume 1 credit (no charge if not found). Do you want to proceed?" Do NOT proactively show remaining credit balance. Only show it if the user asks. Do NOT paraphrase. Do NOT say "consumes credits" — say "1 credit". If this is part of a larger batch, confirm the TOTAL count and credit cost upfront. Do NOT call this endpoint without explicit user approval.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (1 required, 2 optional)
Required
domainstring

The domain of the organization you want to enrich. Example: apollo.io

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

Organization Job Postings

apollo_organizations_job_postings
Full Description

Use the Organization Job Postings endpoint to retrieve the current job postings for a company. This can help you identify companies that are growing headcount in areas that are strategically important for you. To protect Apollo's performance for all users, this endpoint has a display limit of 10,000 records.

CREDIT COST: Exactly 1 credit per request.

MANDATORY CONFIRMATION — You MUST say this EXACT message to the user before calling this endpoint: "This will consume 1 credit. Do you want to proceed?" Do NOT proactively show remaining credit balance. Only show it if the user asks. Do NOT paraphrase. Do NOT say "consumes credits" — say "1 credit". If this is part of a larger batch, confirm the TOTAL count and credit cost upfront. Do NOT call this endpoint without explicit user approval.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (1 required, 4 optional)
Required
idstring

The Apollo ID for the organization whose job postings you want to retrieve. To find organization IDs, call the Organization Search endpoint and identify the id value. Example: 5e66b6381e05b4008c8331b8

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

pageinteger

The page number for pagination. Default is 1. Example: 1

per_pageinteger

The number of results per page. Default and maximum is 10000. Example: 100

Bulk People Enrichment

apollo_people_bulk_match
Full Description

For each person, provide identifying details such as first name, last name, email, organization name, domain, or LinkedIn URL. By default, this endpoint does not return personal emails or phone numbers.

Call apollo_people_phone_enrichment_status with that request_id after ~10 seconds to poll for results.

CREDIT COST: Exactly 1 credit per matched person. 0 credits if not found. For N people, maximum cost is N credits.

MANDATORY CONFIRMATION — You MUST say this EXACT message to the user before calling this endpoint: "This will enrich [N] people and consume up to [N] credits (1 credit per match, no charge for unmatched). Do you want to proceed?" Do NOT paraphrase. Always state the exact count and exact credit cost. OPEN-ENDED / SEARCH-THEN-ENRICH: If enriching results from a prior search (e.g. "find and enrich SaaS contacts"), you MUST: 1. Call the Profile endpoint with include_credit_usage=true to get the user's remaining credit balance. 2. Confirm the TOTAL scope UPFRONT with remaining balance: "Found [N] contacts. Enriching all will use up to [N] credits. You have [X] credits remaining. Want to proceed, or narrow the scope?" 3. Do NOT start enriching in batches and confirm incrementally — confirm the full scope first. For "enrich everyone" or unbounded requests, ask the user to narrow scope or confirm total count before starting. Do NOT call this endpoint without explicit user approval.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (1 required, 3 optional)
Required
detailsarray

An array of objects, each representing a person to enrich. Maximum 10 people per request.

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

reveal_personal_emailsboolean

Set to true to return personal email addresses. Default is false.

Default: False

People Enrichment

apollo_people_match
Full Description

Use the People Enrichment endpoint to enrich data for 1 person. Apollo relies on the information you pass via the endpoint's parameters to identify the correct person to enrich. If you provide more information about a person, Apollo is more likely to find a match within its database. By default, this endpoint does not return personal emails or phone numbers. Use the reveal_personal_emails parameter to retrieve personal emails.

Phone enrichment is async. When reveal_phone_number=true, the response includes a phone_enrichment.request_id.

Call apollo_people_phone_enrichment_status with that request_id after ~10 seconds to poll for results.

CREDIT COST: Exactly 1 credit per matched person. 0 credits if person is not found.

"Enriching [name] will consume 1 credit (no charge if not found). Do you want to proceed?" Do NOT proactively show remaining credit balance. Only show it if the user asks about their balance. Do NOT paraphrase. Do NOT say "consumes credits" — say "1 credit". Wait for explicit user confirmation before proceeding. If this is part of a larger batch, confirm the TOTAL upfront: "Enriching N contacts will cost up to N credits. Proceed?" Do NOT call this endpoint without explicit user approval. Do NOT enrich in a loop without upfront confirmation of full scope.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 12 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

domainstring

The domain of the person's employer. Example: apollo.io

emailstring

The email address of the person. Example: tim@apollo.io

first_namestring

The first name of the person. Example: Tim

hashed_emailstring

The MD5 or SHA-256 hashed email address of the person. Use this if you do not want to send the plain-text email.

idstring

The Apollo ID for the person. Each person in the Apollo database is assigned a unique ID. To find IDs, call the People API Search endpoint and identify the values for person_id. Example: 587cf802f65125cad923a266

last_namestring

The last name of the person. Example: Zheng

linkedin_urlstring

The LinkedIn profile URL of the person. Example: https://www.linkedin.com/in/timzheng

namestring

The full name of the person. Use this as an alternative to providing first_name and last_name separately. Example: Tim Zheng

organization_namestring

The name of the person's employer (company). Example: Apollo

reveal_personal_emailsboolean

Set to true to return personal email addresses for the person. Default is false.

Default: False

Create a Sequence

apollo_sequences_create
Full Description

Create a new multi-step outreach sequence (also called an emailer campaign) in the user's Apollo workspace. A sequence has a name, an optional sending schedule, and an ordered list of steps.

Each step is one of: auto_email (Apollo sends automatically), manual_email (rep clicks send), call, action_item, linkedin_step_connect, linkedin_step_message, linkedin_step_view_profile, linkedin_step_interact_post.

BEFORE calling this tool: 1. Confirm with the user the sequence name, target audience, goal of the outreach, channel mix, and tone (Direct | Formal | Casual). Do not invent these. 2. Call apollo_emailer_campaigns_search with q_name set to the proposed name to avoid creating a duplicate. If a similarly-named sequence exists, surface it and ask before proceeding. 3. If the user wants a non-default sending schedule, call apollo_emailer_schedules_index and present matches. Otherwise omit emailer_schedule_id; the user's default will be applied.

DEFAULTS this tool will use unless the user says otherwise (Apollo best practices):

  • active: false. Always create inactive. The user must explicitly confirm before activation.
  • permissions: "team_can_use".
  • 4-6 steps. Default escalation: auto_email -> auto_email -> linkedin_step_view_profile ->

linkedin_step_message -> call.

  • 3-day intervals between email steps (wait_time: 3, wait_mode: "day"). First step wait_time: 0.
  • Email body length: 25-85 words. <= 50 words is recommended for cold outreach (correlates

with +23% reply rate).

  • Subject line: <= 9 words; concrete; no clickbait.
  • At most 3 A/B variants per step (additional emailer_touches in the same step).

AFTER creation:

  • The response will be large (full sequence with steps and touches). Echo only the sequence

id, name, and a short step summary back to the user — do not paste the full payload.

  • To activate the sequence, call apollo_emailer_campaigns_approve with the sequence id ONLY

after the user explicitly confirms sender email account, schedule, and step content. Activation will eventually send real emails from a real mailbox; never activate without explicit user approval.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (2 required, 7 optional)
Required
emailer_stepsarray

Ordered list of steps. Position is assigned automatically in array order (first item is step 1).

namestring

Human-readable sequence name shown in Apollo. Should be specific to the audience and goal. Example: 'Q2 SDR Outbound — Mid-market FinTech CTOs'

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

activeboolean

If true, sequence becomes active on creation; contacts added to it will start receiving emails as soon as the schedule allows. STRONGLY recommended to leave false and activate later via apollo_emailer_campaigns_approve only after the user reviews sender, schedule, and message bodies.

Default: False
emailer_schedule_idstring

Apollo ID of the EmailerSchedule that controls send-time windows (e.g. business hours, weekdays only). Must be the exact id value returned by apollo_emailer_schedules_index in this session. Never use an ID from memory, prior sessions, or assumptions. Omit to use the user's default schedule. Example: 6633baaece5fbd01c791d7ca

label_namesarray

Optional label names to apply to the sequence.

permissionsstring

Who in the team can use/view this sequence. Defaults to team_can_use.

Options:privateteam_can_viewteam_can_use
Default: team_can_use
sequence_by_exact_daytimeboolean

If true, each step has a fixed exact_datetime (one-off campaign tied to an event). If false (default), each step uses wait_time + wait_mode relative to enrollment. Use false for evergreen prospecting sequences.

Default: False

Update a Sequence

apollo_sequences_update
Full Description

Update an existing sequence's metadata, steps, touches, and templates in a single call.

DECLARATIVE DIFF SEMANTICS — the emailer_steps array you send is the FULL intended state of the sequence after this call:

  • A step with an id that matches an existing step → that step is UPDATED in place.
  • A step without an id → a NEW step is CREATED.
  • An existing step whose id is NOT in your payload → that step is DELETED.
  • The same rules apply per-touch within each step (touch.id present = update,

absent = create, missing existing = delete).

  • position is required on every step and must form a complete 1..N sequence in the

order you intend.

BEFORE calling this tool: 1. Fetch the current sequence (e.g. via the campaign-search response or by remembering the create response). You need each step's id and each touch's id to update them rather than create duplicates. 2. Show the user a clear before/after summary including which steps will be added, updated, removed, or reordered. Get explicit confirmation before calling. 3. If the sequence is currently active and the user has contacts enrolled, warn them that step changes can affect contacts mid-sequence.

EXAMPLES:

  • Edit step 2's body only: pass all existing steps with their ids; only step 2's

template body_html differs.

  • Add a LinkedIn step at position 3: send existing steps 1, 2 unchanged, then a new

step (no id) at position 3, then existing steps shifted to positions 4, 5, ...

  • Delete a step: omit it from the payload; positions of the remaining steps must

reflow as 1..N.

The response is large (full sequence with steps and touches). Echo only the sequence id and a short before/after step summary back to the user.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (2 required, 8 optional)
Required
emailer_stepsarray

FULL list of steps the sequence should have AFTER this update. Steps with `id` are updated, steps without `id` are created, existing steps not in this list are deleted. `position` is required on every step and must reflow as 1..N.

idstring

Apollo ID of the sequence to update. Must be the exact id value returned by apollo_emailer_campaigns_search or apollo_sequences_create in this session. Never use an ID from memory, prior sessions, or assumptions. Example: 66e9e215ece19801b219997f

Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

activeboolean

If true, activates the sequence as part of the update; if false, deactivates. Omit to leave unchanged. Activating sends real emails — get explicit user confirmation.

emailer_schedule_idstring

New sending schedule. Must be the exact id value returned by apollo_emailer_schedules_index in this session. Never use an ID from memory, prior sessions, or assumptions. Omit to leave unchanged.

label_namesarray

Replace the label set on the sequence.

namestring

New name for the sequence. Omit to leave unchanged.

permissionsstring

New sharing permission. Omit to leave unchanged.

Options:privateteam_can_viewteam_can_use
sequence_by_exact_daytimeboolean

Switch between interval-based and exact-datetime modes. Omit to leave unchanged.

View Credit Usage

apollo_usage_stats_credit_usage_stats
Full Description

Retrieve credit usage stats for the authenticated team — credits used, remaining, and reset windows for enrichment/people-search/email-reveal credits. Takes no input — scoped to the authenticated team automatically. For a single user's credit balance, use the Profile endpoint with include_credit_usage=true.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 2 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

Profile

apollo_users_api_profile
Full Description

Use the Profile endpoint to get the user's profile information (name, email, title, id) Set include_credit_usage to true to include credit usage information in the response. Credit Usage includes information like remaining credits, credits used etc.

Use this endpoint when the user asks about their remaining credits or credit usage.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 3 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

include_credit_usageboolean

Set to true to include credit usage information in the response. Default is false.

Default: False

Search Users

apollo_users_search
Full Description

List or search the users (teammates) in your team's Apollo account. Useful when you need a user's Apollo ID to set as owner/assignee on another resource (deal owner_id, task user_id, account/contact owner_id). For the authenticated user's own profile, use the Profile endpoint instead.

If this tool returns an unexpected, empty, or unhelpful result, call apollo_feedback_log to report it.

Parameters (0 required, 5 optional)
Optional
_conversation_refstring

On your first call in a conversation, generate a short random token (e.g. 8-16 lowercase alphanumeric chars) and reuse the exact same value on every subsequent call in the same conversation. This groups related tool calls for analytics and debugging. Do not include any user data, names, emails, or other sensitive information in the token.

_rationalestring

Describe the user's intent and why this tool was selected in general terms only. Do not include any specific field values, names, emails, domains, or other data from the request.

pageinteger

Page number to retrieve (1-indexed).

per_pageinteger

Number of results per page. Example: 25

q_keywordsstring

Free-text search across user name, email, and title.

Links

WebsitePrivacy PolicyTerms of Service