Pushing Yirlo replies and interested leads into GoHighLevel

What the GoHighLevel connection does

Yirlo emails decision makers on your behalf, reads what comes back and sorts each reply. When a person writes back, Yirlo can post that reply to a webhook address. When the reply is interested, Yirlo posts a second kind of event for a hot lead. GoHighLevel receives both through a workflow and turns them into records your team already works in.

This suits agencies and service businesses that run their sales follow-up inside GoHighLevel. The contact, the pipeline stage and the reminder to call all live in one place, while Yirlo handles finding companies, checking addresses, writing the first email and answering replies.

Before you start

Before you begin, line up a pair of prerequisites. First, a live campaign inside your Yirlo project. Second, a GoHighLevel sub-account where you're allowed to build workflows. The Inbound Webhook trigger sits in GoHighLevel's premium tier, so check how your plan bills for premium workflow actions before any live replies arrive.

Decide up front what each event should create. A common pattern is that every reply creates or updates a contact, while a hot lead also creates an opportunity in a pipeline stage such as New interested lead, plus a task for whoever books the call.

• A GoHighLevel workflow with the Inbound Webhook trigger
• A Yirlo project with a campaign running or ready to run
• A pipeline in GoHighLevel for the opportunities
• The person who will own follow-up tasks

Set it up in six steps

The order matters a little: the URL comes from GoHighLevel first, and the sample fields come from Yirlo second.

• In GoHighLevel, open Automation, create a new workflow and choose Inbound Webhook as the trigger.
• Copy the webhook URL that the trigger shows.
• In Yirlo, open the webhook settings under Integrations, paste the URL and choose the events you want: reply.received, hot_lead.received, or both.
• Press Send test event in Yirlo. GoHighLevel receives a sample and reads its fields, so they appear in the mapping dropdowns.
• Add a Create Contact or Update Contact action and map email, first_name, last_name and company from the webhook data.
• Add a Create Opportunity action or a Create Task action, save the workflow and publish it.

What each event contains

Yirlo sends two event types. A lead's genuine response produces reply.received. When Yirlo labels that response as interested, hot_lead.received is sent. The event name is part of the payload, so a single workflow can split the two with an If/Else step.

Each payload includes the contact's email address, first and last name and employer, plus the campaign that contacted them and the reply text. Map the email, names and employer onto the contact record. Store the campaign in a tag, a custom field or the opportunity name, so you can later see which audience produced the lead. Drop the reply text into a note or task description, so whoever follows up already knows what the lead wrote.

Out-of-office messages and unsubscribe replies are labeled by Yirlo as well. If you only want people who answered with intent in your pipeline, build the opportunity step on the hot lead event and let ordinary replies create or update the contact only.

Contact, opportunity or task: which to choose

Use the contact step for every event. Matching on email keeps a lead from appearing twice when the same person replies a second time.

Use an opportunity when a hot lead should appear in a pipeline with a stage and a value. An agency selling websites and ads to dental clinics, roofing contractors or law firms usually wants this, because the owner then sees interested prospects next to the deals already in progress.

Use a task when a human should act quickly and a pipeline card would add little. A task titled with the lead's company and a reply excerpt in the description tells a sales rep exactly what to do next. Many teams add both: the opportunity records the deal and the task assigns the call.

Checking the signature

Yirlo signs every delivery. To verify one, compute an HMAC-SHA256 digest over the body bytes exactly as received, keyed with your signing secret, and compare it with the X-Yirlo-Signature header. A matching value shows the event came from Yirlo and was not altered on the way. Full details are in the docs at yirlo.com/api-docs.

A GoHighLevel workflow URL works like a password, so keep it private and paste it only into Yirlo. If you want verification on every event, run a small endpoint of your own that checks the header and then forwards valid events to the GoHighLevel URL. Teams that skip this step can rely on the secrecy of the URL and rotate it by creating a new trigger when needed.

Other ways to get leads into GoHighLevel

An intermediary tool is another option, and all three popular ones work. In Zapier, start a Zap with the Catch Hook event from Webhooks by Zapier. In n8n, place a Webhook node. In Make, select Custom webhook. Any of them receives the identical signed payloads and can pass the data to a GoHighLevel action. Ready-made Yirlo connectors for those tools are coming soon.

For scheduled syncing, the Yirlo API reads hot leads and the inbox with an X-API-Key, so a script can pull new items every hour. Leads also download as a CSV from Yirlo, which works well for a one-time import of your existing results into GoHighLevel.

Questions

Related