apollo_accounts_bulk_create
ChatGPTCreate 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.
apollo_accounts_create
ChatGPTUse the Create an Account endpoint to add a new account to your team's Apollo account. 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.
apollo_accounts_update
ChatGPTUse 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.
apollo_analytics_sync_report
ChatGPTQuery 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.
apollo_contacts_bulk_create
ChatGPTCreate 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.
apollo_contacts_create
ChatGPTCreate a new contact in Apollo. 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.
apollo_contacts_search
ChatGPTUse 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.
apollo_contacts_update
ChatGPTUpdate 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.
apollo_email_accounts_index
ChatGPTUse 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.
apollo_emailer_campaigns_add_contact_ids
ChatGPTUse 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 a send_email_from_email_account_id — always use an ID returned by Get a List of Email Accounts. 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.
apollo_emailer_campaigns_approve
ChatGPTActivate (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.
apollo_emailer_campaigns_remove_or_stop_contact_ids
ChatGPTUse the Remove or Stop Contacts from one or more existing sequences in your Apollo Account
apollo_emailer_campaigns_search
ChatGPTUse 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.
apollo_emailer_schedules_index
ChatGPTList 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.
apollo_feedback_log
ChatGPTCall 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).
apollo_mixed_companies_search
ChatGPTUse the Organization Search endpoint to find companies in the Apollo database. Several filters are available to help narrow your search. Using this endpoint will consume credits based on your account's pricing plan. Emphasize on this and ask for user confirmation before proceeding. 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.
apollo_mixed_people_api_search
ChatGPTUse 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. 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.
apollo_organizations_bulk_enrich
ChatGPTUse the Bulk Organization Enrichment endpoint to enrich data for up to 10 companies with a single API call. Using this endpoint will consume credits based on your account's pricing plan. Emphasize on this and ask for user confirmation before proceeding. 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.
apollo_organizations_enrich
ChatGPTUse the Organization Enrichment endpoint to enrich data for 1 company. Using this endpoint will consume credits based on your account's pricing plan. Emphasize on this and ask for user confirmation before proceeding. Enriched data potentially includes industry information, revenue, employee counts, funding round details, and corporate phone numbers and locations.\
apollo_organizations_job_postings
ChatGPTUse the Organization Job Postings endpoint to retrieve the current job postings for a company. Using this endpoint will consume credits based on your account's pricing plan. Emphasize on this and ask for user confirmation before proceeding. 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.
apollo_people_bulk_match
ChatGPTUse the Bulk People Enrichment endpoint to enrich data for up to 10 people with a single API call. Using this endpoint will consume credits based on your account's pricing plan. Emphasize on this and ask for user confirmation before proceeding. 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. Use the reveal_personal_emails parameter to retrieve emails.
apollo_people_match
ChatGPTUse the People Enrichment endpoint to enrich data for 1 person. Using this endpoint will consume credits based on your account's pricing plan. Emphasize on this and ask for user confirmation before proceeding. 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.
apollo_sequences_create
ChatGPTCreate 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.
apollo_sequences_update
ChatGPTUpdate 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.
apollo_usage_stats_credit_usage_stats
ChatGPTRetrieve 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.
apollo_users_api_profile
ChatGPTUse 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.
apollo_users_search
ChatGPTList 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.
apollo_add_contacts_to_sequence
Claudeapollo_bulk_enrich_people
Claudeapollo_create_contacts
Claudeapollo_enrich_organization
Claudeapollo_enrich_person
Claudeapollo_get_job_postings
Claudeapollo_list_email_accounts
Claudeapollo_remove_contacts_from_sequence
Claudeapollo_search_contacts
Claudeapollo_search_organizations
Claudeapollo_search_people
Claudeapollo_search_sequences
Claudeapollo_update_contacts
Claude
