GoHighLevel + Growth Dept ACR
Built and tested. A contact field starts a campaign; it connects once Growth Dept registers its GoHighLevel app.
Ready once our app is registered
Overview
Set the contact field ACR Active Campaign ID to a campaign's ID, usually from a workflow, and ACR starts that campaign; 0 stops it. ACR can add a note for each call, email and text, turn on Do Not Disturb when someone opts out, and book on the sub-account's calendars. Calls and texts still need the contact's recorded consent: map the opt-in fields your CRM keeps, or the campaign's consent rule skips them. It is built and tested against the vendor's documented API, and it connects once Growth Dept registers its app with GoHighLevel.
What GoHighLevel is
GoHighLevel is a CRM and marketing platform used by agencies and their clients.
How it connects, once the app is registered
The connection is built and tested. No store can connect it until Growth Dept registers its app with GoHighLevel.
- 1
Install on one sub-account
Install the Growth Dept ACR app and choose exactly one sub-account.
- 2
Let ACR add its field
ACR adds the ACR Active Campaign ID contact field to GoHighLevel, plus the webhook or check that tells it when the field changes.
- 3
Start a contact
Set the ACR Active Campaign ID contact field to the campaign's ID, usually with a workflow step that sets a custom field. ACR imports the contact and starts that campaign.
- 4
Stop a contact
Set the field to 0, or to the campaign's stop value.
- 5
Start reading and publish
Reading stays off until an admin starts it, with a confirmation. Then publish the campaign and switch its trigger on when you are ready.
What you can do today
No store can connect GoHighLevel directly yet. If GoHighLevel can post an event to a web address, the Custom API route below works today, because a Custom API campaign accepts events from any sender.
- 1
Create a Custom API campaign
Choose Custom API as the campaign's lead source. ACR shows a private trigger URL with its own token.
- 2
Send the event from GoHighLevel
Have a workflow post the contact to the trigger URL when your chosen field changes.
- 3
Use ACR's field names
Name the event checkout/updated and send the shopper's unique_id, email or phone, first_name, final_price and cart_link, as the API reference shows.
- 4
Send the purchase too
Post checkout/completed with the same unique_id to the same trigger URL when the shopper pays, so outreach stops for anyone who has already bought.
- 5
Test and publish
Run a practice conversation, then publish the campaign and switch its trigger on when you are ready.
Waiting on GoHighLevel?
Tell us how you use GoHighLevel. We will say what ACR can do for your store today and what is still ahead.