Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

LeadConnector

Lead Connector - Go High Level

CategorySales And Crm
AuthenticationOAuth 2.0
Version0.3.0
Published scopes11 published scopes
Last updatedSeptember 19, 2026

Overview

Connect LeadConnector with Flows360

Lead Connector - Go High Level

Use the LeadConnector connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 11 actions and 4 triggers.

Available actions

  • Create Contact
  • Update Contact
  • Add Contact to Campaign
  • Add Contact to Workflow
  • Add Note to Contact
  • Search Contacts
  • Create Opportunity
  • Update Opportunity
  • Plus 3 additional declared actions.

Available triggers

  • New Contact
  • Contact Created or Updated
  • New Form Submission
  • New Opportunity

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: LeadConnector
  • Package: @activepieces/piece-lead-connector@0.3.0
  • Exact artifact digest: sha256:b9c4c46a7a45a0e4e7c03ff1531b8cd677757c0f0039eb7f81072e4af7abc925
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Contact (create_contact), Create a new contact. Classification: read.
  • Update Contact (update_contact), Update an existing contact. Classification: read.
  • Add Contact to Campaign (add_contact_to_campaign), Add an existing contact to a campaign. Classification: read.
  • Add Contact to Workflow (add_contact_to_workflow), Add an existing contact to a workflow. Classification: read.
  • Add Note to Contact (add_note_to_contact), Add a new note to a contact. Classification: read.
  • Search Contacts (search_contacts), Search for contacts with a search query. Classification: read.
  • Create Opportunity (create_opportunity), Create a new opportunity. Classification: read.
  • Update Opportunity (update_opportunity), Updates an existing opportunity. Classification: read.
  • Create Task (create_task), Create a new task. Classification: read.
  • Update Task (update_task), Update a task. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Contact, polling.
  • Contact Created or Updated, polling.
  • New Form Submission, polling.
  • New Opportunity, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects15
Supported actions11
Triggers4

Authentication

Authentication method: OAuth 2.0

Required scopes

campaigns.readonlycontacts.writecontacts.readonlylocations.readonlylocations/tags.readonlylocations/tags.writeopportunities.readonlyopportunities.writeusers.readonlyworkflows.readonlyforms.readonly

Authentication profiles

connection · oauth2

OAuth scopes: campaigns.readonly, contacts.write, contacts.readonly, locations.readonly, locations/tags.readonly, locations/tags.write, opportunities.readonly, opportunities.write, users.readonly, workflows.readonly, forms.readonly

Supported objects

ObjectReadWriteNotes
Create Contact Yes No Create a new contact.
Update Contact Yes No Update an existing contact.
Add Contact to Campaign Yes No Add an existing contact to a campaign.
Add Contact to Workflow Yes No Add an existing contact to a workflow.
Add Note to Contact Yes No Add a new note to a contact.
Search Contacts Yes No Search for contacts with a search query.
Create Opportunity Yes No Create a new opportunity.
Update Opportunity Yes No Updates an existing opportunity.
Create Task Yes No Create a new task.
Update Task Yes No Update a task.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Contact Yes No polling trigger declared by the pinned package.
Contact Created or Updated Yes No polling trigger declared by the pinned package.
New Form Submission Yes No polling trigger declared by the pinned package.
New Opportunity Yes No polling trigger declared by the pinned package.

Supported actions

Create Contact · Read

Create a new contact.

create_contact · Risk: low · Retry: safe

Inputs

  • firstName · string · Optional
  • lastName · string · Optional
  • email · string · Optional
  • phone · string · Optional
  • companyName · string · Optional
  • website · string · Optional
  • tags · array · Optional
  • source · string · Optional
  • country · string · Optional, When using a dynamic value, make sure to use the ISO-2 country code, and not the country name.
  • city · string · Optional
  • state · string · Optional
  • address · string · Optional
  • postalCode · string · Optional
  • timezone · string · Optional
Update Contact · Read

Update an existing contact.

update_contact · Risk: low · Retry: safe

Inputs

  • id · string · Required, The ID of the contact.
  • firstName · string · Optional
  • lastName · string · Optional
  • email · string · Optional
  • phone · string · Optional
  • companyName · string · Optional
  • website · string · Optional
  • tags · array · Optional
  • source · string · Optional
  • country · string · Optional, When using a dynamic value, make sure to use the ISO-2 country code, and not the country name.
  • city · string · Optional
  • state · string · Optional
  • address · string · Optional
  • postalCode · string · Optional
  • timezone · string · Optional
Add Contact to Campaign · Read

Add an existing contact to a campaign.

add_contact_to_campaign · Risk: low · Retry: safe

Inputs

  • contact · string · Required, The contact to use.
  • campaign · string · Required
Add Contact to Workflow · Read

Add an existing contact to a workflow.

add_contact_to_workflow · Risk: low · Retry: safe

Inputs

  • contact · string · Required, The contact to use.
  • workflow · string · Required
Add Note to Contact · Read

Add a new note to a contact.

add_note_to_contact · Risk: low · Retry: safe

Inputs

  • contact · string · Required, The contact to use.
  • note · string · Required
  • user · string · Required
Search Contacts · Read

Search for contacts with a search query.

search_contacts · Risk: low · Retry: safe

Inputs

  • query · string · Required, The value you want to search for.
Create Opportunity · Read

Create a new opportunity.

create_opportunity · Risk: low · Retry: safe

Inputs

  • pipeline · string · Required, The ID of the pipeline to use.
  • stage · string · Required, The stage of the pipeline to use.
  • title · string · Required
  • contact · string · Required, The contact to use.
  • status · string · Required
  • assignedTo · string · Optional
  • monetaryValue · number · Optional
Update Opportunity · Read

Updates an existing opportunity.

update_opportunity · Risk: low · Retry: safe

Inputs

  • pipeline · string · Required, The ID of the pipeline to use.
  • opportunity · string · Required
  • stage · string · Optional, The stage of the pipeline to use.
  • title · string · Optional
  • contact · string · Optional, The contact to use.
  • status · string · Optional
  • assignedTo · string · Optional
  • monetaryValue · number · Optional
Create Task · Read

Create a new task.

create_task · Risk: low · Retry: safe

Inputs

  • contact · string · Required, The contact to use.
  • title · string · Required
  • dueDate · string · Required
  • description · string · Optional
  • assignedTo · string · Optional
  • completed · boolean · Required
Update Task · Read

Update a task.

update_task · Risk: low · Retry: safe

Inputs

  • contact · string · Required, The contact to use.
  • task · string · Required
  • title · string · Optional
  • dueDate · string · Optional
  • description · string · Optional
  • assignedTo · string · Optional
  • completed · boolean · Optional
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Contact · Poll

Trigger when a new contact is added.

Contact Created or Updated · Poll

Trigger when a contact is created or updated.

New Form Submission · Poll

Trigger when a form is submitted.

Inputs

  • form · string
New Opportunity · Poll

Trigger when a new opportunity is added.

Inputs

  • pipeline · string

Setup

Setup

  1. Add the LeadConnector connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • campaigns.readonly
  • contacts.write
  • contacts.readonly
  • locations.readonly
  • locations/tags.readonly
  • locations/tags.write
  • opportunities.readonly
  • opportunities.write
  • users.readonly
  • workflows.readonly
  • forms.readonly
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-lead-connector@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 11 actions and 4 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required LeadConnector connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-lead-connector@0.3.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com