Your CRM, on autopilot.
HubSpot holds your pipeline, your contact graph, and your support queue — but keeping it clean still takes someone’s time. Connect once and hand that work to an agent: contacts logged, deals created, stale records flagged, pipeline summaries written — while you focus on closing.
Watch a call become a clean CRM record.
A call ends. Without any manual entry, the agent logs the outcome, updates the contact, and advances the deal stage. Pick a step to see what the agent does at each point.
firstname, lastname, email, lifecyclestage.Three recipes Dario runs every week.
Each card is a complete agent workflow — trigger, tools called, output. Copy the pattern and tune the instructions to your pipeline.
What agents can do.
Each object group is scoped individually — grant read-only to reporting agents and read + write only to agents that need to make changes.
List up to 100 contacts per call, or fetch a single contact by ID. Default fields include firstname, lastname, email, phone, company, and lifecyclestage.
List open deals with stage and close date, or create a deal with a name, amount, and pipeline stage. Default stage on create: appointmentscheduled.
List companies, fetch a record by ID with domain and location data, or create a new company with name, domain, and industry.
List open tickets, fetch details including pipeline stage and priority, or create a ticket with subject, content, stage, and priority (LOW, MEDIUM, HIGH). Default stage “1” maps to New in HubSpot’s built-in Support Pipeline.
Connect HubSpot.
HubSpot connects via OAuth 2.0. You choose which service groups to enable before the OAuth handshake, so the granted scopes match exactly what your agents need.
Open Integrations
Choose your services
Authorize via OAuth
app.hubspot.com. Sign in and grant the requested crm.objects.* scopes for the services you selected.Tools by object group.
Each accordion covers the tools in that group, the default properties returned, and a concrete example of what an agent can do with them.
Contacts (2 tools — read only)
Contacts (2 tools — read only)
contacts:list — returns up to 100 contacts per call (default 25). Default fields: firstname, lastname, email, phone. Use this to pull today’s new leads or build a pre-meeting briefing.contacts:get — fetch a single contact by ID. Default fields expand to include company and lifecyclestage. Use this when an agent needs the full picture on one person before drafting an outreach message.Example: “List the 10 most recently added contacts” — agent calls contacts:list with limit: 10 and formats the results as a Slack digest.Deals (2 tools — read + write)
Deals (2 tools — read + write)
deals:list — list deals with default fields dealname, amount, dealstage, closedate. Cap at 100 per call. Good for pipeline reviews and stale-deal detection.deals:create — create a deal with a required dealname, optional amount, and dealstage (default appointmentscheduled). Deal stage IDs are account-specific — verify the correct strings in your HubSpot pipeline settings before using custom stages.Example: “Create a deal called Q3 Expansion for $15,000” — agent calls deals:create with dealname: "Q3 Expansion", amount: 15000.Companies (3 tools — read + write)
Companies (3 tools — read + write)
companies:list — list companies with name, domain, industry, numberofemployees. Useful for account mapping or enrichment runs.companies:get — fetch a single company by ID; adds phone, city, and country to the default field set. Use before a call to pull the full account profile.companies:create — create a company record with a required name, optional domain and industry. Check whether the account already exists first — HubSpot’s CRM v3 API does not deduplicate automatically.Example: “Look up Acme Corp by company ID and return their industry and headcount” — agent calls companies:get.Tickets (3 tools — read + write)
Tickets (3 tools — read + write)
tickets:list — list tickets with default fields subject, content, hs_pipeline_stage, hs_ticket_priority, createdate. Good for daily support queue reviews.tickets:get — fetch a ticket by ID; also returns hs_pipeline, hs_lastmodifieddate. Useful when an agent needs to cross-reference a ticket with a contact or deal.tickets:create — create a ticket with a required subject, optional content, stage (default "1" = New in the built-in Support Pipeline), and priority (LOW, MEDIUM, or HIGH). Custom pipelines use different numeric IDs — confirm in HubSpot before assigning.Example: “Create a support ticket: login broken, high priority” — agent calls tickets:create with subject: "Login broken", priority: "HIGH".Tips before you go live.
Grant only the scopes agents actually need
Grant only the scopes agents actually need
deals:write or tickets:write. Use the service toggles before connecting to grant only the permissions each agent’s tasks require. Narrower grants mean a smaller blast radius if something goes wrong, and they signal intent clearly when you audit access later.Override the properties parameter for richer data
Override the properties parameter for richer data
hs_lead_status, notes_last_contacted, or a custom property, pass those names as a comma-separated string in the properties parameter in the agent’s tool configuration. You only pay for what you fetch.Deal stage IDs are account-specific strings
Deal stage IDs are account-specific strings
deals:create is appointmentscheduled — a built-in HubSpot pipeline stage. If your team uses custom pipelines, retrieve the exact stage ID strings from your HubSpot pipeline settings before writing them into agent instructions. A wrong stage ID causes the create call to fail.Ticket stage '1' means New — custom pipelines differ
Ticket stage '1' means New — custom pipelines differ
"1" for the New stage. Custom pipelines use different numeric IDs. Before creating tickets in a custom pipeline, confirm the correct stage IDs in HubSpot → Settings → Support → Pipelines.Try the CRM Manager template
Try the CRM Manager template
No bundled MCP for HubSpot
No bundled MCP for HubSpot
Automate your pipeline in minutes.
Connect HubSpot via OAuth, enable the CRM Manager template, and watch contacts, deals, and tickets stay current — without any manual entry.
OAuth 2.0 — scoped exactly to what your agents need.
9 tools across 4 CRM objects · Granular permission toggles · No bundled MCP required.
Related topics.
All apps
Agents
Schedules
