Delivery methods
The four ways a buyer can receive leads — email, webhook, Google Sheets, SMS — and how several delivery methods on one buyer work together.
A delivery method is how one buyer actually receives its leads. There are four types: email, webhook, Google Sheets and SMS. A buyer can have several, and they all fire for the same lead.
Manage them under Buyers → the buyer → Delivery methods.
The four types
| Type | What you set up | What the buyer gets |
|---|---|---|
| Recipient (leave empty to use the buyer's own address), subject and body — see Email deliveries | One email per lead | |
| Webhook | An https:// URL, optional headers, optional custom body — see Webhook deliveries | One POST with a JSON body per lead |
| Google Sheets | Share your sheet with the service account address shown on the page, then paste the spreadsheet ID and tab name | One row appended per lead; column headers are created automatically on the first lead |
| SMS | Sending and receiving numbers, plus a message template using {{lead.firstName}}-style variables. Requires a Twilio account connected in Settings → Integrations | One text message per lead |
Every delivery method carries its own list of fields to send. That list, and the formatting of each value, is covered in Field mapping and transforms.
Several methods on one buyer
Delivery methods are not a fallback chain. A lead routed to the buyer is sent through every targeted active method at once — add an email and a Google Sheet and the buyer gets both.
- Priority (lower number first) sets the order they are listed and dispatched in.
- Active / Inactive is the on-off switch. An inactive method never receives anything.
- The delivery is marked delivered as soon as one method succeeds. If another failed, the delivery history shows
Partial: 1 of 2 endpoints failedwith the error. It only counts as failed when they all fail.
Which methods a routing rule targets
By default a routing rule delivers to all of the buyer's active methods. To send only to some of them, pick a subset under Delivery targets in the rule (Routing rules).
A method no rule targets shows a Not used — won't deliver badge in the list: it's configured but nothing reaches it yet.
Reuse and testing
Each type has a test action on its page — preview the exact webhook payload without sending, send a real test to the buyer's URL, send a test email, or check the Google Sheets connection. Use Duplicate to buyer… (or Duplicate from a client when creating) to copy a working setup to another buyer instead of rebuilding it.
Common questions
One method failed, another worked. Was the lead delivered? Yes. The delivery is delivered and billable as soon as one method succeeds; the failure is recorded next to it as a partial error.
Can I stop a buyer receiving leads without deleting anything? Switch its delivery methods to Inactive, or pause the buyer in the pipeline from its routing rule. Both are reversible and keep the configuration.
Why does my new delivery method say "Not used — won't deliver"? No routing rule targets it. Either the buyer isn't in a pipeline yet, or the rules that use it have an explicit delivery-target list that excludes it.
Which method is used when a buyer has three? All three, in parallel. Priority only orders them; it doesn't make one a backup for another.