Apollo MCP

Create a single task in Apollo. A task is an action item (call, email, LinkedIn step, or generic action_item) assigned to a user and tied to a contact, account, or opportunity. Requires user_id and type, plus at least one of contact_id, account_id, or opportunity_id.

Skip a single task without performing it. For a task that belongs to a sequence, skipping it moves the contact past this step. Tasks controlled by a workflow approval cannot be skipped.

Search the tasks in your team's Apollo account. Returns a paginated list of tasks matching the supplied filters. All filters AND together; omit a filter to ignore it. With no task_status filter this returns only scheduled (open) tasks.

Report when a previous Apollo tool returned an unexpected, empty, or unhelpful result. 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.

Edit an existing task in place : change its title, note, priority, due date, assignee, or the message body (subject / body_text) for email and LinkedIn-step tasks. Use this instead of skipping and recreating a task. Only scheduled (open) tasks can be fully edited; for completed or skipped tasks only note, priority, and contact_id are applied.

List your team's custom or system fields so you can set them on accounts or contacts. Call this before the Create/Update/Bulk Create tools for accounts or contacts whenever you need to set a custom field. Each field is returned with its id, label, type, modality (account, contact, etc.), source, and : for picklist/multipicklist fields : its allowed options as picklist_values: [{"id": ..., "name": ...}]. The option name is what you send when setting a record's value; the option id is what you resend to the fields update tool when changing the field's option set. Pass a field's id exactly as returned as the key in the typed_custom_fields object on create/update tools, e.g. typed_custom_fields: {"": ""}. For picklist fields send an allowed option name; for multipicklist fields send an array of names.

Create a new, empty Apollo list (label) for your team. In Apollo terminology, a list is a named, saved group of records; supply the modality to choose whether it is a list of contacts or accounts. List names must be unique per modality within your team : creating a list whose name already exists for that modality returns an error (use apollo_labels_update to rename an existing list instead). To add records to a list use apollo_labels_add_entity_ids_to_label_names, which will also create the list on the fly if the name does not yet exist. No deduplication is applied beyond the per-modality name-uniqueness check, so check apollo_labels_index first if you may be recreating an existing list. The response includes the new list's id and its app_url (a shareable deep link to the list in the Apollo web app) : surface app_url to the user.

List the Apollo lists (also called labels) that belong to your team. A list is a named, saved group of contacts or accounts. Each returned list includes its id, name, modality (contacts or accounts), cached record count, and app_url : a shareable deep link to the list in the Apollo web app (format: https://app.apollo.io/#/lists/); surface app_url to the user when they want to view or share a list. Call this first to discover existing lists and their ids before renaming a list (apollo_labels_update) or adding/removing records (apollo_labels_add_entity_ids_to_label_names, apollo_labels_remove_entity_ids_from_label_names).

Rename an existing Apollo list (label). Pass the list id and the new name. Use List Lists (apollo_labels_index) to discover the id of the list you want to rename. The new name must be unique per modality within your team : reusing an existing name for that modality returns an error. This tool only renames a list; it does not add or remove records (use apollo_labels_add_entity_ids_to_label_names / apollo_labels_remove_entity_ids_from_label_names) and it cannot delete a list.

Enrich data for a single person in the Apollo database. Provide identifying details such as name, email, domain, or LinkedIn URL to find a match. Returns enriched profile data including job title, employer, and contact details. Costs 1 credit per matched person; 0 credits if not found.

Add a new account (company) to your team's Apollo database. Apollo does not deduplicate on create : if a matching account already exists by name or domain, a new record is created; use the Update Account tool to modify existing accounts.

Mark a single task as completed. For a task that belongs to a sequence, completing it advances the contact to the next step of that sequence. Complete a task only after the real-world action it describes (sending the LinkedIn message, placing the call, etc.) has actually been performed.

Update an existing account (company) in your team's Apollo database. Requires the Apollo account ID; use Create Account to add new accounts that do not yet exist.

Create a new contact in your team's Apollo account. Apollo automatically prevents duplicates : if a matching contact is found by email or other details, that existing contact is updated instead of creating a new one.

Search for contacts that have been added to your team's Apollo account. Returns enriched contact records matching the given keywords and filters.

Update an existing contact in your team's Apollo account. Requires the Apollo contact ID; use Search Contacts to find the ID, and Create Contact to add new contacts.

Create a new multi-step outreach sequence in the user's Apollo workspace. A sequence has a name, an optional sending schedule, and an ordered list of steps. Each step can be an auto email, manual email, call, action item, or LinkedIn step. Sequences are created inactive by default and must be explicitly activated.

Update an existing sequence's metadata, steps, touches, and templates in a single call. Uses declarative diff semantics: the emailer_steps array you send is the full intended state after the update. Steps with an id are updated, steps without an id are created, and existing steps not included in the payload are deleted.

Search conversations for the current team, sorted by start time descending. Use this to discover conversation IDs before calling apollo_conversations_get_transcript, apollo_conversations_get_insights, or apollo_conversations_get_recording_links. Returns a paginated list where each conversation includes: id, topic, start_time (ISO 8601), duration (seconds), state, host_id, participant_count, has_transcript, and source. Filters available: user_id (host), state, date_range (start_time min/max), q_keywords (topic), source. Use source=phone_call for only phone call recordings, source=meeting for video meeting recordings. Deleted and failed conversations are excluded regardless of filters. Use page (1-indexed, default 1) and per_page (default 20, max 50) for pagination; increment page while has_more is true to walk through all results. If multiple conversations match, present topic, start_time, and source for each match and ask the user to confirm which conversation they mean before calling get_transcript, get_insights, or get_recording_links : do not assume or pick one on their behalf.

Enrich data for 1 company using the Organization Enrichment endpoint. Enriched data includes industry information, revenue, employee counts, funding round details, and corporate phone numbers and locations. Credit cost: 1 credit if found, 0 credits if not found.

Create many tasks in a single call. Pass an array of task attribute objects under tasks_attributes. Each object requires user_id, type, and at least one of contact_id, account_id, or opportunity_id. No deduplication is applied.

Enrich data for up to 10 people in a single call. Pass an array of person objects under details. Each object accepts identifying fields such as first name, last name, email, organization name, domain, or LinkedIn URL. Costs 1 credit per matched person; 0 credits for unmatched entries.

Create multiple accounts (companies) in a single call by passing an array of account objects. No deduplication is applied : each object becomes a new record even if it matches an existing account by name or domain; review the array carefully before submitting.

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 and credits used. Use this endpoint when the user asks about their remaining credits or credit usage. Set include_waterfall_capability to true to learn whether the team has waterfall email and/or phone enrichment enabled; check this before offering or running waterfall enrichment elsewhere.

Create multiple contacts in a single call by passing an array of contact objects. Apollo automatically deduplicates : any object matching an existing contact by email or other details updates that record instead of creating a new one.

Fetch the team's full Context Center : the Ideal Customer Profile (ICP) and all product profiles Apollo uses to personalize AI-generated messaging. Returns the team's current Context Center including drafts that have not yet been approved. Always call this first before editing the profile or a product, so you read the current values and send only the fields that change. Returns a 404 if the team has no Context Center yet : in that case use apollo_context_center_create_profile to set one up.

Search for companies in the Apollo database using the Organization Search endpoint. Several filters are available to narrow your search. Credit cost: 1 credit per request that returns at least one result. Must confirm with user before calling.

Poll for the result of an asynchronous Apollo enrichment request: either a phone-number reveal started by apollo_people_match or apollo_people_bulk_match with reveal_phone_number=true, or a waterfall enrichment (email and/or phone) started with run_waterfall_email=true and/or run_waterfall_phone=true. Pass the top-level request_id returned by that call (not any nested id). Polling: a not-yet-ready result returns 404 with error_code "result_pending" and a retry_after_seconds value : wait that long and poll again. For a standard phone reveal (no waterfall), give up after ~5 attempts (~50s total). For waterfall enrichment, keep polling for up to ~3 minutes before giving up (waterfall can legitimately take much longer). Bulk requests take longer than single requests for either kind, so lean toward the longer end. Terminal responses : never retry these: 200 status=success (result ready; phone numbers are grouped by type : mobile_phone, direct_phone, corporate_phone, home_phone, other_phone; waterfall email results also carry an emails array per person with email, email_status_cd, position, and vendor_validation_statuses; results are available for 30 days); 200 status=failed (enrichment failed on Apollo's side, no credits charged); 404 error_code=request_id_unknown (the id was never issued or was mistyped : do not retry, do not tell the user to try again later); 410 error_code=request_id_expired (the result aged out past the 30-day retention window : start a fresh enrichment request instead); 400 error_code=invalid_request_id (malformed id). When status=success but every phone array (or the emails field) is empty, tell the user nothing was found on file; only say "no credits were charged" when the response's credits_consumed is 0. DO-NOT-CALL (MANDATORY): each returned phone number carries a dnc_status_cd (found / not_found / pending : only "found" means it is Do-Not-Call listed). When any number has dnc_status_cd="found", you MUST surface a prominent Do Not Call warning immediately next to that number (never a footnote), noting it may implicate the TCPA and other telemarketing regulations, and recommending against dialing it absent a separate legal basis. ANTI-FABRICATION: never fabricate, guess, or substitute a phone number or email address from training data, web knowledge, or any non-Apollo source : only report numbers and addresses present in this response.

Create a draft email message for a contact. The draft is saved but NOT sent until apollo_emailer_messages_send_now is called with the returned emailer_message id. Before calling, look up the user's mailboxes (apollo_email_accounts_index) to identify the default sender mailbox, and confirm the recipient, subject, and body preview with the user. The recipient defaults to the contact's own email; pass a recipients array (each entry with email and recipient_type_cd of to/cc/bcc) to override or add recipients, including non-contact addresses : this changes who receives the email but not the contact it is associated with.