Integration · Sell and serve

HighLevel and Meteor AI agents

Connect HighLevel to a WhatsApp Met: find and update contacts, tag them, move opportunities and check appointments through the official MCP server.

Book a demo See every integration

How does HighLevel connect to Meteor?

With the HighLevel ready connector, your WhatsApp Met works on the HighLevel sub-account the admin authorizes. It finds the contact, creates or updates it without duplicating it, adds tags and reads its tasks. It also checks the pipelines, finds the customer's opportunity and moves it to another stage, reviews calendar events and appointment notes, and reads orders and payment transactions. It is HighLevel's official server: usage runs on your account, and removing tags starts switched off until the admin turns it on.

What it automates

What a Meteor Met does with HighLevel

Log the WhatsApp customer without duplicates

When someone writes, the Met looks for the contact in HighLevel and creates it if it is missing; if it exists, it updates it with what the person said. Then it adds the tags your team uses to segment.

Move the opportunity when the customer moves forward

The Met checks the pipelines and their stages, finds the customer's opportunity and moves it to the right stage, for example from "interested" to "quote sent".

Tell the customer which appointment they have

If the customer asks about their appointment, the Met reviews the sub-account calendar events and the appointment notes, and replies with the date and what was noted.

Confirm a payment or an order

When the customer says they already paid, the Met looks up the order or reviews the sub-account's payment transactions and confirms what is on record.

21 tools

Everything your Met can ask HighLevel 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
`contacts_get_contacts`	Searches and lists the contacts in the sub-account.
`contacts_get_contact`	Returns a contact's full details.
`contacts_create_contact`	Creates a new contact in the sub-account.
`contacts_upsert_contact`	Creates the contact or, if it already exists, updates it instead of duplicating it.
`contacts_update_contact`	Updates an existing contact's details.
`contacts_add_tags`	Adds tags to a contact.
`contacts_remove_tags`	Removes tags from a contact. It starts switched off.
`contacts_get_all_tasks`	Lists the tasks linked to a contact.
`conversations_search_conversation`	Searches conversations in the sub-account.
`conversations_get_messages`	Returns the messages in a HighLevel conversation.
`conversations_send_a_new_message`	Sends a new message inside a HighLevel conversation.
`calendars_get_calendar_events`	Lists the events and appointments in the sub-account calendars.
`calendars_get_appointment_notes`	Returns the notes saved on an appointment.
`opportunities_get_pipelines`	Lists the sales pipelines and their stages.
`opportunities_search_opportunity`	Searches opportunities in the sub-account.
`opportunities_get_opportunity`	Returns an opportunity's details.
`opportunities_update_opportunity`	Updates an opportunity, for example the pipeline stage it is in.
`locations_get_location`	Returns the connected sub-account's details.
`locations_get_custom_fields`	Lists the custom fields the sub-account has.
`payments_get_order_by_id`	Returns an order by its ID.
`payments_list_transactions`	Lists the sub-account's payment transactions.

The limits

What the HighLevel integration does NOT do

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

It does not create new opportunities: the server lets it search, read and update them, but it has no tool to open an opportunity from scratch.
It does not book, move or cancel appointments. It reads calendar events and appointment notes; booking still happens in HighLevel.
It does not delete contacts or opportunities. The only action that removes anything is removing tags, and it starts switched off.
It does not ask for confirmation in the chat before writing. The admin chooses in Connections which actions stay on.
It sees no more than the granted permissions allow: HighLevel states that the available tools depend on those permissions.

Before you start

What you need to connect HighLevel

1

A HighLevel sub-account

You need access to the sub-account where your contacts, pipelines and calendars live. If you are an agency, connect the sub-account of the client the Met will serve.
2

Connect it in Met

In Met, open Connections → HighLevel → Connect. A HighLevel window opens so you can sign in and authorize Met. Then you choose which actions stay on.

Frequently asked questions

Questions about HighLevel and Meteor

No. The official server lets it search, read and update opportunities, not create them. If the customer already has an opportunity, the Met can move it to another stage.

Yes, but the Met works with the sub-account that was connected. To serve another agency client, connect that client's sub-account.

It can send a new message inside a HighLevel conversation if that action is on. The WhatsApp conversation with the Met still happens in Meteor.

You do, with your own HighLevel account. Meteor does not resell HighLevel: the connector uses your company's account and whatever that account has enabled.

Step by step