HubSpot is a common CRM target. Actionist agents can read contacts and deals, log activity, draft follow-ups, and enrich leads with web research before they hit a human’s queue.Documentation Index
Fetch the complete documentation index at: https://learn.actionist.ai/llms.txt
Use this file to discover all available pages before exploring further.
What you can do
- Read & write contacts, companies, deals, tickets.
- Log activity — calls, emails, meetings, tasks.
- Enrich records using web research or LinkedIn data.
- Trigger workflows from form submissions, lifecycle stage changes, or deal stage moves.
Setup
Install the HubSpot MCP server
Integrations → Discover → HubSpot → Install. Authenticate via OAuth (recommended) or a private app token.
Pick the right scopes
Read-only for research agents, full read/write only for the CRM agent that should mutate records. Less surface = less risk.
Common workflows
- Lead enrichment — when a new contact lands from a web form, an agent looks up the company, finds the most senior contact mentioned in recent news, and appends a 3-bullet brief to the contact record.
- Follow-up drafter — after a Calendly meeting, an agent reads the recording transcript and drafts a follow-up email saved to the contact’s activity log (not sent — human approves).
- Stale deal nudger — every Monday, list deals in the “Proposal” stage with no activity in 14 days. Post the list to
#sales. - Daily activity digest — summarize yesterday’s logged activity by sales rep for the manager’s standup.
Limits & gotchas
- API quotas are tier-dependent. Starter is 100 calls / 10 seconds per private app token.
- Custom properties need to be created in HubSpot first — Actionist can read/write them but not create the schema.
- Workflow vs sequence vs sequence enrolment. Different APIs, different scopes. Read the HubSpot docs once before scripting.
- Deal pipeline names aren’t stable. Always use IDs, not labels.