Skip to main content
The Notifications section lets you manage who receives alerts when events occur—like when you receive a new lead or get outbid on a buy order.

​
Adding contacts

Add phone numbers or email addresses to receive notifications. The available contact types depend on what your provider has enabled:
  • Email — Receive notifications via email
  • Phone — Receive notifications via text message (if texting is enabled)

​
Managing notifications

Click on any contact to see its notification settings. From there, you can toggle individual notification types on or off for that contact. This lets you control exactly who gets notified about what—send lead alerts to your sales team’s phones while keeping billing notifications in your inbox.

​
Webhooks

The Webhooks tab lets you send lead data to external systems whenever a lead is assigned to you.

​
Creating a webhook

  1. Click New Webhook
  2. Enter the URL where lead data should be sent
  3. Choose your HTTP method (GET, POST, PUT, PATCH, or DELETE)
  4. Optionally customize the payload template

​
Payload format

Webhooks always send JSON. By default, the payload includes the lead’s charged amount, scope, lead type, and all deliverable fields for the lead category. The default template looks like this: 
{
  "charged_amount": "{{ charged_amount }}",
  "scope": "{{ scope }}",
  "lead_type": "{{ lead_type }}",
  {{ deliverable_fields }}
}
If you need to remap or restructure the data, use the payload template field to define a custom format.

​
Template variables

Payload templates support merge fields using double curly braces: {{ variable_name }}.
VariableDescription
{{ charged_amount }}The amount charged for the lead
{{ scope }}The geographic scope of the assignment (e.g., county)
{{ lead_type }}The name of the lead type
{{ lead_category }}The name of the lead category
{{ buyer.phone }}Your phone number on file
{{ deliverable_fields }}Expands to all deliverable fields for the lead category as JSON key-value pairs
The {{ deliverable_fields }} variable is special—it expands to raw JSON key-value pairs rather than a single value. Place it inside your JSON object and it will insert all deliverable fields (like name, email, phone, etc.) directly into the payload.

​
Lead fields

Lead fields are available in two formats:
  • Flat: {{ first_name }}, {{ last_name }}, {{ email }}, {{ phone }}
  • Nested: {{ lead.first_name }}, {{ lead.last_name }}, {{ lead.email }}, {{ lead.phone }}
Both formats work identically. The nested format can be useful when you need to distinguish lead fields from other data in complex templates, or when integrating with systems that expect a specific payload structure. Custom fields from the lead category are accessible via {{ lead.details.field_name }} or directly by name if using {{ deliverable_fields }}.

​
Managing webhooks

You can enable or disable a webhook at any time without deleting it.

​
Testing webhooks

Before going live, test your webhook to verify your endpoint receives data correctly. You have two options:
  • Use an existing lead — Select a lead from your history to test with real data. Search by lead ID, name, email, or phone to find a specific lead.
  • Generate sample data — Create fake data based on a lead type. Useful when you don’t have leads yet or want to test without using real information.
Either option sends a test payload to your endpoint so you can confirm it’s working before enabling the webhook.