Lead Distro AILead Distro AI
DocsBuyersDelivery Methods

Delivery Methods

Lead Distro AI buyer delivery methods — Webhook (JSON POST), Email, Google Sheet. How each works, when to use which, how Parse Post Response decides which replies count as accepted (including OR and AND rules), and FAQs.

Last updated:

Three Delivery Methods

MethodHow it worksBest for
WebhookJSON POST to any URLCRMs (HubSpot, Salesforce, Clio, GHL), automation platforms (Zapier, Make), custom internal endpoints
EmailEmail notification with lead detailsBuyers without a CRM, low-volume manual intake, paper-trail compliance
Google SheetLead appended as a new rowBuyers who run on spreadsheets, simple intake without CRM setup

Webhook Delivery

Sub-second latency from lead acceptance to POST. Full JSON payload with system fields + custom fields. Works with any tool that accepts incoming webhooks. Supports Basic, Bearer, API key, and OAuth 2.0 authentication. The default choice for serious buyers.

Parse Post Response: Choose Which Destination Replies Count as Accepted

Open a destination on the campaign's Routing tab and scroll to Parse Post Response. Set the Accepted rule to the reply field and value that mean the destination took the lead, for example status equals accepted. Without an Accepted rule, every 2xx reply counts as accepted and billable.

A reply that does not match the Accepted rule is recorded as Rejected, with the destination's reason on the lead. Turn on the Duplicated rule to record a destination's duplicate reply as Duplicate instead. Parse Post Response has three outcomes: Accepted, Duplicated and Rejected.

Use OR and AND Rules in Parse Post Response (Advanced Expression)

Yes, Parse Post Response can check several conditions. In Routing → your destination → Parse Post Response, set Response Format to JSON and the Accepted rule's operator to advanced expression. Then write one rule that uses or, and and not.

Lead_Status == "Accepted" or (Test_Mode == true and Lead_Status == "Filtered")
  • This advanced expression accepts a live lead only when Lead Status is Accepted. It also passes a destination test when the destination's own reply says Test Mode is true and Lead Status is Filtered.
  • In an advanced expression, spaces and symbols in a field name become _. A reply field called Lead Status is written Lead_Status. A nested field uses a dot path, such as result.status.
  • An advanced expression compares with ==, !=, <, <=, > and >=. Text goes in double quotes. true, false and null need no quotes.
  • A field missing from the reply never matches, so a missing field can never turn a lead into Accepted.
  • The Duplicated rule offers advanced expression too, for example Lead_Status == "Duplicate".
  • Use the test panel under the advanced expression, or Execute Test, to check the rule against a real reply. Execute Test and live leads use the same rule.

Advanced expression works only when Response Format is JSON. For an XML or Text reply, use one Accepted rule with equals, contains, not equals or exists.

Email Delivery

Sends a formatted email to the buyer's address with lead details. Useful for buyers without a CRM or for compliance contexts where the buyer needs an email trail of every received lead. Latency is ~1-2 seconds. Limited to plain-text or templated HTML; no programmatic ingestion downstream.

Google Sheet Delivery

Authenticates once via Google OAuth, then every lead appends as a new row in the buyer's spreadsheet. Columns auto-populate from the campaign's field mapping. Useful for buyers who don't run a CRM but want structured intake — common for solo practitioners and small intake teams.

Most buyers should use Webhook delivery — it's the fastest, most flexible, and most integrate-able. Email is for non-technical buyers who can't or won't set up a webhook receiver; Google Sheet is for buyers who explicitly prefer spreadsheets. Default to Webhook unless the buyer asks for something else.

Combining Primary Delivery + Automations

A destination can use several delivery methods at once. Each one is a tab under Delivery Methods in the destination's settings: add one with + Add method, remove one with the x on its tab. When a Webhook is set, its reply decides whether the lead was accepted, and Email, Google Sheet and GHL send only after it accepts. A destination has at most one Webhook; to send the lead to more URLs, add automations on lead.accepted (Slack alerts, secondary CRMs, internal dashboards).

Frequently Asked Questions

What delivery methods does Lead Distro AI support for buyers?
Three primary delivery methods: Webhook (JSON POST to any URL — works with CRMs and automation platforms), Email (notification with lead details — for non-technical buyers), Google Sheet (appended as a new row — for spreadsheet-driven intake). Buyers can also attach automations on top of primary delivery for parallel fan-out (Slack alerts, secondary CRMs, SMS).
Can a buyer use multiple delivery methods at the same time?
One primary delivery method per buyer, plus unlimited automations. So a buyer with Webhook as primary can also have Slack alerts, an email-copy automation, and a Google Sheet append all running in parallel on lead.accepted events. The primary handles the canonical delivery; automations are for secondary destinations.
What's the latency of webhook delivery vs email delivery?
Webhook: typically under 500ms end-to-end from lead acceptance to POST. Email: 1-2 seconds due to SMTP routing. Google Sheet: ~1 second (Google Sheets API write). For time-sensitive verticals (legal intake, home services emergencies, mortgage rate locks), webhook is the right default; for low-urgency intake email is fine.
Which address does email delivery send from?
From your own address when you connect one in Settings → Integrations → Email Sending (Gmail, SendGrid or any SMTP provider). Without one, it sends from the Lead Distro AI address. Each Email delivery method shows a Sent from line with the address it uses, and a link to change it. The Sender Name below it is the name people see. If your own server refuses a send, that email goes out from the Lead Distro AI address instead, and the line says so.
Can I customize the email delivery format?
Limited — Lead Distro AI uses a standard template with lead details, source, and timestamp. Custom HTML templates are not natively supported today (on the roadmap). For fully custom email formats, use Webhook delivery to an automation platform (Zapier, Make) that formats and sends a custom email — more work to set up but unlimited template flexibility.
How does Google Sheet delivery handle high-volume campaigns?
Lead Distro AI batches appends to respect Google Sheets API quotas. For low-to-medium volume (<1,000 leads/day per sheet), real-time append works fine. For high-volume (10,000+/day), Google Sheets becomes a bottleneck — switch to Webhook delivery to a database or to a Google Sheet via Zapier with its own queue. The 5M-row limit in Google Sheets is also a long-term concern for sustained high-volume.
Can Parse Post Response use OR rules or more than one condition?
Yes. Open the destination on the campaign's Routing tab, go to Parse Post Response, set Response Format to JSON, and set the Accepted rule's operator to advanced expression. Write one rule with or and and, for example Lead_Status == "Accepted" or Lead_Status == "Sold". Spaces in a field name become _. Advanced expression works for JSON replies only.
How do I make a destination test pass when the destination answers "Filtered" in test mode?
Use an advanced expression on the Accepted rule under Routing → your destination → Parse Post Response: Lead_Status == "Accepted" or (Test_Mode == true and Lead_Status == "Filtered"). Live leads still need Accepted. The test passes only when the destination's own reply says Test Mode is true. Destination tests are never leads and are never billed.
A destination said "Duplicate" but the lead shows as Rejected. How do I fix that?
Its Duplicated rule (under Parse Post Response in the destination's settings) is reading a different field than the one the destination used. Open the lead, go to Logs, and expand that delivery. When the reply is JSON, the yellow This looks like a duplicate box has a Fix the Duplicated rule button. It opens the destination's settings with the rule already filled in (for example errors.0.error equals Duplicate) and shows the old rule next to the new one. Nothing changes until you press Save. The new rule applies to the next lead; leads already sent keep their status.
Can buyers switch delivery methods without re-onboarding?
Yes — change the delivery method on the buyer detail page. Change takes effect on the next ingested lead. For a buyer switching from Email to Webhook, configure the webhook URL first, set up the receiver, then flip the delivery method. Test Send a sample lead before switching to confirm the new delivery path works.

If you have any questions, send us an email at support@leaddistro.ai