Contact Followers Setup

Manage team member followers on contact records so the right people get notified when contacts update. This quick-start shows you how to add and remove followers through the API.

Prerequisites

Before working with Contact Followers, confirm you have:

A GoHighLevel sub-account with team members (users) configured
A Private Integration Token with the contacts scope configured
At least one contact ID and one user ID to test with
A REST client such as Postman, Insomnia, or curl

To find user IDs, check your sub-account’s team member list in Settings > My Staff or use the Users API endpoint.

Set Up Authentication

Contact Followers use the same authentication as all contact endpoints. You need a Private Integration Token (PIT) with the contacts scope.

If you already have a PIT from a previous setup, reuse it. Follower operations are covered under the same contacts scope.

If you need a new token, navigate to Settings > Integrations > Private Integrations in your sub-account. Create a new integration, enable the contacts scope, save, and copy the token.

Set your Authorization header to Bearer {your-pit-token} for all requests. Your base URL is https://services.leadconnectorhq.com.

Make Your First Call

The primary operation is adding a follower to a contact. Send a POST request to /contacts/{contactId}/followers:

POST /contacts/{contactId}/followers
Authorization: Bearer {your-pit-token}
Content-Type: application/json

{
  "followers": ["user-id-1", "user-id-2"]
}

The followers parameter accepts an array of user IDs. Each user ID corresponds to a team member in your sub-account. When added as a follower, that team member receives notifications about changes to the contact record, including new messages, notes, tasks, and status updates.

To remove followers, send a DELETE request to /contacts/{contactId}/followers with the same body format:

DELETE /contacts/{contactId}/followers
Content-Type: application/json

{
  "followers": ["user-id-1"]
}

This removes only the specified users from the follower list. Other followers remain unaffected.

Handle the Response

A successful follower addition returns a 200 status confirming the update:

{
  "followers": ["user-id-1", "user-id-2", "existing-follower-id"]
}

The response includes the complete list of current followers on the contact, not just the ones you added. This lets you verify the full follower state in one call.

When removing followers, the response returns the updated follower list with the specified users removed. If a user ID in your removal request was not a follower, the API silently ignores it and processes the rest.

Common errors: 400 means the followers array is missing or empty. 404 means the contactId does not exist. 401 means your token is invalid or lacks the contacts scope. If a user ID does not correspond to an active team member, the API may accept it but the user will not receive notifications.

Test Your Setup

Run through this checklist to confirm follower management is working:

Add a follower with POST /contacts/{id}/followers using your own user ID and verify the 200 response
Check the contact with GET /contacts/{id} and confirm the followers array includes your user ID
Trigger a notification by adding a note to the contact via API or the UI. Confirm you receive a notification as a follower
Remove yourself with DELETE /contacts/{id}/followers and verify you no longer appear in the followers list
Add multiple followers in a single call with two or more user IDs and confirm all are added

Open the contact record in the GoHighLevel UI to verify followers display correctly. Team members listed as followers should see the contact’s activity in their notification feed.

Next Steps

Read the full Contact Followers Guide for patterns like auto-assigning followers based on lead source or pipeline stage. Combine followers with Contact Notes to ensure the right team members are notified when important context is logged, or use Contact Tags to build workflows that automatically add followers when high-value tags are applied.