# How to connect HubSpot to Grok Bot (no API keys) > Connect HubSpot to Grok Bot with ClawLink in one click — 224 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/hubspot Grok Bot runs on its own cloud computer, so most HubSpot guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical HubSpot setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real HubSpot 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 hubspot` > 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 HubSpot. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect HubSpot** — `npx -y @useclawlink/cli connect hubspot`, 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 hubspot # connect HubSpot (browser OAuth) npx -y @useclawlink/cli actions hubspot # list available actions npx -y @useclawlink/cli run hubspot --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 hubspot ``` 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: > Create it in HubSpot for me, then confirm the important fields before you finish. ### 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 HubSpot is connected in the dashboard, that agent calls the same 224 HubSpot 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). ## HubSpot MCP for Grok Bot Looking for a HubSpot MCP server for Grok Bot? ClawLink connects HubSpot to Grok Bot and exposes 224 HubSpot 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 HubSpot integration](https://claw-link.dev/openclaw/hubspot) and the [Hermes HubSpot integration](https://claw-link.dev/hermes/hubspot) connect the same ClawLink account the same way. ## What the Grok Bot HubSpot integration can do 224 HubSpot 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 224. ### 30 of 224 HubSpot tools for Grok Bot | Tool | What it does | |---|---| | **Create company** `hubspot_create_company` | Create a HubSpot company | | **Create contact** `hubspot_create_contact` | Create a HubSpot contact | | **Create deal** `hubspot_create_deal` | Create a HubSpot deal | | **Create task** `hubspot_create_task` | Create a HubSpot task | | **Get company** `hubspot_get_company` | Get a HubSpot company by ID | | **Get deal** `hubspot_get_deal` | Get a HubSpot deal by ID | | **Get ticket** `hubspot_get_ticket` | Get a HubSpot ticket by ID | | **Read contact** `hubspot_read_contact` | Get a HubSpot contact by ID | | **Retrieve owners** `hubspot_retrieve_owners` | List HubSpot owners and users | | **Search companies** `hubspot_search_companies` | Search HubSpot companies | | **Search contacts by criteria** `hubspot_search_contacts_by_criteria` | Search HubSpot contacts | | **Search CRM objects by criteria** `hubspot_search_crm_objects_by_criteria` | Search HubSpot CRM objects | | **Search deals** `hubspot_search_deals` | Search HubSpot deals | | **Search tickets** `hubspot_search_tickets` | Search HubSpot tickets | | **Update contact** `hubspot_update_contact` | Update a HubSpot contact | | **Audit pipeline changes** `hubspot_audit_pipeline_changes` | Retrieves a reverse chronological audit log of all changes for a specific, existing HubSpot CRM | | **Batch read companies by properties** `hubspot_batch_read_companies_by_properties` | Batch-retrieves up to 100 HubSpot company records by their IDs in a single request | | **Fetch import error details** `hubspot_fetch_import_error_details` | Fetches a paginated list of read-only error details for a specific HubSpot CRM import | | **Fetch recording settings** `hubspot_fetch_recording_settings` | Fetches call recording settings for a specified, existing HubSpot calling extension app | | **Get AB email variation** `hubspot_get_ab_email_variation` | Retrieves the alternate variation of a specified A/B marketing email; the `emailId` must | | **Get account info** `hubspot_get_account_info` | Gets current HubSpot account info (email, hubId, user details) using access-token lookup | | **Get active imports list** `hubspot_get_active_imports_list` | Retrieves a list of currently active import jobs in HubSpot for monitoring ongoing data | | **Get aggregated statistic intervals** `hubspot_get_aggregated_statistic_intervals` | Retrieves aggregated statistics for marketing emails (e.g., send counts), grouped by specified | | **Get aggregated statistics** `hubspot_get_aggregated_statistics` | Retrieves aggregated statistics for marketing emails, optionally within an ISO8601 formatted | | **Get all marketing emails for a hub spot account** `hubspot_get_all_marketing_emails_for_a_hub_spot_account` | Fetches a list of marketing emails from a HubSpot account, with options for filtering, sorting | | **Get contact IDS** `hubspot_get_contact_ids` | Fetches a list of contact IDs for a specific HubSpot campaign based on interaction type | | **Get deals** `hubspot_get_deals` | Retrieves multiple HubSpot deals by their IDs in a single batch request | | **Get emails** `hubspot_get_emails` | Retrieves multiple HubSpot email engagement records by their IDs in a single batch request | | **Get import record information** `hubspot_get_import_record_information` | Retrieves a comprehensive summary of a specific HubSpot CRM import record by its `importId` | | **Get marketing email draft** `hubspot_get_marketing_email_draft` | Retrieves the draft version of a marketing email by its `emailId`; if no draft exists, returns | ## Example prompts **Create Company** > Create it in HubSpot for me, then confirm the important fields before you finish. **Create Contact** > Create it in HubSpot for me, then confirm the important fields before you finish. **Create Deal** > Create it in HubSpot for me, then confirm the important fields before you finish. **Create Task** > Create it in HubSpot for me, then confirm the important fields before you finish. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app 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 HubSpot working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a HubSpot app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect HubSpot through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for HubSpot. | 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 HubSpot actions to the runtime in a format your agent can reliably use. | 224 tools for HubSpot are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes HubSpot 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 HubSpot in the browser, and the 224 tools above work from chat. There is no SDK, no config file, and no API key handling. 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 HubSpot 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 HubSpot tools HubSpot 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 HubSpot 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. ### HubSpot 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. ### OAuth finished in the browser but the account is still missing Try reconnecting HubSpot and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot HubSpot integration? Yes. ClawLink is the fastest way to connect Grok Bot to HubSpot: link your HubSpot account once in the browser and Grok Bot can call the HubSpot API through 224 ready-made tools — no custom code or token handling. ### How do I connect HubSpot 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 hubspot` to authorize HubSpot. 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 or API keys to manage. ### How long does it take to connect HubSpot to Grok Bot? About two minutes. Sign in, click Connect next to HubSpot in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring HubSpot up myself? The alternative to ClawLink is usually manual OAuth app 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 HubSpot 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 CentralStationCRM](https://claw-link.dev/grokbot/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Connect Salesforce](https://claw-link.dev/grokbot/salesforce) — Manage CRM data and workflows - [Grok Bot RepairShopr integration](https://claw-link.dev/grokbot/repairshopr) — RepairShopr is a comprehensive repair shop management software designed to streamline operations, manage customer relationships, and enhance business efficiency.