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, and FAQs for picking the right delivery for each buyer.

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 HMAC-SHA256 signing for verification. The default choice for serious buyers.

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

Each buyer has one primary delivery method (Webhook, Email, or Google Sheet) plus any number of automations attached to lead.accepted events. Automations can fan out to additional destinations: Slack alerts, secondary CRMs, internal dashboards, SMS notifications. Primary delivery and automations run in parallel; one failing doesn't block the others.

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.
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 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.

Related Articles

Buyer Basics
Manage buyers in Lead Distro AI: delivery methods, lead caps, pricing, state and field filters, white-label client portals, and real-time acceptance rules for every buyer in your lead operation.
State Filters
Route leads to Lead Distro AI buyers based on US state coverage. State allowlists, multi-state buyers, combining with zip and custom filters, and FAQs.
Integration Patterns
Lead Distro AI integrations: Zapier, Make, Google Sheets, Slack, HubSpot, Salesforce, Clio, and custom webhooks. Connect your lead distribution pipeline to every tool in your agency stack.

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

Manual Billing ModeState Filters