Who can connect Apollo for the company?

A company connection is installed by an administrator.

Can I connect Apollo just for myself?

Anyone can install a personal connection within the plan’s limit and use it in their own conversations.

Do I use my Apollo account or a company account?

Yours: Apollo requires an API key, and each person registers their own, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.

Does Skyller do everything on that action list?

The list is what the vendor offers. What the AI uses in your company is what the administrator turned on, for the groups they defined — Skyller never widens the connector's access.

Does an action in Apollo happen without anyone approving it?

Reads happen within permission. Write actions have a risk level; sensitive ones show a confirmation card before running and are recorded. The company adjusts the classification when needed.

Apollo does not show up in my company's catalog.

The administrator may have hidden the integration for your company, or the vendor may have discontinued it — in that case it leaves the catalog on the next synchronization, without deleting what was already connected. Talk to whoever administers Skyller in your company.

Integration · CRM and sales

Apollo in Skyller.

Connect Apollo to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.

Try it free Book a demo

Actions and events

Apollo

CRM and sales

Apollo provides CRM and lead generation capabilities, helping businesses discover contacts, manage outreach, and track sales pipelines for consistent customer relationship development

Actions: 48
Events: 0

Source: Composio catalog
Login: API key
Country: Global — no specific country
Actions list: re-read from the vendor every 24 hours
Official site: www.apollo.io

Description and action names are the ones the vendor publishes, in English; action descriptions are shown summarized. Skyller does not alter that content.

48 ACTIONS

published by the vendor; the company enables only the necessary ones

0 EVENTS

triggers the system can send, when the vendor offers them

API KEY

each person signs in with their own credential, encrypted

APPROVAL BY RISK

sensitive actions show a card before running

Live proof

One request, one query in Apollo and one approval.

The scene shows the path of a request; the exact actions depend on the functions your company enables in Apollo.

Input
A team member asks, in the conversation, for something that today requires opening Apollo — inside their area's space, with their login.
What Skyller does
1. 01Picks, among the enabled functions, a query action and looks the information up in Apollo with the person's own credential.
2. 02If the request requires writing something in Apollo, shows the card with what it is about to do and waits for Approve.
3. 03Returns the result in the conversation and records who asked, which action was used and when.
Result
Apollo stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

What this scene does not promise

The available actions are the ones the vendor publishes for Apollo; in your company only the functions turned on by the administrator are available.
If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
Being in this catalog does not mean being installed, with a valid login, working in your company.

Illustrative scene with fictitious data; no action is named because the choice depends on the functions your company enables.

Where this helps your work

Apollo inside the conversation where the work happens.

Three common situations for people who use Apollo every day. What Skyller does in each one depends on the functions your company turns on.

Preparing the meeting

“Summarize this customer's history before the call.”

The salesperson asks by name. Skyller queries Apollo through the read functions enabled for sales and builds the summary with the latest interactions and the deal stage.

CRM context in the conversation

Logging the follow-up

“Create the follow-up activity for Friday.”

Creating a record in Apollo is a write action: Skyller shows the card with the deal, the date and the note and waits for Approve.

Record with approval

Administering

“Reading, yes. Changing a proposal's value, no.”

The administrator turns on reading and activity creation for the team; changing values and deleting records stay off. Every call to Apollo goes in the record.

Function by function

Actions and events

What the vendor offers in Apollo.

Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.

Showing 12 of 48

Add Contacts to Sequence
APOLLO_ADD_CONTACTS_TO_SEQUENCE
Adds contacts to a specified Apollo email sequence and returns the contact details.
Bulk organization enrichment
APOLLO_BULK_ORGANIZATION_ENRICHMENT
Enriches data for up to 10 organizations simultaneously by providing a list of their base company domains (e.g., 'apollo.io', not 'www.apollo.io').
Bulk people enrichment
APOLLO_BULK_PEOPLE_ENRICHMENT
Use to enrich multiple person profiles simultaneously with comprehensive data from Apollo's database. Each call consumes Apollo credits; avoid re-enriching the same contacts.
Bulk update account stage
APOLLO_BULK_UPDATE_ACCOUNT_STAGE
Bulk updates the stage for specified existing Apollo.io accounts, moving them to a valid new account stage.
Create an Apollo account
APOLLO_CREATE_ACCOUNT
Creates a new account in Apollo.io; a new record is created even if a similar account exists, and provided owner_id or account_stage_id must be valid existing IDs.
Bulk create Apollo accounts
APOLLO_CREATE_BULK_ACCOUNTS
Creates multiple accounts in Apollo.io with a single API call (maximum 100 accounts per request). Use when creating multiple company records at once.
Bulk create Apollo contacts
APOLLO_CREATE_BULK_CONTACTS
Tool to bulk create multiple contacts in Apollo with a single API call. Use when you need to create multiple contacts efficiently. Supports up to 100 contacts per request with optional deduplication.
Create call record in Apollo
APOLLO_CREATE_CALL_RECORD
Tool to log call records in Apollo from external systems. Use when recording calls made through outside systems like Orum or Nooks; requires a master API key and cannot dial prospects directly.
Create Apollo contact
APOLLO_CREATE_CONTACT
Creates a new contact in Apollo.io; use account_id to link to an organization and contact_stage_id for sales stage.
Create custom field
APOLLO_CREATE_CUSTOM_FIELD
Creates a new custom field in Apollo.io for contacts, accounts, or opportunities. Use when you need to define additional data fields beyond Apollo's standard attributes.
Create Apollo deal
APOLLO_CREATE_DEAL
Creates a new sales opportunity (deal) in Apollo.io; all provided IDs (owner_id, account_id, opportunity_stage_id) must be valid existing Apollo identifiers.
Create Apollo Task
APOLLO_CREATE_TASK
Tool to create a single task in Apollo.io. Use when you need to add a new task to your team's Apollo account for a specific contact.

Before you start

What your company needs to use Apollo.

Login: Each person enters their own Apollo API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs: An administrator connects Apollo for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions: 48 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan: Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.

Questions from the people who decide