Connect WiseRep with Go High Level
Automatically push GHL leads into WiseRep calling campaigns — and send call transcripts, summaries and conversion status straight back to GHL when every conversation ends.
WiseRepHow it works
Two webhooks, opposite directions
One webhook pushes new GHL leads into a WiseRep campaign. The second sends call results back to GHL after every completed conversation.
Trigger in GHL
A workflow step fires when a contact qualifies — form submitted, tag applied, pipeline stage changed, or any GHL trigger you choose.
Webhook to WiseRep
GHL POSTs the contact's name, phone and campaign tag to WiseRep's inbound webhook at api.wiserep.com/api/webhook.
AI agent dials the lead
WiseRep matches the tag to a campaign, queues the contact and the assigned AI agent makes a natural-voice call.
Results posted back
After every completed call WiseRep sends transcript, AI summary, conversion status and call length back to your GHL workflow.
| Direction | From | To | Purpose |
|---|---|---|---|
| Inbound | Go High Level | WiseRep | Send a new lead into a WiseRep campaign |
| Outbound | WiseRep | Go High Level | Send call results back after every completed call |
Prerequisites
Before you start
- A WiseRep account on a paid plan (or active trial)
- At least one Campaign created in WiseRep with an Agent assigned
- A Go High Level sub-account with Workflow access
- The campaign's Tag set in WiseRep (explained in Step 1 below)
Tag your WiseRep campaign
Tags are how WiseRep routes incoming GHL leads to the correct campaign. Every campaign that receives GHL leads must have a unique tag.
- 1In WiseRep, go to Campaigns and open the campaign you want GHL to feed leads into.
- 2Find the Tag field in the campaign settings.
- 3Enter a short, unique identifier — see examples on the right.
- 4Save the campaign.
Rules for tags
- Must be unique — no two campaigns can share the same tag
- Case-sensitive — GHL-Sales and ghl-sales are treated as different tags
- Use hyphens instead of spaces
| Example Tag | Use Case |
|---|---|
ghl-sales | Main outbound sales campaign |
q3-real-estate | Quarterly real estate outreach |
webinar-follow-up | Post-webinar lead follow-up |
inbound-form | Leads from a website contact form |
Set up the inbound webhook in GHL
This webhook tells GHL to send lead data to WiseRep whenever a contact qualifies.
POST https://api.wiserep.com/api/webhookIn Go High Level:
- 1Open the Workflow that should trigger a call (e.g., on contact creation, tag applied, form submitted, pipeline stage changed).
- 2At the point in the workflow where you want to trigger the call, add a Webhook action.
- 3Set method POST, URL https://api.wiserep.com/api/webhook, and Content-Type application/json.
- 4Build the request body using the field reference.
- 5Save and Publish the workflow.
Phone number format
Numbers must be in international format — +12125550100, not 2125550100. If GHL's contact.phone doesn't include the country code, prepend it manually: "+1{{contact.phone}}".
Example request body
{
"full_name": "{{contact.full_name}}",
"phone": "{{contact.phone}}",
"tags": "ghl-sales",
"email": "{{contact.email}}",
"company": "{{contact.company_name}}",
"website": "{{contact.website}}"
}| Field | Type | Required | Description |
|---|---|---|---|
full_name | string | Yes | Contact's full name |
phone | string | Yes | Contact's phone number in international format |
tags | string | Yes | The WiseRep campaign tag (must match exactly) |
email | string | No | Contact's email address |
company | string | No | Contact's company name |
website | string | No | Contact's website |
Configure the outbound webhook in WiseRep
This tells WiseRep where to send call results after every completed call from a tagged campaign.
- 1In WiseRep, go to Integrations → Go High Level.
- 2In the Webhook URL field, paste the URL of your GHL workflow webhook trigger (create a new GHL workflow with a Webhook trigger to get this URL).
- 3Toggle the integration to Enabled.
- 4Click Save.
From this point forward, every time a call completes on a tagged campaign, WiseRep will POST the results to that URL.
Example payload WiseRep sends to GHL
{
"to": "+12125550100",
"status": "completed",
"summary": "Sarah expressed strong interest in the enterprise plan and requested a follow-up demo on Thursday at 2pm.",
"transcript": "Agent: Hi Sarah, this is Alex calling from WiseRep — is now a good time?\nSarah: Hi Alex, yes I've been expecting your call...",
"converted": true,
"callLength": 187
}| Field | Type | Description |
|---|---|---|
to | string | The phone number that was called |
status | string | Call outcome: completed, no-answer, voicemail, or failed |
summary | string | AI-generated summary of the conversation and outcome |
transcript | string | Full word-for-word transcript of the call |
converted | boolean | true if the lead was marked as converted, false otherwise |
callLength | number | Duration of the call in seconds |
Use call results in GHL
Once call data lands in GHL, you can use it to drive follow-up actions. Common setups:
| GHL Action | Condition | Example Use |
|---|---|---|
| Apply a tag | converted = true | Tag contact as interested |
| Apply a tag | converted = false | Tag contact as not-interested |
| Add a note | Always | Save summary to the contact's activity timeline |
| Update custom field | Always | Store transcript and callLength on the contact record |
| Enroll in sequence | converted = true | Trigger a follow-up email or SMS nurture sequence |
| Notify team member | converted = true | Alert a rep to follow up on a hot lead |
Use GHL's If/Else branches in your workflow to split on the converted field and route leads into the appropriate follow-up path.
Under the hood
How lead routing works
- 1
Extracts full_name, phone, tags, and any other fields from the payload.
- 2
Splits tags by comma — a single payload can include multiple tags (e.g., "tags": "ghl-sales,urgent") and WiseRep matches the first campaign found.
- 3
Looks up the campaign by tag.
- 4
If a campaign is found: the contact is immediately added to the campaign's dial list and will be called according to the campaign's schedule and preferred calling hours.
- 5
If no campaign exists yet with that tag: the lead is stored safely and will be automatically retroactively added to the campaign as soon as one is created with a matching tag — no leads are ever lost.
All fields included in the payload (email, company, website, or any custom fields) are stored on the lead record and available as variables in your agent's prompt:
Hi {full_name}, this is Alex calling from WiseRep on behalf of {company}...Troubleshooting
Common issues & fixes
Leads aren't being added to my campaign
| Check | What to do |
|---|---|
| Tag mismatch | Confirm the tags value in your GHL webhook body exactly matches the tag on the WiseRep campaign — it's case-sensitive |
| Campaign status | Leads can only be added to campaigns with status Scheduled or Active — not Completed or Cancelled |
| Workflow not firing | In GHL, open the workflow's execution history and confirm the webhook action ran. Check for errors on the webhook step |
| Wrong URL | Confirm you're posting to https://api.wiserep.com/api/webhook (not a staging or test URL) |
The outbound webhook isn't reaching GHL
| Check | What to do |
|---|---|
| Integration not enabled | Go to Integrations → Go High Level in WiseRep and confirm the toggle is On |
| No tag on campaign | The outbound webhook only fires for calls from campaigns that have a tag set — verify your campaign has a tag |
| Wrong GHL URL | Confirm the URL in WiseRep's integration settings matches the webhook trigger URL in your GHL workflow |
| GHL workflow not published | In GHL, make sure the receiving workflow is Published, not in draft |
| Single calls excluded | Calls made via Calls → New Call are not attached to a campaign and will not trigger the outbound webhook |
Phone numbers aren't connecting
| Check | What to do |
|---|---|
| Missing country code | Ensure GHL is sending numbers in international format: +12125550100 |
| GHL strips the + | Some GHL configurations omit the +. In your webhook body, use: "+{{contact.phone}}" or "+1{{contact.phone}}" |
| Invalid format | Avoid spaces, dashes, or parentheses — WiseRep expects a clean E.164 number |
Leads arrived before the campaign was created
No action needed. WiseRep stores all inbound webhook data even when no matching campaign exists. The moment you create a campaign and assign the matching tag, WiseRep will automatically retroactively add all previously received leads with that tag into the campaign's dial list.
Go High Level Integration FAQ
Wire WiseRep into your GHL workflows.
See the two-way GHL sync live in a 20-minute demo, or start a free trial and connect your first workflow today.