LeadConnector | Operate As Docs

Connect your client's LeadConnector with a sign-in, and call its API through Operate As.

Website: gohighlevel.com
Connects by: Signing in with LeadConnector
Category: CRM and sales
Services: 1
Tools: 31

Service	Key	Base URL
LeadConnector	`lead-connector`	`https://services.leadconnectorhq.com`

Connecting

Your client presses Connect on their link and approves on LeadConnector's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "lead-connector"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "lead-connector"    ]  }]

Permissions

What the client reads	Permission it asks for
See your campaigns	`campaigns.readonly`
Add and change your contacts	`contacts.write`
See your contacts	`contacts.readonly`
See your sub-accounts	`locations.readonly`
See your contact tags	`locations/tags.readonly`
Add and change your contact tags	`locations/tags.write`
See your opportunities and pipelines	`opportunities.readonly`
Add and change your opportunities	`opportunities.write`
See your team's users	`users.readonly`
See your workflows	`workflows.readonly`
See your forms and their submissions	`forms.readonly`

Tools

Install LeadConnector's typed package for your language:

pip install operate-as-lead-connector

pip install operate-as-lead-connector

Run lead-connector.add_contact_to_campaign

curl -X POST https://api.operate.as/v1/actions/lead-connector.add_contact_to_campaign \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "contact_id": "<contact_id>",
      "campaign_id": "<campaign_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/lead-connector.add_contact_to_campaign \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "contact_id": "<contact_id>",      "campaign_id": "<campaign_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/lead-connector.add_contact_to_campaign

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://services.leadconnectorhq.com. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../lead-connector/contacts/" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../lead-connector/contacts/" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If LeadConnector refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's LeadConnector access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's LeadConnector access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "lead-connector",
    "services": [
      "lead-connector"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "lead-connector",    "services": [      "lead-connector"    ],    "reconnectUrl": "https://…"  }}