Send qualified Sendpilot leads to Liteo

Create a Liteo connection, then route qualified Sendpilot leads through your automation tool.

Reviewed September 15, 2026

Browse all guides
On this page

Send qualified Sendpilot leads to Liteo through Zapier, Make, Pabbly, or n8n. The workflow creates one lead contact and keeps later updates tied to the same person.

Do not use every reply as the trigger. Replies can be negative, automated, or from the wrong person. Instead, have a person mark the lead Interested in Sendpilot.

Before you connect

You need:

  • admin access to your Liteo workspace;
  • a Sendpilot plan with API and webhook access;
  • a Sendpilot API key;
  • an automation tool that can receive a webhook and make HTTP requests;
  • Interested as the Sendpilot status that hands a lead to Liteo.

This recipe uses Sendpilot's lead.updated event. A live test confirmed that this event does not include the visible Interested status, so the workflow must look up the lead before it filters.

Create the Liteo connection

  1. In Liteo, open Settings, then choose Integrations.
  2. Find Sendpilot and select Set up Sendpilot.
  3. Choose who should own new leads.
  4. Select Create connection.
  5. Copy the connection code before you close the dialog.

Receive the Sendpilot event

Create a webhook trigger in Zapier, Make, Pabbly, or n8n. Copy its HTTPS webhook address into Sendpilot and subscribe to Lead Updated (lead.updated).

Run a test from Sendpilot. Confirm that the captured event includes these stable values:

  • eventId;
  • workspaceId;
  • data.campaignId;
  • data.leadId;

Stop here if any of those values are missing. Names, company names, and LinkedIn slugs are not safe identity fields.

Fetch the lead

Sendpilot's single-lead endpoint did not resolve the ID emitted by the webhook in our live test. Use the campaign lead-list endpoint instead:

Method: GET
URL: https://api.sendpilot.ai/v1/leads?campaignId={{data.campaignId}}&page=1&limit=100
Header: X-API-Key: YOUR_SENDPILOT_API_KEY

Find the item in leads whose id exactly equals data.leadId from the webhook. If pagination.totalPages is greater than 1 and the item is not on the first page, request each later page until you find it.

Stop the run if no exact ID is found or firstName is empty. The response supplies the lead's name, title, company, LinkedIn URL, and customLeadStatus; do not invent a placeholder name.

Filter for a qualified lead

Continue only when the matched lead's customLeadStatus exactly equals INTERESTED. Stop the run for LEAD, WRONG_PERSON, NOT_INTERESTED, NO_RESPONSE, or any other value.

Do not filter on data.newStatus from the webhook. A live Lead to Interested change emitted DONE to DONE there, while the lead-list response correctly returned customLeadStatus: INTERESTED.

Do not use a reply, connection acceptance, or message event as the default trigger. Those events do not prove the lead is qualified.

Import the lead into Liteo

In Zapier, choose Liteo's Import Lead action. Map the fields below.

Liteo fieldSendpilot value
Source event IDeventId from the webhook
Providersendpilot
Provider account IDworkspaceId from the webhook
External lead IDdata.leadId from the webhook
Lead statuscustomLeadStatus from the matched lead
Qualified statusINTERESTED
Profile URLlinkedinUrl from the lead response
First namefirstName from the lead response
Last namelastName from the lead response
Job titletitle from the lead response
Company namecompany from the lead response
SourceSendpilot

You can add an existing Liteo tag such as Qualified. The workflow does not create tags, tasks, deals, pipelines, or custom fields for you.

For Make, Pabbly, or n8n, send the same values to POST /v1/inbound/leads. Use the Liteo connection code as a Bearer token and map eventId to the Liteo-Idempotency-Key header.

Test the workflow

Mark one test lead Interested, then run the captured event through the complete workflow twice. Both runs should return the same Liteo contact.

Check the contact in Liteo. Confirm its owner, source, optional tag, and LinkedIn profile link before enabling the workflow.

Disconnect Sendpilot

Open Settings, choose Integrations, then find the Sendpilot key. Select Revoke key to stop later imports.

Revoke the Sendpilot API key in Sendpilot separately. Contacts already added to Liteo stay in place.

Still stuck?

Tell us what you expected and what happened. We’ll help you find the cause.

Email hello@liteo.io