Send Yirlo replies and hot leads to Google Sheets

Two ways to get Yirlo data into Google Sheets

The first way is live. Yirlo sends an event to your webhook each time a real reply arrives (reply.received) and each time an interested reply becomes a hot lead (hot_lead.received). A tool in the middle catches the event and adds a row to your sheet within moments.

The second way is a one-time or occasional import. You download the lead CSV from Yirlo and load it into a sheet, which gives you every lead in the project with its campaign, status and notes in one table.

Most teams use both. The CSV gives a full picture of who was contacted, and the webhook rows keep a running log of who answered.

Prepare the sheet before you connect anything

Create one spreadsheet with two tabs, for example Replies and Hot leads. Put the column headings in row one, because Zapier, n8n and Make read those headings and offer them as targets when you map fields.

A practical set of headings is: Received at, Email, Name, Company, Campaign, Reply text, Owner and Follow-up date. The first five and the reply text come from Yirlo. Owner and Follow-up date stay empty on arrival so a person on your team can fill them in.

Keep the Hot leads tab short and easy to scan. A founder who checks it every morning wants to see the email, the company and what the person wrote, then decide who gets a call.

Zapier: Catch Hook to Google Sheets

Zapier receives the Yirlo event with Webhooks by Zapier. Follow these steps for each event type, or build one Zap for hot leads and a second for all replies.

• Open Zapier, make a Zap, and pick the Webhooks by Zapier app for its trigger step, then Catch Hook as the event type. Zapier generates a custom URL, so copy it.
• Switch back to the Yirlo app and register the URL you just copied as a fresh webhook endpoint. Pick the event that should fire it: a reply coming in, or a lead being flagged as hot.
• Fire a test event from Yirlo's webhook screen. Zapier picks up a sample payload and shows its fields, ready to choose from in the next step.
• Add an action: Google Sheets, then Create Spreadsheet Row. Choose your spreadsheet and the tab.
• Link each sheet column to a sample field, such as the lead's name and email, their company, the campaign, and what the reply said.
• Test the action, check the row in the sheet, then publish the Zap.

n8n: Webhook node to Google Sheets node

In n8n, start a new workflow and make a Webhook node the opening step, configured for POST. n8n displays a production URL. Paste that into Yirlo as the destination. While n8n waits for data, use the send-test-event option in Yirlo.

Add a Google Sheets node after it, choose the operation that appends a row, and select the document and sheet. Map each column from the webhook data. Activate the workflow so the production URL stays live.

n8n can also verify authenticity. Put a Code node in front of the sheet step that hashes the unmodified request body with HMAC-SHA256 and checks the result against the header named X-Yirlo-Signature. Only genuine Yirlo events then produce rows.

Make: Custom webhook to Google Sheets

In Make, create a scenario that begins with the Webhooks module and its Custom webhook trigger. Make generates an address; paste it into Yirlo and choose the event.

Run the scenario once so it waits for data, then click Send test event in Yirlo. Make reads the sample and learns the structure, which is what makes the fields selectable later.

Add the Google Sheets module that adds a row. Pick the spreadsheet and tab, map the columns to the webhook fields, and switch the scenario on. If you want replies and hot leads on separate tabs, create two scenarios with one webhook each, which keeps each mapping simple.

Fields available for each row

Every webhook event includes the lead's email address, name and employer, along with the reply wording and the campaign behind it. With that you can tell who answered, where they work, which audience they belong to and what they said.

The CSV export of leads carries more columns. Contact fields are email, name, job title and LinkedIn profile. Company fields are company name, website, industry and size. Each row also records the deal status, a note, the conversation, the campaign and the lead's status, and the location comes as city, state and country. Industry, company size and location work well as filters in a sheet, for example to check whether replies cluster in one state or one size band.

A phone number column is coming soon, along with other contact details. For now the sheet is built around email, company and the conversation.

Import the full lead CSV into Google Sheets

Download the lead CSV from Yirlo. In Google Sheets, open File, then Import, then Upload, and drop the file in. Choose to insert a new sheet if you want to keep your existing tabs untouched, or replace the current sheet for a fresh copy.

Once the data is in, a few habits help. Freeze the header row, add a filter view on the status column, and sort by campaign to compare how each audience performed. A pivot table on campaign and status gives a quick count of replies per campaign without any formulas.

The CSV is a snapshot. Download it again when you want a fresh copy, and use the webhook rows for anything that should update as replies come in.

Reading hot leads on a schedule instead

You can also fetch the data yourself. The endpoint reference lives at yirlo.com/api-docs. A morning schedule in n8n, or a time-driven Apps Script trigger, can then append whatever is new as rows in a tab.

The webhook is simpler when you want each row the moment it happens. The scheduled read suits a daily digest sheet. A listed Yirlo app for Zapier, n8n and Make is coming soon, which will shorten the setup further.

Questions

Related