Setting up Tuco with GoHighLevel (Lead Connector)

This guide walks through connecting Tuco to a GoHighLevel sub account as a custom conversation provider, then building an automation that sends iMessage, follows up with a voice note, and falls back to SMS for contacts without an iPhone.
Estimated time: 15 minutes.

Before you start

You need:

• Your Tuco login credentials, issued after your invoice is paid
• Admin access to the GoHighLevel sub account you want to connect
• Within Go High Level you need to create a PIT Token inside (Step 3) 
• Location ID of the Go HIgh Level workspace (Only one install at a time) 
• At least one active provisioned line in your Tuco workspace

Sending rules:

• 50 new contacts per line, per day. This is a per line cap on first outbound messages. Scale volume by adding lines, not by raising the cap. This will get your line banned. 
• No links until the contact replies. Apple blocks link taps from senders who are not in the recipient's contact book, so a link in a cold opener is dead weight at best and a spam signal at worst.
• No attachments in the first outbound message. No voice notes, no images. These are permitted from message two onward, and the contact does not need to have replied first.
• No unsolicited or duplicate sends. Tuco automatically deduplicates repeat messages to the same lead.

Common mistakes

Part 1: Connect Tuco to GoHighLevel

Step 1. Open the CRM integration in Tuco

Log into app.tuco.ai. In the left sidebar, click Integrations (seventh item down). At the top of that page, next to API Keys, click CRM, then select Lead Connector.
Lead Connector is the whitelabel name for GoHighLevel. Both refer to the same platform.

Step 2. Choose your provider type

You will be offered three options: custom conversation provider, default provider, or whitelabel app.
Choose Custom Conversation Provider. This is the recommended option for most accounts, specifically those running their own A2P approval and not routing messages through an external bot or appointment setter. Click Next.

Step 3. Create a private integration in GoHighLevel

In a separate tab, open app.gohighlevel.com and switch into the sub account you want to connect.
Click the cog wheel to open Settings, then scroll to the bottom of the settings menu and click Private Integrations.
Click to create a new integration, name it Tuco AI, click Next, then select all scopes. Click Create.

Step 4. Copy the PIT token

GoHighLevel generates a token beginning with pit-. Click copy.
Save this token somewhere secure for your own records. It is not retrievable later. Paste it into Tuco and click Next.

Step 5. Copy your Location ID

Back in GoHighLevel, go to Settings → Business Profile. Your Location ID is displayed there. Click copy, return to Tuco, and paste it in.

Step 6. Verify scopes and connect

Click Check Scopes. Tuco will list the permissions it has been granted. All of them are required, because Tuco maintains a two way sync with GoHighLevel.
Click Continue, then Connect.

Step 7. Install the Lead Connector app

Tuco now generates an API key beginning with tuco_. Copy it.
Do not click Finish. Click Install Lead Connector instead. Clicking Finish at this point leaves the integration half configured.
You will be asked to log into GoHighLevel again. When the sub account selector appears, select one sub account only. Installing across multiple sub accounts in a single pass will fail. Repeat this step per sub account if you need more than one.
Click Install, then continue through the confirmation.

Step 8. Connect the account

A window opens asking for an API key. Paste the tuco_ key you copied in Step 7 and click Connect Account. A green check confirms the connection.

Step 9. Confirm the install

Reload GoHighLevel. Go to App Marketplace → Installed Apps and refresh until Tuco appears in the list.
If Tuco does not appear after a few refreshes, uninstall and repeat Steps 7 and 8.

Part 2: Build the automation

Step 10. Create the workflow

Go to Automations → Create Workflow → Start from Scratch.
Set your trigger. Common choices are a tag being added or a contact being created. Click Save.

Step 11. Check iMessage availability

Add an action. Switch to the Apps tab, search for Tuco, and select Check iMessage. The contact field autofills.

Step 12. Branch on the result

Add an If/Else action and build your own branch. Name the first branch something like iMessage available.
Set the condition to: Tuco AI → Check iMessage Available → true. Save the action.
Everything on the true branch sends through your Tuco line. Everything on the false branch will send through your A2P SMS number.

Step 13. Send the first message

On the true branch, add an action from Apps, search Tuco, and select Send iMessage.
The first message must be plain text only. No attachments, no links, no voice notes, no images. Apple flags accounts that open a new conversation with rich content.
Example:

Hi {{contact.first_name}}, this is [Name] from [Company].

Use the name field exactly as it appears in the contact record you are referencing.
Sending line: if your workspace has more than one line, specify the line ID. Copy it from the Tuco dashboard using the copy button next to the number, then paste it into the action.
Skip if replied: leave blank on the first message. It only matters for follow ups.
Save the action.

Step 14. Add a wait

Add a Wait step. One hour is a sensible default for the first follow up. Save.

Step 15. Send a voice note

Add another Tuco action, this time Send Voice Note. Voice notes are our recommended follow up format.
Note the flag on this action: it is available for follow ups only, never for opening a new conversation. This is the same Apple account safety reason described in Step 13.
Preparing the audio file:

1. Record your note and export it as an MP3
2. In Tuco, go to Leads → Upload Audio and drag the file in
3. Copy the resulting URL and paste it into the action

You can host the MP3 yourself instead, provided the URL is publicly accessible. Test this by opening the link in an incognito window. If it plays without a login, it will work. YouTube links, Loom links, and anything behind authentication will not.
Skip if replied: set this to true. If the contact already answered your first message, they should not receive an automated follow up.
Voice note toggle: leave this set to true so the message renders as a native audio message with a waveform rather than a generic file attachment.
Sending line: paste the same line ID used in Step 13.
Save the action.

Step 16. Add the SMS fallback

Go back to the false branch of your If/Else. Add Send SMS and write a plain text version of your message. This covers contacts who cannot receive iMessage.
Save the workflow.

Part 3: Testing and debugging

Click Test Workflow, choose a test contact, and click Run Test.
Execution Logs in GoHighLevel show which path each contact took through the branches. Use this first when a contact does not receive anything.
Activity Logs in Tuco (left sidebar) show sends, failures, and deduplications. Use this when the execution log shows a successful send but no message arrived.
Duplicate detection: Tuco blocks identical messages sent repeatedly to the same contact, as a spam control. During testing this means your second and third test runs may silently drop. Change the wording slightly between runs, for example swapping "Hi" for "Hey". This does not affect production sends to distinct contacts.

Part 4: Replying to contacts

Replies arrive in Conversations in GoHighLevel, the same as any other channel. The iMessage conversation provider appears in the composer, and you can switch between SMS, WhatsApp, and Tuco using the selector at the bottom.
Voice notes you sent appear in the thread as audio messages.

FAQ

Can I use my own MP3 hosted elsewhere? Yes, as long as the URL is publicly accessible. Open it in an incognito window to confirm it loads without a login.
Why did my test message not send? Most often duplicate detection. Check Activity Logs in Tuco. Otherwise check Execution Logs in GoHighLevel to confirm the contact took the branch you expected.
Do I need to repeat setup for each sub account? Yes. Each sub account needs its own private integration, Location ID, and install pass.

Foxwell & Pierce, Inc. | 8 The Green Ste R, Dover, DE 19901
Confidential. Tuco AI is operated by Inboxpirates Consulting (Crewcharge Technologies Pvt Ltd and Foxwell & Pierce, Inc.). iMessage is a trademark of Apple Inc. Apple is not affiliated with, and does not endorse, Tuco AI.

Updated on: 28/07/2026