/apolloio

name: apolloio
description: |
  Apollo.io integration. Manage Persons, Organizations, Deals, Leads, Pipelines, Users and more. Use when the user wants to interact with Apollo.io data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: "Marketing Automation, Sales"

Apollo.io

Apollo.io is a sales intelligence and engagement platform. It helps sales, marketing, and recruiting teams to identify, contact, and close deals with targeted prospects. Users leverage Apollo.io to streamline outreach, automate tasks, and track performance metrics.

Official docs: https://developers.apollo.io/

Apollo.io Overview

• **Contact**
• **Contact Enrichment**
• **Account**
• **Email**
• **Engagement**
• **Email Engagement**
• **Task**
• **Call**
• **Opportunity**
• **User**
• **List**

Use action names and parameters as needed.

Working with Apollo.io

This skill uses the Membrane CLI to interact with Apollo.io. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to Apollo.io

Use `membrane connection ensure` to find or create a connection by app URL or domain:

membrane connection ensure "https://www.apollo.io" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

• **`READY`** — connection is fully set up. Skip to **Step 2**.
• **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
• `clientAction.type` — the kind of action needed:
• `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
• `"provide-input"` — more information is needed (e.g. which app to connect to).
• `clientAction.description` — human-readable explanation of what's needed.
• `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
• `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

• **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and `outputSchema` (what it returns).

Popular actions

| Name | Key | Description | |---|---|---| | List Users | list-users | Get a list of users in your Apollo team. | | List Deals | list-deals | List all deals in your Apollo account. | | List Account Stages | list-account-stages | Get a list of all account stages in your Apollo account. | | List Contact Stages | list-contact-stages | Get a list of all contact stages in your Apollo account. | | List Custom Fields | list-custom-fields | Get all custom fields defined in your Apollo account. | | List All Lists | list-all-lists | Get all lists (labels) in Apollo. | | Get Account | get-account | Retrieve an account by ID from your Apollo account. | | Get Contact | get-contact | Retrieve a contact by ID from your Apollo account. | | Get Deal | get-deal | Retrieve a deal by ID from your Apollo account. | | Create Contact | create-contact | Create a new contact in your Apollo account. | | Create Account | create-account | Create a new account (company) in your Apollo account. | | Create Deal | create-deal | Create a new deal/opportunity in your Apollo account. | | Create Task | create-task | Create a new task in your Apollo account. | | Update Account | update-account | Update an existing account in your Apollo account. | | Update Contact | update-contact | Update an existing contact in your Apollo account. | | Update Deal | update-deal | Update an existing deal in your Apollo account. | | Search Contacts | search-contacts | Search for contacts that have been added to