# How to connect Apollo to Grok Bot (paste one key, 48 tools) > Connect Apollo to Grok Bot with ClawLink: paste your Apollo key once and 48 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/grokbot/apollo Grok Bot runs on its own cloud computer, so most Apollo guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Apollo setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Apollo actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect apollo` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Apollo. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Apollo** — `npx -y @useclawlink/cli connect apollo`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect apollo # connect Apollo (browser OAuth) npx -y @useclawlink/cli actions apollo # list available actions npx -y @useclawlink/cli run apollo --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect apollo ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Use Apollo to add contacts to sequence and walk me through the result in plain English. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Apollo is connected in the dashboard, that agent calls the same 48 Apollo tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Apollo MCP for Grok Bot Looking for a Apollo MCP server for Grok Bot? ClawLink connects Apollo to Grok Bot and exposes 48 Apollo tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Apollo integration](https://claw-link.dev/openclaw/apollo) and the [Hermes Apollo integration](https://claw-link.dev/hermes/apollo) connect the same ClawLink account the same way. ## What the Grok Bot Apollo integration can do 48 Apollo tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 48. ### 30 of 48 Apollo tools for Grok Bot | Tool | What it does | |---|---| | **Add contacts to sequence** `apollo_add_contacts_to_sequence` | Enroll contacts into an Apollo email sequence | | **Create account** `apollo_create_account` | Create a company account in Apollo CRM | | **Create contact** `apollo_create_contact` | Create a new contact in Apollo CRM | | **Create deal** `apollo_create_deal` | Create a new deal in Apollo CRM | | **Get auth status** `apollo_get_auth_status` | Get the connected Apollo user and team context | | **Get deal** `apollo_get_deal` | Get an Apollo deal by ID | | **List deals** `apollo_list_deals` | List Apollo deals/opportunities | | **Organization enrichment** `apollo_organization_enrichment` | Enrich a company from Apollo's database | | **Organization search** `apollo_organization_search` | Search Apollo's organization database | | **People enrichment** `apollo_people_enrichment` | Enrich a person from Apollo's contact database | | **People search** `apollo_people_search` | Search Apollo's people database | | **Search accounts** `apollo_search_accounts` | Search company accounts in Apollo CRM | | **Search contacts** `apollo_search_contacts` | Search contacts already stored in Apollo CRM | | **Search sequences** `apollo_search_sequences` | Search Apollo email sequences | | **Search tasks** `apollo_search_tasks` | Search Apollo tasks | | **Bulk organization enrichment** `apollo_bulk_organization_enrichment` | Enriches data for up to 10 organizations simultaneously by providing a list of their base | | **Bulk people enrichment** `apollo_bulk_people_enrichment` | Use to enrich multiple person profiles simultaneously with comprehensive data from Apollo's | | **Get account** `apollo_get_account` | Retrieve detailed information about a specific account by its Apollo ID | | **Get contact** `apollo_get_contact` | Retrieves detailed information about a specific contact by its ID | | **Get labels** `apollo_get_labels` | Retrieves all labels from Apollo.io, used for organizing contacts and accounts | | **Get opportunity stages** `apollo_get_opportunity_stages` | Retrieves all configured opportunity (deal) stages from the Apollo.io account | | **Get organization** `apollo_get_organization` | Retrieves complete information about a specific organization by its Apollo ID | | **Get organization job postings** `apollo_get_organization_job_postings` | Retrieves paginated job postings for a specified organization by its ID, optionally filtering | | **Get typed custom fields** `apollo_get_typed_custom_fields` | Retrieves all typed custom field definitions available in the Apollo.io instance, detailing | | **List account stages** `apollo_list_account_stages` | Retrieves the IDs for all available account stages in your team's Apollo account | | **List contact stages** `apollo_list_contact_stages` | Retrieves all available contact stages from an Apollo account, including their unique IDs and | | **List email accounts** `apollo_list_email_accounts` | Retrieves all email accounts and their details for the authenticated user; takes no parameters | | **List fields** `apollo_list_fields` | Retrieves all field definitions from Apollo.io, including system fields and custom fields | | **List users** `apollo_list_users` | Retrieves a list of all users (teammates) associated with the Apollo account, supporting | | **Search calls** `apollo_search_calls` | Searches for call records in Apollo.io using filters like date range, duration, direction | ## Example prompts **Add Contacts To Sequence** > Use Apollo to add contacts to sequence and walk me through the result in plain English. **Create Account** > Create it in Apollo for me, then confirm the important fields before you finish. **Create Contact** > Create it in Apollo for me, then confirm the important fields before you finish. **Create Deal** > Create it in Apollo for me, then confirm the important fields before you finish. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Apollo working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Apollo API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Apollo account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Apollo. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Apollo actions to the runtime in a format your agent can reliably use. | 48 tools for Apollo are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Apollo to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Apollo in the browser, and the 48 tools above work from chat. There is no SDK and no config file, and the Apollo key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect Apollo from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Apollo tools Apollo tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Apollo call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Apollo returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Apollo has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Grok Bot Apollo integration? Yes. ClawLink is the fastest way to connect Grok Bot to Apollo: link your Apollo account once in the browser and Grok Bot can call the Apollo API through 48 ready-made tools — no custom code or token handling. ### How do I connect Apollo to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect apollo` to authorize Apollo. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files, and the Apollo key you paste is stored server-side instead of in your environment. ### How long does it take to connect Apollo to Grok Bot? About two minutes. Sign in, click Connect next to Apollo in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Apollo up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Apollo working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Connect HubSpot](https://claw-link.dev/grokbot/hubspot) — Manage contacts, deals, and pipelines - [CentralStationCRM](https://claw-link.dev/grokbot/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Grok Bot Salesforce integration](https://claw-link.dev/grokbot/salesforce) — Manage CRM data and workflows