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.
Three Delivery Methods
| Method | How it works | Best for |
|---|---|---|
| Webhook | JSON POST to any URL | CRMs (HubSpot, Salesforce, Clio, GHL), automation platforms (Zapier, Make), custom internal endpoints |
| Email notification with lead details | Buyers without a CRM, low-volume manual intake, paper-trail compliance | |
| Google Sheet | Lead appended as a new row | Buyers 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 StatusisAccepted. It also passes a destination test when the destination's own reply saysTest ModeistrueandLead StatusisFiltered. - In an advanced expression, spaces and symbols in a field name become
_. A reply field calledLead Statusis writtenLead_Status. A nested field uses a dot path, such asresult.status. - An advanced expression compares with
==,!=,<,<=,>and>=. Text goes in double quotes.true,falseandnullneed 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?
Can a buyer use multiple delivery methods at the same time?
What's the latency of webhook delivery vs email delivery?
Which address does email delivery send from?
Can I customize the email delivery format?
How does Google Sheet delivery handle high-volume campaigns?
Can Parse Post Response use OR rules or more than one condition?
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?
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?
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?
Related Articles
If you have any questions, send us an email at support@leaddistro.ai