Yirlo Zapier integration: send replies and hot leads anywhere
By the Yirlo team · Product details checked against the app
Yirlo can forward each incoming lead response, along with every one it flags as a hot lead, to a Zapier Catch Hook as soon as it lands. A Zap on the other end might append a spreadsheet row, create a CRM contact or post to a chat channel. Setup is a one-time paste of a URL in the app.
How Yirlo and Zapier connect
Yirlo connects to Zapier through a webhook, which works with any Zap you build. In Zapier you start a Zap with the trigger Webhooks by Zapier, choose Catch Hook, and Zapier gives you a URL. You paste that URL into Yirlo, and every event Yirlo sends lands in that Zap.
The Zap is the bridge between Yirlo and your CRM: whatever app Zapier can write to, your replies can reach.
Two events are available to subscribe to today. reply.received goes out whenever a lead sends a genuine response, while auto-replies such as out-of-office messages, unsubscribes and flat refusals are skipped. hot_lead.received goes out only when Yirlo classifies a reply as real buying interest.
Set up the Catch Hook in five steps
The whole setup takes a few minutes if you already have a Zapier account. Here is the order that avoids most mistakes.
- In Zapier, create a new Zap and pick Webhooks by Zapier as the trigger app, with Catch Hook as the event.
- Copy the custom webhook URL Zapier shows you. It starts with https, which is the only kind Yirlo accepts.
- Inside the app, go to the Integrations page under Settings and register your Zapier hook address as a new webhook. Up to 20 webhook addresses fit on one account, so another Zap or a different tool can receive the same events in parallel.
- Wait for a real reply, or post a sample payload to the Catch Hook URL yourself so Zapier has fields to map. Then use Test trigger in Zapier.
- Add your action steps, switch the Zap on, and check the webhook's last delivery status in Yirlo to confirm Zapier accepted the call.
What each webhook contains
Deliveries are POST requests with a JSON body. Here is a sample for a hot lead: {"data": {"company": "Bellwether Logistics", "campaign": "Mid-size 3PL operators", "first_name": "Marcus", "last_name": "Bell", "email": "[email protected]", "reply": "Yes, send me times for Thursday."}, "event": "hot_lead.received", "occurred_at": "2025-06-12T14:03:22Z"}.
Inside data you get the person's name, address, employer, the campaign that found them and what they wrote back. Replies are truncated at 3,000 characters, well beyond what typical replies need. In Zapier, every one of these values shows up as its own field, ready to map into later steps.
The event field tells you which of the two events you received. If you only want hot leads in a Slack channel, add a Filter step after the trigger that continues only when event equals hot_lead.received.
Where the replies can go
Most teams send the same payload to three kinds of places. Each one solves a different problem, and you can run all three from separate Zaps.
A spreadsheet is the simplest log. A Google Sheets or Airtable step can append one row per reply with the date, company, campaign and reply text. After a few weeks you can sort by campaign and see which audiences produce answers, which complements the results email Yirlo sends three times a week.
A CRM is where a reply becomes a record. Use the email as the match key so Zapier updates an existing contact when one exists and creates one when it does not. Put the campaign name in a source or note field, and the reply text in a note, so whoever follows up sees the actual words.
A chat channel is for speed. A hot lead posted to Slack or Microsoft Teams with the name, company and reply gets seen within minutes by the person who can book the call. Yirlo also emails hot leads to you, so the channel message reaches a whole sales group rather than one inbox.
Examples by type of seller
The routing you want depends on who you sell to. These are illustrations of how a Zap might be arranged, not customer stories.
Suppose you sell payroll software to companies with 20 to 200 employees. Yirlo might build one campaign for staffing agencies and another for regional construction firms, with a first email about how each handles weekly pay runs. Replies from the agency campaign can go to one rep's CRM pipeline, and replies from the construction campaign to another. A Filter step on the campaign field does the split.
Suppose you sell security audits to SaaS companies. A reply like "We just did one, ask again in Q4" is a real reply but not a hot lead. Sending reply.received to a spreadsheet lets you see these and set a reminder, while hot_lead.received goes straight to Slack.
Suppose you sell packaging to e-commerce brands. Replies often ask about minimum order quantities. A Zap can post the reply text to a channel so the person who knows pricing answers quickly, even when Yirlo has already drafted a reply toward your goal.
Security and delivery details
Every webhook gets its own random secret that starts with whsec_. When Yirlo makes a delivery, it computes an HMAC-SHA256 hash of the unmodified request body, keyed with that secret, and puts the result into a header named X-Yirlo-Signature. Your own server or script can recompute the hash and compare. If the two values are equal, the request came from Yirlo and the body was not altered.
Zapier's Catch Hook URL contains a long token that is hard to guess, so treat the URL like a password and do not paste it into shared documents. If you ever post to your own server as well, verify the signature there.
Yirlo waits 5 seconds for a response. Zapier's Catch Hook answers quickly, so this is rarely an issue, but heavy processing belongs in later Zap steps and not in the receiving endpoint. Each webhook in Settings > Integrations shows its last delivery status, so a mistyped URL or a switched-off Zap shows up there.
n8n and Make work the same way
If your team uses another automation tool, the steps are the same. In n8n, add a Webhook node and paste its production URL into Yirlo. In Make, create a Custom webhook and paste that URL. Neither has a Yirlo app listing today, so each tool uses its own generic webhook trigger.
Because you can add up to 20 URLs, you can send the same events to Zapier for the sales team and to n8n for a workflow that your operations team maintains.
What stays inside Yirlo
The webhook delivers replies and hot leads to your Zap. Targeting companies, writing first emails, sending from the mailboxes Yirlo manages and drafting follow-ups all run inside the app. When a Zap should act on an event, the Yirlo API (X-API-Key) lets it read a conversation, send a reply, add a note, update a lead status, or start and stop a campaign. The full inbox and every campaign and email can also be edited in the app.
Billing is about $0.05 for every email Yirlo sends, paid from your prepaid balance. The webhook itself is free of charge. Whatever task and plan limits Zapier applies still count separately.
Questions
Is there a Yirlo app in the Zapier directory?
Yirlo connects through Webhooks by Zapier today. Pick the Catch Hook trigger and paste the URL it gives you into Settings > Integrations in Yirlo.
Which events can I send to Zapier?
Two trigger events are available in Zapier. The reply.received event fires each time a prospect sends back a real response. The hot_lead.received event fires only when Yirlo judges that a message shows obvious interest in buying. Out-of-office messages, opt-outs and plain rejections stay out of both.
What fields will I see in the Zap?
Each payload names the event and gives a timestamp, followed by a data section. That section holds the company, the campaign, the person's name and email address, and the reply text, which can be up to 3,000 characters long.
Can I send leads straight into my CRM?
Yes, through a Zap. Zapier takes the fields from the webhook and creates or updates a contact in the CRM you choose, so replies and hot leads arrive as records.
Do I have to use https?
Yes. Yirlo only accepts https webhook URLs, and Zapier's Catch Hook URLs already use it.
How many webhooks can I add?
Up to 20 URLs. You can point several at different Zaps, or mix Zapier with n8n or Make.
How do I verify a request came from Yirlo?
Every webhook comes with a secret that begins with whsec_. For each delivery, Yirlo runs the raw payload through HMAC-SHA256 keyed with that secret and sends the digest in a header named X-Yirlo-Signature. To verify that a delivery came from Yirlo, calculate the same digest on your own server and check that it matches the header value.
How do I know if a delivery failed?
Open Settings > Integrations to see whether the most recent attempt to reach each webhook succeeded. Yirlo gives up on a response after 5 seconds, so confirm the Zap is turned on and the URL was pasted correctly.
Can I get only hot leads in Slack?
Yes. Add a Filter step in the Zap that continues only when the event field equals hot_lead.received, then add a Slack step that posts the name, company and reply.