GoHighLevel

GoHighLevel

This connector uses the HighLevel API v2 (https://services.leadconnectorhq.com, the platform also sold as GoHighLevel and LeadConnector) for one sub-account (location): contacts with notes, tasks and tags, conversations and sending SMS, email or WhatsApp, opportunities and pipelines, calendars and appointments, users, custom fields, workflows, form and survey submissions, invoices, payments and the Social Planner.

Setup (5 minutes, sub-account admin)

1. In the sub-account open Settings, Private Integrations and click Create new Integration. Name it (e.g. AnythingMCP) and select the scopes the tools need: locations.readonly, locations/customFields.readonly, locations/tags.readonly, contacts.readonly, contacts.write, conversations.readonly, conversations/message.readonly, conversations/message.write, opportunities.readonly, opportunities.write, calendars.readonly, calendars/events.readonly, calendars/events.write, users.readonly, workflows.readonly, forms.readonly, surveys.readonly, invoices.readonly, invoices.write, payments/orders.readonly, payments/transactions.readonly, payments/subscriptions.readonly, socialplanner/account.readonly, socialplanner/post.readonly, socialplanner/post.write. Leave out the write scopes the AI should not have.
2. Copy the token (it starts with pit-, shown once) into GOHIGHLEVEL_API_TOKEN. It is sent as Authorization: Bearer <token>.
3. Copy the Location ID from Settings, Business Profile (or the URL .../location/<id>/...) into GOHIGHLEVEL_LOCATION_ID. Every tool works in that sub-account.
4. Run gohighlevel_get_location to check both.

The connector sends the required Version header itself (2021-07-28, and 2021-04-15 for conversations and calendars).

Workflow

• Setup data: gohighlevel_get_location, gohighlevel_list_custom_fields (ids for customFields), gohighlevel_list_tags, gohighlevel_list_users and gohighlevel_get_user (ids for assignedTo), gohighlevel_list_pipelines (pipeline and stage ids), gohighlevel_list_calendars, gohighlevel_list_workflows.
• Contacts: find with gohighlevel_search_contacts, read with gohighlevel_get_contact; gohighlevel_create_contact, gohighlevel_upsert_contact (no duplicates by email or phone), gohighlevel_update_contact; tags with gohighlevel_add_contact_tags and gohighlevel_remove_contact_tags; notes with gohighlevel_list_contact_notes and gohighlevel_create_contact_note; tasks with gohighlevel_list_contact_tasks, gohighlevel_create_contact_task, gohighlevel_update_contact_task; gohighlevel_list_contact_appointments.
• Automations: gohighlevel_add_contact_to_workflow and gohighlevel_remove_contact_from_workflow (only published workflows), or add a tag that a workflow triggers on.
• Conversations: gohighlevel_search_conversations (by contact or unread), gohighlevel_get_conversation, gohighlevel_list_messages, and gohighlevel_send_message to send SMS, email, WhatsApp or social messages. Sending reaches the contact at once and may cost SMS or email credits: show the user the text and recipient and wait for a yes. Contacts with DND on a channel are not reached on it.
• Sales: gohighlevel_search_opportunities, gohighlevel_get_opportunity, gohighlevel_create_opportunity, gohighlevel_update_opportunity (move stage), gohighlevel_update_opportunity_status (won, lost).
• Booking: gohighlevel_get_free_slots, then gohighlevel_create_appointment; gohighlevel_list_calendar_events, gohighlevel_get_appointment, gohighlevel_update_appointment (reschedule, confirm, cancel, no-show).
• Leads from forms: gohighlevel_list_forms, gohighlevel_list_form_submissions, gohighlevel_list_surveys, gohighlevel_list_survey_submissions.
• Money: gohighlevel_list_invoices, gohighlevel_get_invoice, gohighlevel_create_invoice, gohighlevel_send_invoice; gohighlevel_list_orders, gohighlevel_get_order, gohighlevel_list_transactions, gohighlevel_get_transaction, gohighlevel_list_subscriptions.
• Social Planner: gohighlevel_list_social_accounts, gohighlevel_list_social_posts, gohighlevel_create_social_post (publishes at the scheduled time; confirm first).

Reading the answers: ids are 20-character strings. Dates on records are ISO 8601 in UTC; calendar free slots and events take Unix time in milliseconds; appointment start and end are ISO 8601 with an offset; opportunity search dates are mm-dd-yyyy; form, survey, invoice and payment filters take YYYY-MM-DD. Invoice and payment amounts are in currency units (120.5 = 120.50), not cents. Phone numbers are E.164.

Paging: contacts use page and page_limit (up to 500 per page, 10,000 results in total; beyond that pass search_after from the last contact). Opportunities use page and limit (up to 100) or startAfter and startAfterId from meta. Conversations use limit and start_after_date; messages last_message_id with nextPage. Invoices and payments use limit and offset; forms and surveys page and limit.

Limits and errors: HighLevel allows 100 requests per 10 seconds and 200,000 per day per sub-account (429 above that). 401 means a wrong or deleted token; 403 or "The token is not authorized for this scope" means the Private Integration lacks that scope (edit it and add the scope); 422 lists invalid fields; 400 "Version header was not found" should not happen through this connector.