Skip to content

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.

Actions and events

Apollo

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

Actions
70
Events
0
Composio catalog
API key
Global — no specific country
re-read from the vendor every 24 hours
www.apollo.io

70 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.

  1. Input

    A team member asks, in the conversation, for something that today requires opening Apollo — inside their area's space, with their login.

  2. 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, acts within permission; if the function is sensitive, it first shows the card and waits for Approve.
    3. 03Returns the result in the conversation and records who asked, which action was used and when.
  3. Result

    Apollo stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

Good to know

  • 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.

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; with the function set to ask for approval, 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.

  • Activate Sequence

    APOLLO_ACTIVATE_SEQUENCE

    Activate an inactive Apollo sequence and begin its scheduled outreach. Activation allows Apollo to send emails externally to enrolled contacts according to the sequence's configured steps and schedule. Reference:

  • Add Contacts to Sequence

    APOLLO_ADD_CONTACTS_TO_SEQUENCE

    Adds contacts to a specified Apollo email sequence and returns the contact details.

  • Add People to Prospects

    APOLLO_ADD_PEOPLE_TO_PROSPECTS

    Save Apollo person IDs returned by APOLLO_PEOPLE_SEARCH as persistent prospect contacts.

  • Archive Sequence

    APOLLO_ARCHIVE_SEQUENCE

    Archive an Apollo sequence, making it inactive and finishing all enrolled contacts. This lifecycle change can end outreach for every contact currently in the sequence.

  • 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.

  • Complete Apollo Task

    APOLLO_COMPLETE_TASK

    Permanently mark an Apollo task as completed and return its resulting state. Apollo provides no undo or reopen route, so confirm the task ID before calling.

  • 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.

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
70 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

Common doubts before connecting Apollo.

Next step

Connect Apollo and try it with your team.

Try it free with your team or book a demo: together we pick the Apollo functions to enable and show the first approved action, with fictitious data.