Hubspot
Wire an agent to HubSpot CRM records, deals, tickets, and marketing workflows through Membrane’s authenticated CLI.
Overview
HubSpot is an agent skill for the Build phase that connects agents to HubSpot CRM and marketing data through the Membrane CLI with managed authentication.
Install
npx skills add https://github.com/membranedev/application-skills --skill hubspotWhat is this skill?
- HubSpot CRM entities: contacts (email), companies, deals, and tickets
- Membrane CLI handles OAuth, tenant login, and credential refresh
- npm global install: @membranehq/cli
- Official HubSpot developer API alignment via Membrane actions
- Free-tier Membrane account supported for auth plumbing
- Membrane CLI package @membranehq/cli
- Core objects: Contact, Company, Deal, Ticket
Adoption & trust: 815 installs on skills.sh; 178 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need HubSpot contacts, deals, or tickets in your agent workflow but do not want to maintain OAuth and credential refresh yourself.
Who is it for?
Solo builders adding CRM or marketing automation to a SaaS or agent product using Membrane’s HubSpot connector.
Skip if: Projects that forbid external SaaS auth, lack network access, or need HubSpot-only custom apps without Membrane.
When should I use this skill?
User wants to interact with HubSpot data, CRM records, or marketing automation via Membrane.
What do I get? / Deliverables
Authenticated Membrane actions run against HubSpot so your agent can manage CRM records and workflows with CLI-driven integration steps.
- Configured Membrane tenant login
- HubSpot actions executed for requested CRM or workflow tasks
Recommended Skills
Journey fit
HubSpot access is implemented while building product features that sync leads, CRM objects, and automation—not a launch-only SEO task. Integrations is the correct shelf for third-party CRM and marketing APIs orchestrated via Membrane.
How it compares
Integration skill via Membrane CLI—not a hosted MCP server catalog entry; pair with your app’s business logic in Build.
Common Questions / FAQ
Who is hubspot for?
Indie builders and small teams using coding agents who need programmatic HubSpot CRM and marketing automation access through Membrane.
When should I use hubspot?
In Build when syncing leads, updating deals or tickets, or automating marketing workflows while implementing backend or agent features.
Is hubspot safe to install?
It requires network login to Membrane and HubSpot and installs a global npm CLI—treat credentials as sensitive and review Security Audits on this Prism page before use.
SKILL.md
READMESKILL.md - Hubspot
# HubSpot HubSpot is a CRM and marketing automation platform that helps businesses manage their sales, marketing, and customer service efforts. It's used by marketing and sales teams to attract leads, nurture them into customers, and provide customer support. Official docs: https://developers.hubspot.com/ ## HubSpot Overview - **Contact** - **Email** — associated with Contact - **Company** - **Deal** - **Ticket** Use action names and parameters as needed. ## Working with HubSpot This skill uses the Membrane CLI to interact with HubSpot. 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: ```bash npm install -g @membranehq/cli@latest ``` ### Authentication ```bash 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: ```bash 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 HubSpot Use `membrane connection ensure` to find or create a connection by app URL or domain: ```bash membrane connection ensure "https://www.hubspot.com/" --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: ```bash 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