Integration · Sell and serve

HubSpot and Meteor AI agents

Connect HubSpot CRM to a Meteor Met: search and update contacts, companies and deals without creating duplicates, with 12 real tools.

Book a demo See every integration

How does HubSpot connect to Meteor?

Meteor connects to your company's HubSpot portal with a private app token and gives your Met 12 tools across three CRM objects: contacts, companies and deals. It can search them by text or by property, open one by its ID, create or update a contact by email without duplicating it, do the same for a company by its domain or by another unique property such as a tax ID, create and move deals, and associate all three. Before every write, the Met explains the change and waits for a yes from the person it is talking to. It does not delete records and it does not touch tickets, emails or marketing.

What it automates

What a Meteor Met does with HubSpot

Log the WhatsApp customer in HubSpot

Your Met talks to the person, asks for their email and creates or updates their contact in HubSpot. Because it searches by that email first, a returning customer is updated rather than duplicated.

Leave the company and the deal in place

With the contact ready, your Met registers the company by its domain or tax ID, opens the deal and associates all three. The rep opens HubSpot and finds a complete record, not three loose ones.

Move a deal to its next stage from the chat

When the customer confirms, your Met explains which stage and properties it will change, waits for the yes and updates the deal in HubSpot. Without that yes, the tool does not write.

Answer with what the CRM already knows

Before replying, your Met looks the person or their company up in HubSpot and reads the properties you ask for, so it does not ask again for what your team already recorded.

12 tools

Everything your Met can ask HubSpot for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`hubspot_test_connection`	Checks that the workspace's saved token still opens the HubSpot CRM.
`hubspot_get_account`	Says whether a token is saved and which authentication it uses; it does not query HubSpot.
`hubspot_search_contacts`	Searches contacts by free text or by property filters, up to 100 per page.
`hubspot_get_contact`	Opens a contact by its ID and returns the properties you ask for.
`hubspot_upsert_contact`	Creates or updates a contact after looking it up by email, so it is not duplicated.
`hubspot_search_companies`	Searches companies by free text or by property filters, with pagination.
`hubspot_get_company`	Opens a company by its ID and returns the properties you ask for.
`hubspot_upsert_company`	Creates or updates a company, looking it up by domain or by another unique property such as a tax ID.
`hubspot_search_deals`	Searches deals by free text or by property filters, with pagination.
`hubspot_create_deal`	Creates a deal with the properties you pass, only after explicit confirmation.
`hubspot_update_deal`	Changes the stage or the properties of an existing deal, only after explicit confirmation.
`hubspot_associate_records`	Associates a contact, company or deal with another one, using the HubSpot association type.

The limits

What the HubSpot integration does NOT do

We would rather say it here than have you find out during rollout.

It does not delete contacts, companies or deals. None of its tools removes a record from HubSpot.
It does not work with tickets, marketing emails, lists, tasks, notes or meetings. It covers three CRM objects: contacts, companies and deals.
It does not create new properties in your portal. It writes to properties that already exist in HubSpot, including the custom ones your team created.
It does not list pipelines or stages. To move a deal, the stage value has to be known in advance, because no tool looks it up.
It does not write without the confirmation flag. Creating, updating or associating needs the call to carry it: the Met sets it when the person in the conversation approves the change, and in an automated flow it is given when the flow is configured.

Before you start

What you need to connect HubSpot

1

A HubSpot private app token

You create it in your own HubSpot portal as a private app, with CRM read and write permissions on contacts, companies and deals. If the token lacks those permissions, HubSpot answers that it has no access and the connector tells you so.
2

Paste it once in Connections

In Meteor, under Connections, you open HubSpot CRM and paste the token for the portal that workspace will use. Meteor stores it encrypted, never shows it again and does not share it with other workspaces. It is never requested in the chat.

Frequently asked questions

Questions about HubSpot and Meteor

It avoids it. The contact tool searches by email first and, when it finds a match, updates that record instead of creating another. Companies work the same way with the domain or with the unique property you choose, such as a tax ID. HubSpot takes a few seconds to index a new record: two sign-ups in a row with the same email can duplicate it.

Creating, updating or associating needs explicit confirmation: the Met explains the change and waits for a yes from the person it is talking to, who can be your customer, as in a WhatsApp sign-up. In an automated flow, confirmation is given when the flow is configured. Reading and searching do not need it.

With a private app token from your portal, one per workspace. That token defines which parts of the CRM the connector can reach, so you decide the permissions when you create it.

Meteor CRM comes included and is where the conversations from your channels live. This integration is for the team that already runs its pipeline in HubSpot and wants the Met to feed it and read from it there, without switching tools.

Step by step