GoHighLevel (GHL) Integration #

Already using GoHighLevel (GHL) to manage your business? This integration lets you add Your AI Connector's AI-powered messaging on top of your existing GHL setup. Messages that come into GHL are forwarded to Your AI Connector for AI-powered handling, and replies from Your AI Connector are sent back through GHL to the customer on the original channel.

Using a different CRM? It does not need a dedicated screen to work with Your AI Connector: see Connecting a Tool We Do Not List for custom functions, the API and webhooks.

This means you can keep using GHL as your main hub while letting the AI handle the AI-driven conversations.

Prerequisites #

• An active Your AI Connector account with your API key (found at Settings → Integrations → API Key). An API key is a unique code that lets GHL securely communicate with your account.
• A GoHighLevel account with permission to create workflows and manage webhooks (automated notifications between systems).

How It Works #

Workflow 1: GHL to Your AI Connector #

This workflow forwards incoming messages from GHL to Your AI Connector.

Step 1: Create the Workflow #

1. In GHL, go to Automation > Workflows.
2. Click Create New Workflow.
3. Name it something descriptive, such as “Send Message to Your AI Connector.”

Step 2: Add Triggers #

Add a trigger for each channel you want to forward:

• Customer Replied - SMS
• Customer Replied - Email
• Customer Replied - Facebook Message
• Customer Replied - Instagram DM
• Customer Replied - Live Chat

You can add all of them or only the channels relevant to your setup.

Step 3: Add Tag Filter (Optional) #

If you only want to forward messages from specific contacts:

1. Click Add Filter on the trigger.
2. Set the condition to “Contact has tag.”
3. Choose your tag(s).
4. Select whether the contact should have any or all of the selected tags.

Step 4: Create a Channel Split #

Add a Condition action to route each channel to its own webhook:

Step 5: Configure Webhooks #

For each branch, add a Webhook / HTTP Request action:

• Method: POST

• URL:

  https://api.youraiconnector.com/v1/incoming_custom_channel_message?apiKey=YOUR_API_KEY
  

• Custom Data fields:

Channel values per branch:

Step 6: Enable Re-Entry #

In the workflow settings, make sure Allow Re-entry is enabled. Without this, only the first message from each contact will be forwarded.

Workflow 2: Your AI Connector to GHL #

This workflow receives replies from Your AI Connector and sends them to the customer through the correct GHL channel.

Step 1: Create an Inbound Webhook in GHL #

1. In GHL, go to Settings > Developers / API.
2. Click Create New Webhook (or “Inbound Webhook”).
3. Name it “Messages.”
4. Save and copy the webhook URL — you’ll need it in the next step.

Step 2: Configure Your AI Connector #

1. In Your AI Connector, click Settings in the sidebar.
2. Under Channels, click Channels.
3. Scroll to the Custom channel card at the very bottom of the page.
4. Paste the GHL inbound webhook URL you just copied into Webhook URL (it must be a public HTTPS address) and click Save.

This is not the Settings → Integrations → Webhooks page. That page is for event notifications and sends a different payload. The GHL outbound relay is set on the Custom channel card under Settings → Channels.

Your AI Connector will now automatically send a notification to GHL every time a message is sent to a contact. The data sent looks like this:

{
  "contactId": "NtL97bwnhITrfIq8lWFi",
  "messageId": "s28dtg13qNuhXLoKpcLs",
  "userId": "wpDZRvaw4Hgh4whUBpwlKPRftOi2",
  "body": "Message content here",
  "toId": "qtpBsc6fiqkXTnSOeze3",
  "channel": "email"
}

Nav note: the API Key you use for Workflow 1 and the Custom channel card you use here live in different places — Settings → Integrations → API Key for the key, and the Custom channel card at the bottom of Settings → Channels for this relay. The separate Settings → Integrations → Webhooks page is for event notifications and sends a different payload; see Webhooks if that is what you want instead.

Step 3: Create the Response Workflow #

1. In GHL, go to Automation > Workflows.
2. Create a new workflow named “Send Message to Contact.”
3. Set the trigger to Inbound Webhook and select the webhook you created in Step 1.

Step 4: Add a Find Contact Action #

1. Add a Find Contact action.
2. Set the search field to Contact ID.
3. Use the value: {{inboundWebhookRequest.toId}}

Step 5: Add an Optional Tag Check #

If you want to limit which contacts receive messages from Your AI Connector:

1. Add a Condition action.
2. Check if the contact has a specific tag.
3. If the tag is missing, end the workflow (add a “Stop” action on the false branch).

Step 6: Add a Channel Split #

Add a Condition action that routes the message based on {{inboundWebhookRequest.channel}}:

Step 7: Configure Each Send Action #

In each send action, set the message body to:

{{inboundWebhookRequest.body}}

Step 8: Enable Re-Entry #

As with Workflow 1, make sure Allow Re-entry is enabled in the workflow settings.

Testing the Integration #

Test GHL to Your AI Connector (Workflow 1) #

1. Send a message to your GHL number or connected channel (for example, send yourself an SMS).
2. Open Your AI Connector and verify the message appears in Chats.
3. Check that the channel label is correct (SMS, email, etc.).
4. Repeat for each channel you configured.

Test Your AI Connector to GHL (Workflow 2) #

1. In Your AI Connector, send a reply to a contact (manually or let the AI respond).
2. Open GHL and verify the contact received the message.
3. Confirm it was sent through the correct channel.
4. Check that the message content matches.

Troubleshooting #

Next Steps #

• Webhooks — set up webhooks for other Your AI Connector events.
• API Access — use the API for custom integrations beyond GHL.
• Custom Channels — learn more about custom channel messaging.