Send Yirlo replies and hot leads to Make
By the Yirlo team · Product details checked against the app
If your follow-up process already lives in Make, Yirlo can feed it directly. Add a Custom webhook trigger to a scenario, paste its URL into Yirlo, and every real reply and every hot lead arrives in Make as structured data. This page walks through the setup, the exact payload, and the scenarios that are worth building first.
How Yirlo and Make fit together
Yirlo does the outbound work: it finds companies and decision makers, writes the first emails, sends them and reads what comes back. Make takes over at the moment a person answers. Yirlo posts the reply to a webhook URL you control, and your Make scenario decides what happens next.
Yirlo connects to Make through Make's own Custom webhook module, which acts as the trigger. Setup takes a few minutes and works like any other webhook-based scenario.
Make can receive two kinds of Yirlo events. Use reply.received to hear about each real answer a prospect writes back. Out-of-office notices, unsubscribe messages and plain refusals never trigger it. Use hot_lead.received when Yirlo judges that an answer signals genuine purchase interest.
Set up the Custom webhook in Make
You need a Make scenario and access to Settings, then Integrations, inside the Yirlo app. The whole setup is five steps.
- In Make, create a new scenario and add the Webhooks module as the first step. Choose the Custom webhook trigger.
- Click Add, name the webhook something like Yirlo replies, and save. Make shows a URL that starts with https. Copy it.
- In Yirlo, open Settings, then Integrations, and add a webhook. Paste the Make URL. Yirlo accepts https addresses only, which Make URLs already are.
- Back in Make, click Run once so the scenario is listening. When the next reply arrives, Make receives it and learns the data structure from that first request.
- Add the modules that should run after the trigger, then switch the scenario on.
The payload Make receives
Both events arrive as an HTTP POST carrying a JSON payload with an identical layout: {"event": "hot_lead.received", "occurred_at": "2025-01-15T14:32:10Z", "data": {"campaign": "...", "company": "...", "email": "...", "first_name": "...", "last_name": "...", "reply": "..."}}. The event key names the type, either reply.received or hot_lead.received, and occurred_at gives the timestamp in ISO format.
After Make has received your first test request, open the mapping panel and expand the data item. The available fields are reply, campaign, company, email, last_name and first_name. Reply contains what the lead wrote, shortened to 3,000 characters, which is plenty for reading it or passing it to a text module.
If you would rather not wait for a live reply to teach Make the structure, send a sample yourself while the scenario is listening. A curl command with a body shaped like the one above, posted to your Make URL, does the job. Replace the sample values with whatever you like; Make only needs the field names.
Verifying the signature
Yirlo generates a separate secret for each webhook, and it begins with whsec_. A digest of the request body, computed with HMAC-SHA256 and that key, travels in the X-Yirlo-Signature header.
A Make webhook URL is hard to guess, but a signature check confirms that a request really came from Yirlo and that the body was not altered. In the Custom webhook settings in Make you can turn on the option to get request headers, which makes X-Yirlo-Signature available in the scenario. Compute an HMAC-SHA256 of the body with your secret, compare it to the header, and stop the scenario with a filter if they differ.
If your scenario only writes a line to a spreadsheet, you may decide the check is not worth the extra modules. If it sends messages to customers or triggers anything with cost, add it.
Scenarios worth building first
Start small. One trigger and two or three modules covers most of what a sales team needs from a reply feed.
- Instant alert for hot leads: filter on the event field for hot_lead.received and post the name, company and reply text to a chat channel so someone answers within minutes.
- Reply log: add a row to a spreadsheet or database for each reply.received event, with campaign, company and the reply text, so you can review what kinds of answers each audience produces.
- Task creation: turn each hot lead into a task on your project board, assigned to whoever owns follow-up, with the reply pasted into the description.
- Reply summary: pass the reply text to an AI module in Make and write a one-line summary next to the record, useful when replies run long.
- Daily digest: collect events in a data store and send one grouped email each morning for teams that dislike constant pings.
Using the campaign field to route replies
Yirlo proposes several campaigns for what you sell, each aimed at a different kind of buyer. The campaign name arrives with every event, so a Make router can send replies from different audiences to different people.
Say you sell a returns-management tool. One campaign might target heads of operations at online retailers, with a first email about the cost of handling returns by hand. Another might target customer experience leads at subscription brands, with an email about refund requests. Replies from the first can go to your solutions specialist, and replies from the second to the person who handles onboarding calls.
The same idea works for an agency that sells to several industries. A router with one branch per campaign name keeps each reply in front of the person who knows that market, without anyone sorting a shared inbox by hand.
Keeping the connection healthy
Yirlo waits 5 seconds for a response. Make's Custom webhook acknowledges the request right away by default, so keep the heavy work in the modules after the trigger and avoid changing the webhook response to something slow.
Status information for the most recent attempt appears in the app beside every webhook. Start there when events stop showing up in Make, then confirm the scenario is turned on and the URL saved in Yirlo is identical to the one Make gave you.
Up to 20 URLs can be registered. That allows a separate scenario for each job, say one for alerts and another for logging, rather than a single overloaded scenario.
What happens before the webhook fires
Long before a reply shows up in Make, Yirlo has already done the groundwork: it read your site, chose who to target, verified the addresses, wrote each opening email and sent it from mailboxes it manages. Every send is paid from credit you buy in advance, and you can switch on automatic card top-ups if you like.
Questions
Is there a Yirlo app in Make?
Yirlo links up with Make through the Custom webhook trigger. In the Yirlo app, open Settings, go to Integrations, and enter the URL that Make gives you.
Which events can I receive in Make?
There are two event types. The reply.received event is triggered by genuine human responses from leads. Auto-replies about being away, unsubscribe requests and flat rejections are skipped. The hot_lead.received event is reserved for responses that Yirlo rates as coming from a strong prospect.
What fields does the payload contain?
Every payload carries an event name, an occurred_at timestamp and a data section. Inside data you get the lead's email address and name, plus the company, the campaign and the reply text, which can run to 3,000 characters.
How do I check that a request came from Yirlo?
Every delivery carries a signature. Take the raw body exactly as it arrived, before any parsing, and hash it with HMAC-SHA256 and the whsec_ key issued for your webhook. Yirlo does the same on its side and writes the result into the X-Yirlo-Signature header. In your scenario, compute the hash yourself and compare it with the header value. If the two match, the call came from Yirlo.
Can I use more than one Make scenario?
Yes, an account can hold twenty webhook endpoints. That lets alerts, logging and routing each run as a separate scenario with a distinct URL and a distinct secret.
Does the URL have to use https?
Yes, Yirlo accepts https URLs only. Make's Custom webhook addresses already use https.
How can I see whether a delivery worked?
Open the app to see how the latest delivery for each webhook went. Responses must arrive within 5 seconds, and a scenario that runs slowly is the most common cause of a failure showing up there.
Can Make send data back into Yirlo?
The webhook feed goes one direction, from Yirlo to Make. A Make HTTP module can also call the Yirlo public API, for example to pause a campaign or pull the latest hot leads inside a scenario.