Salesforce integration: hot leads and replies from Yirlo, logged as leads and tasks

What arrives in Salesforce

Your webhook endpoint gets two kinds of events from Yirlo. A reply.received event goes out whenever a genuine reply comes in, and a hot_lead.received event goes out once that reply has been labeled interested. The payload names the lead, shows their email and company, points to the originating campaign, and includes the text they wrote.

Most teams point both events at Salesforce but build different actions for each. A hot lead becomes a record plus a task with a due date. A routine reply can be a note or a field update on a record that already exists.

• Email: the match key for finding an existing lead or contact
• Name: becomes the lead's first and last name
• Company: fills the required Company field on a Salesforce lead
• Campaign: shows which audience and angle produced the reply
• Reply text: goes into the task description or a long text field

Before you start

You need a Yirlo project with at least one campaign, a Salesforce login that can create leads and tasks, and an account in Zapier, n8n or Make. Pick one of the three. The flow is the same in each: a webhook trigger, a lookup, a create step, a task step.

Decide up front whether new people should become leads or contacts. Cold outbound usually produces people Salesforce has never seen, so a lead is the natural record. If the person already sits in an account as a contact, the lookup step below attaches the task to that contact and skips the duplicate.

Step by step with Zapier

Open Zapier, make a Zap, and choose the Catch Hook option in its Webhooks app. Zapier gives you a URL of its own. Paste that into a new webhook in the Integrations section of Yirlo and select the hot lead event. Press the test event button in Yirlo, and a sample payload arrives in Zapier so you can map the fields.

Add a Salesforce step that looks up a contact by email, then another that looks up a lead by email. Add a Salesforce step that creates a lead, run only when both lookups come back empty. Set Last Name from the name field (a Formatter step can split a full name), Company from the company field, Email from the email field, and Lead Source to Yirlo.

Add a final Salesforce step that creates a task. Set the subject to something like Reply from the lead's name at their company, put the reply text in Description, set the due date to today, and link the task to whichever record the earlier steps found or created. Turn the Zap on.

Step by step with n8n

In n8n, drop a Webhook node onto the canvas, choose POST as its method, and give Yirlo the node's production URL. While you are building, use the node's test URL instead and trigger a sample from Yirlo. The payload shows up in the node, and you can drag its fields into the nodes that follow.

Next, add a Salesforce node that searches leads by email and a second search for contacts. An IF node sends the flow down a create branch when both searches return nothing. In the create branch, a Salesforce node creates the lead with Last Name, Company and Email from the webhook. A final Salesforce node creates the task with the reply text in the description.

n8n can also verify authenticity before it writes anything. Insert a Code node that hashes the body exactly as received using HMAC-SHA256 and your signing secret, then check the result against the signature header Yirlo attaches to each call. If the two differ, end the workflow, and spoofed calls never reach your CRM.

Step by step with Make

Create a scenario that starts with the Webhooks module and choose Custom webhook. Add a new webhook, copy its address into Yirlo, and press Send test event. Make reads the sample and builds the data structure, so the fields show up as mappable items in the next modules.

Add a Salesforce module to search for records by email, then a router with two routes. One route handles a record that already exists and creates only the task. The other route creates a lead first and then the task. Map the reply text into the task's Description in both routes, and set Lead Source to Yirlo on new leads.

Run the scenario once from the test event, check the records in Salesforce, then switch scheduling to immediate so each webhook is processed as it arrives.

Mapping fields and keeping data clean

Salesforce requires a Last Name and a Company on every lead. Yirlo sends a name and a company for each person, so both can be filled from the webhook. If a name arrives as a single string, split it in the automation tool so the last word becomes the Last Name.

Put the campaign into a custom text field on the lead, or add it to the start of the task description. Later you can report on which audience and which first-email angle produce the most opportunities. A short line such as Campaign: and then the campaign name works well.

If you want richer records, download the lead CSV. Along with the contact's email and name, it carries job title, company website, LinkedIn profile, industry, company size and location down to city, state and country. It also shows the campaign, status, conversation, deal status and a note. The Salesforce Data Import Wizard can load the file and fill any gaps in the webhook payload. A scheduled job is the other route: it can call the Yirlo API on a timer to pull hot leads and read inbox conversations.

How reps use the result

Yirlo reads each reply, labels it and drafts an answer that points toward your goal, such as a booking link. Reps often see the prospect's reply in Salesforce while the conversation continues in Yirlo's inbox. The task description holds what the prospect wrote, so the rep opens the task and already knows the context.

Each company receives email at just one decision maker, so a company's activity lands in Salesforce under a single contact, which keeps your records tidy. Sending is billed at around $0.05 per email against prepaid credit. Whichever of Zapier, n8n or Make you prefer, it can pass hot leads and replies into Salesforce today by listening for Yirlo's webhooks.

Questions

Related