Lead Connector - Go High Level
LeadConnector currently provides 4 triggers that can start a workflow and 11 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
New Contact
Trigger when a new contact is added.
Contact Created or Updated
Trigger when a contact is created or updated.
New Form Submission
Trigger when a form is submitted.
New Opportunity
Trigger when a new opportunity is added.
Create Contact
Create a new contact.
Update Contact
Update an existing contact.
Add Contact to Campaign
Add an existing contact to a campaign.
Add Contact to Workflow
Add an existing contact to a workflow.
Add Note to Contact
Add a new note to a contact.
Search Contacts
Search for contacts with a search query.
Create Opportunity
Create a new opportunity.
Update Opportunity
Updates an existing opportunity.
Create Task
Create a new task.
Update Task
Update a task.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported LeadConnector event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Contact
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported LeadConnector action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Contact
Combine LeadConnector with another integration and Coherence records to keep account, contact, and deal context attached to the work around it.
Starts with
New Contact
Finishes with
Create Contact, then preserve the outcome in Coherence
The exact authentication fields depend on LeadConnector. The workflow structure stays straightforward:
Authorize the LeadConnector account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with LeadConnector or provide a complementary trigger or action.
LeadConnector currently provides 4 triggers that can start a workflow and 11 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
LeadConnector currently lists 4 triggers and 11 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported LeadConnector triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
