← Back to Skills Marketplace
7469
Downloads
5
Stars
0
Active Installs
16
Versions
Install in OpenClaw
/install apollo-api
Description
Apollo.io API integration with managed OAuth. Search and enrich people and companies, manage contacts and accounts. Use this skill when users want to prospect, enrich leads, or manage sales data. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn an Apollo connection into automation, in the order they are used: the connection (the first step), a hosted function that runs an Apollo action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Apollo examples; they add no Apollo capability - Apollo is not an event source, a trigger cannot read Apollo data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install only if you intend to connect Apollo through Maton. Review OAuth scopes, prefer read-only access where possible, confirm every write or sequence action before it runs, and be especially careful with enrichment or trigger destinations because they can expose personal or business data.
Capability Assessment
Credentials
The skill uses network access, OAuth credentials, and optional API-key fallback, which are proportionate for an API integration but involve business and personal data held in Apollo.
Install Mechanism
The skill instructs users to install a pinned Maton CLI via npm or Homebrew and mentions optional SDK packages; this is disclosed and coherent with the integration, but users should verify they want Maton installed and authenticated.
Instruction Scope
Runtime instructions are scoped to user-approved Apollo and Maton operations, default to read/list actions, require confirmation for writes and new connections, and treat external API data as untrusted.
Persistence & Privilege
OAuth tokens are stored in the OS credential store and Maton functions/triggers can create persistent automation, but the artifact repeatedly requires explicit approval, narrow scoping, private functions, DENY_ALL network policy by default, and destination disclosure.
Purpose & Capability
The documented capabilities match the stated purpose: Apollo API access through Maton for prospecting, enrichment, contacts, accounts, sequences, and email-message search, with write operations called out as requiring confirmation.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install apollo-api - After installation, invoke the skill by name or use
/apollo-api - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.6
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.5
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.4
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.3
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.2
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.1
Reword the webhook warning and separate CLI vs SDK credential guidance to address SkillSpector findings (P3/E1 exfiltration-phrasing false positive, SDI-4 auth inconsistency)
v1.2.0
Appendix drops the raw curl example; SkillSpector 2.11 static findings addressed across the reference; HTTP blocks replaced with maton api
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.7
- Removed the file: skill-card.md
- No changes to functionality or API usage; documentation and interface remain unchanged.
v1.0.6
- Changed all endpoint and connection management URLs from gateway.maton.ai/ctrl.maton.ai to api.maton.ai
- Added security & permissions section specifying required user approval for all write operations
- Updated code examples and documentation to use new api.maton.ai URLs
- Clarified connection management workflows and required headers
- Removed LICENSE.txt file
v1.0.5
- Added a new clawdbot metadata section specifying emoji and required environment variable (MATON_API_KEY).
v1.0.4
No changes detected in this version.
- No updates or modifications were made to the skill files.
v1.0.3
- Replaced all bash/curl connection management examples with native Python equivalents for easier scripting and cross-platform compatibility.
- Updated the Quick Start and connection management sections with Python examples using `urllib.request` and `os`.
- No API changes or new endpoints; documentation/examples updated only.
v1.0.2
- Added a note in the description recommending the api-gateway skill for other third party apps.
- Updated all example curl commands to use environment variable syntax ($MATON_API_KEY) for consistency.
- Added important notes about using curl with glob parsing (-g option) and issues with environment variable expansion when piping output to commands like jq.
v1.0.1
- Added instructions for specifying which Apollo connection to use via the Maton-Connection header.
- Clarified the API base URL format and usage of {native-api-path}.
- Enhanced the Get Connection response example with additional metadata fields.
- Updated authentication instructions to specify that signing up may be necessary to obtain an API key.
- Minor improvements and clarifications throughout the documentation for accuracy and completeness.
v1.0.0
Apollo API skill initial release:
- Integrates Apollo.io API with managed OAuth via Maton gateway.
- Supports searching and enriching people and companies.
- Enables management of contacts, accounts, and sales sequences.
- OAuth connection management and API key setup instructions included.
- Provides comprehensive usage and code examples for curl, JavaScript, and Python.
- Details error handling, pagination, search filters, and common endpoints.
Metadata
Frequently Asked Questions
What is Apollo?
Apollo.io API integration with managed OAuth. Search and enrich people and companies, manage contacts and accounts. Use this skill when users want to prospect, enrich leads, or manage sales data. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn an Apollo connection into automation, in the order they are used: the connection (the first step), a hosted function that runs an Apollo action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Apollo examples; they add no Apollo capability - Apollo is not an event source, a trigger cannot read Apollo data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 7469 downloads so far.
How do I install Apollo?
Run "/install apollo-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Apollo free?
Yes, Apollo is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Apollo support?
Apollo is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Apollo?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.6.
More Skills