GoHighLevel integration

What it does

The GoHighLevel integration lets your agency operate inside a client's sub-account without leaving TaskJuice. Connect a client's GoHighLevel Location once and you can create and update contacts, push deals into pipelines, list pipeline structure, log tasks, and send SMS messages through the client's own Conversations channel. Every call targets the Location ID recorded on the connection, so a workflow you build for one client runs unmodified against the next sub-account you onboard.

Connect a GoHighLevel account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose GoHighLevel and click Connect.
3. The GoHighLevel marketplace prompts the account owner to pick a Location (sub-account). The chosen Location ID is what TaskJuice will use as the API tenant for every call on this connection.
4. Approve the requested scopes (contacts, opportunities, conversations, tasks, locations, pipelines).
5. TaskJuice returns to the workspace with the connection ready to use in any workflow.

To revoke access, the account owner can open the GoHighLevel marketplace and uninstall the TaskJuice app from that Location. The full grant flow is documented in the GoHighLevel marketplace authorization guide.

Triggers

• gohighlevel/contact-created fires when a new contact is created in the connected sub-account. The payload carries the GoHighLevel ContactCreate event with locationId, id, name, email, phone, and tags.
• gohighlevel/opportunity-status-updated fires when an opportunity's status changes (for example, from open to won). The payload carries the GoHighLevel OpportunityStatusUpdate event with pipelineId, pipelineStageId, status, previousStatus, and monetaryValue, so workflows can act on closed-won transitions or other status diffs without a follow-up read.

GoHighLevel signs every webhook delivery with HMAC-SHA256 and sends the base64-encoded digest in the x-wh-signature header. TaskJuice verifies the signature against the shared secret stored on the trigger before activating the workflow. Activations that fail the check are rejected.

Actions

• gohighlevel/create-contact, gohighlevel/update-contact, gohighlevel/get-contact, gohighlevel/list-contacts cover the contact lifecycle, including tags and attribution source.
• gohighlevel/create-opportunity creates an opportunity in a pipeline stage, attached to a contact, with optional monetary value and owner.
• gohighlevel/list-pipelines returns every opportunity pipeline (and its stages) in the connected sub-account, so workflow authors can map a human-readable pipeline name to the GoHighLevel pipelineId and pipelineStageId values that create-opportunity requires.
• gohighlevel/add-task attaches a task to a contact with a title, body, due date, and optional assignee.
• gohighlevel/send-sms sends an SMS through the GoHighLevel Conversations channel, using a Twilio number provisioned in the sub-account.

Known limitations

• GoHighLevel enforces per-Location rate limits on the v2 API. When the API returns a 429 status, TaskJuice surfaces it as a retryable error and respects the Retry-After header. Refer to the GoHighLevel rate-limiting reference for the current allowance per plan tier.
• A connection is scoped to a single GoHighLevel Location. To run workflows across multiple client sub-accounts, create one connection per Location.
• The integration targets the LeadConnector v2 REST API with Version: 2021-07-28. Endpoints or webhook event types outside that contract are not exposed.
• gohighlevel/send-sms requires a Twilio number provisioned inside the GoHighLevel sub-account. Without a provisioned number, the Conversations API returns a 422 validation error.