Apollo API Key connector for AI agents

Tools your sales agent reaches for on Apollo, scoped per user.

CALL ANY TOOL

Search and enrich people and accounts, drive sequences, and log calls and tasks, each call on the user's own API key rather than a shared workspace credential.

apolloapikey_activate_sequence

Activate sequence

Activate (start) an inactive Sequence in your team's Apollo account by ID. Once activated, the sequence begins sending emails to its contacts on the configured schedule. The sequence must have at least one step configured before it can be activated. Requires a master API key. Returns the updated sequence object with its active state.

Parameters

Name

Type

Required

Description

sequence_id

string

Required

The Apollo ID for the sequence that you want to activate. To find sequence IDs, use the Search for Sequences endpoint and identify the id value for the sequence.

apolloapikey_add_contacts_to_sequence

Add contacts to sequence

Add contacts to an existing Sequence in your team's Apollo account, identified either by contact_ids or by label_names (at least one is required). Requires a sending email account (send_email_from_email_account_id). Supports overrides to allow adding contacts despite missing/unverified emails, recent job changes, membership in other sequences, or ownership restrictions. Requires a master API key. Returns the count and status of contacts added.

Parameters

Name

Type

Required

Description

send_email_from_email_account_id

string

Required

The Apollo ID for the email account used to send to contacts you add to the sequence. Use Get a List of Email Accounts to find the ID. A single ID is typical; Apollo also accepts a JSON array of IDs for multi-mailbox rotation.

sequence_id

string

Required

The Apollo ID for the sequence to which you want to add contacts. To find sequence IDs, use the Search for Sequences endpoint and identify the id value for the sequence.

add_if_in_queue

boolean

Optional

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

auto_unpause_at

string

Optional

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

contact_ids

array

Optional

The Apollo IDs for the contacts to add to the sequence. Use Search Contacts to find contact IDs. Either contact_ids or label_names must be provided.

contact_verification_skipped

boolean

Optional

Set to true to skip contact verification during the addition process.

contacts_without_ownership_permission

boolean

Optional

Set to true to add contacts even if you do not have ownership permission for them.

label_names

array

Optional

Alternative to contact_ids. Names of labels used to identify contacts to add to the sequence; all contacts carrying these labels are enrolled. Either contact_ids or label_names must be provided.

send_email_from_email_address

string

Optional

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

sequence_active_in_other_campaigns

boolean

Optional

Set to true to add contacts even if they are already active in other sequences. Does not differentiate between active and paused sequences.

sequence_finished_in_other_campaigns

boolean

Optional

Set to true to add contacts even if they have been marked as finished in another sequence.

sequence_job_change

boolean

Optional

Set to true to add contacts to the sequence even if they have recently changed jobs.

sequence_no_email

boolean

Optional

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

sequence_same_company_in_same_campaign

boolean

Optional

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

sequence_unverified_email

boolean

Optional

Set to true to add contacts to the sequence if they have an unverified email address.

status

string

Optional

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

user_id

string

Optional

The ID for the user in your team's Apollo account taking the action of adding contacts. Shown in the sequence's activity log. Use Get a List of Users to find IDs.

apolloapikey_add_records_to_list

List add records to

apolloapikey_archive_sequence

Archive sequence

apolloapikey_bulk_create_accounts

Bulk create accounts

apolloapikey_bulk_create_tasks

Bulk create tasks

apolloapikey_bulk_update_accounts

Bulk update accounts

apolloapikey_check_email_send_status

Check email send status

apolloapikey_complete_task

Complete task

apolloapikey_create_contact

Create contact

apolloapikey_create_email_draft

Create email draft

apolloapikey_enrich_contact

Enrich contact

apolloapikey_get_account

Get account

apolloapikey_get_contact

Get contact

apolloapikey_get_conversation_export

Export get conversation

apolloapikey_get_current_user

Get current user

apolloapikey_get_email_stats

Get email stats

apolloapikey_get_person

Get person

apolloapikey_list_contact_deals

List contact deals

apolloapikey_list_deals

List deals

apolloapikey_list_fields

List fields

apolloapikey_list_sequences

List sequences

apolloapikey_query_report

Query report

apolloapikey_search_accounts

Search accounts

apolloapikey_search_conversations

Search conversations

apolloapikey_search_news_articles

Search news articles

apolloapikey_update_account

Update account

apolloapikey_update_contact

Update contact

apolloapikey_update_contact_stages

Update contact stages

apolloapikey_update_sequence

Update sequence

Update an existing Sequence (emailer campaign) in your team's Apollo account by ID. Update sequence-level settings such as name, active state, schedule, and sending limits, as well as the sequence's steps and email touches. Passing emailer_steps will create, update, reorder, or remove steps and touches based on the IDs provided; steps that exist on the sequence but are not present in the array are removed. Requires a master API key. Returns the updated sequence object.

Parameters

Name

Type

Required

Description

sequence_id

string

Required

The Apollo ID for the sequence that you want to update. To find sequence IDs, use the Search for Sequences endpoint and identify the id value for the sequence.

active

boolean

Optional

Turn the sequence on (true) or off (false). When set to true, Apollo resumes scheduling for the sequence; when set to false, pending work is paused.

bcc_emails

string

Optional

Comma-separated list of email addresses to BCC on emails sent from this sequence.

cc_emails

string

Optional

Comma-separated list of email addresses to CC on emails sent from this sequence.

creation_type

string

Optional

The creation type for the sequence. A draft sequence is automatically promoted to new (or ai_assistant) when steps are added.

emailer_schedule_id

string

Optional

Attach a sending schedule to the sequence. Must reference a non-empty schedule that belongs to your team. Example: 6095a710bd01d100a506d4af

emailer_steps

array

Optional

The ordered list of steps in the sequence. Include a step's id to update it; omit id to create a new step. Steps that exist on the sequence but are not present in this array are removed. Each step object supports: id, position (1-based), type, wait_mode, wait_time, auto_skip_in_x_days, and emailer_touches (array of {id, status (to_be_reviewed/approved), attachment_ids, emailer_template: {subject, body_html}, generation_options, generation_tone}). Include a touch's id to update it; omit to create a new touch.

label_names

array

Optional

Replace the labels (folders) this sequence belongs to. Passing new values overwrites the existing labels.

max_emails_per_day

integer

Optional

Maximum number of emails that can be sent per day for this sequence.

name

string

Optional

Update the name of the sequence. Example: New outbound sequence

permissions

string

Optional

Update who can access the sequence. One of: team_can_use, team_can_view, private. Example: team_can_use

same_account_reply_delay_days

integer

Optional

Number of days to wait before contacting another person at the same account after a reply is received.

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Apollo (API Key) tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["apolloapikey"], toolNames: [
    "apolloapikey_activate_sequence",
    "apolloapikey_add_contacts_to_sequence",
    "apolloapikey_add_records_to_list"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Is the Salesforce sync healthy?" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["apolloapikey"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Which data sources are connected?" }],
  tools,
});

// Execute the tool call with the user's vaulted Apollo (API Key) credential
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["apolloapikey"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Pull open Zendesk tickets created this week." }],
  tools,
});

// Tool call runs with the user's vaulted Apollo (API Key) credential
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["apolloapikey"] }, pageSize: 100,
});

const agent = new Agent({
  name: "apolloapikey_agent",
  model: "gemini-2.5-pro",
  instruction: "Work with Apollo (API Key) for the signed-in user.",
  tools,
});

await agent.run("What auth does the Shopify connector need?");

Try these prompts

Paste any prompt into your agent to get started.

Prospecting

Copy the prompt

Copied

Who at this account should we be talking to?

Copy the prompt

Copied

Enrich these domains and return verified contacts.

Copy the prompt

Copied

Search for RevOps leaders at Series B companies.

Sequences

Copy the prompt

Copied

Add these contacts to my outbound sequence.

Copy the prompt

Copied

Which sequences are active and how are they performing?

Copy the prompt

Copied

Remove this contact from every sequence.

Pipeline hygiene

Copy the prompt

Copied

List the accounts with no activity in 30 days.

Copy the prompt

Copied

Create a task to follow up on this opportunity.

Copy the prompt

Copied

Log the outcome of this call.

SEE HOW AUTH WORKS

Your users connect their Apollo API key once. It stays vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Apollo (API Key)

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Apollo (API Key)

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Apollo (API Key)

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Apollo (API Key)

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

GTM and RevOps Teams

Outbound prospecting agent

Searches Apollo for prospects matching your ICP, scores and ranks them, drafts personalized outreach in Gmail, and logs every send to Google Sheets. Mail goes out as the rep, not from a shared inbox.

GTM and RevOps Teams

CRM AI agent

Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.

GTM and RevOps Teams

Deal intelligence agent

Pulls recent Gong calls, scores deal risk with an LLM, cross-references the record in Attio, and DMs each owner their at-risk deals in Slack. Every read is scoped to that rep's own access.

GTM and RevOps Teams

Sales call prep agent

Reads tomorrow's calls from Google Calendar, mines past Granola notes and Attio history for context, and delivers each rep a prep brief in Slack, scoped to the calls that rep actually owns.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Apollo (API Key) token looks fine in a demo. In production every action looks like one service account, and you cannot tell who wired a source or ran a query. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Apollo (API Key) today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

How is this different from the OAuth Apollo connector?

Same Apollo, different credential. This one uses each user's API key and exposes apolloapikey_* tools; the OAuth connector uses a user grant and exposes apollo_* tools. Pick the one that matches how your team authenticates.

Does each user need their own key?

That is the point of this connector. A key per user keeps enrichment and sequence activity attributed, where a single shared workspace key makes every action look identical in the audit trail.

How many tools are available?

80 across people, accounts, sequences, calls, tasks, and enrichment. The page shows a representative 30; the docs list all of them.

Can I keep the agent out of sequence writes?

Yes. Scope the connection to the search and enrichment tools; sequence and task writes stay unavailable, enforced before the API call.

How is the key stored?

Encrypted per tenant with AES-256, resolved at request time, never placed in LLM context.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit