Delivery Channels

Delivery channels define how leads are sent to partners when distribution rules match. Leadflip supports email and webhook delivery. Each partner can have one primary delivery channel configured per profile.

Email Delivery

Email delivery sends leads to the partner's email address as formatted messages.

• Recipient – The partner's email (from their profile or overridden per profile).
• Format – Typically CSV or a formatted HTML/text body. You can configure which fields are included.
• Subject – Customizable subject line (e.g., "New Lead: {{lead_name}}").
• Attachment – If CSV, the lead data may be attached as a file.
• Batching – Some setups support batching multiple leads into one email (e.g., hourly digest).

Use case: Partners who prefer simple email notifications and don't have an API.

Webhook Delivery

Webhook delivery sends leads via HTTP POST to a URL the partner provides.

• URL – The partner's endpoint (e.g., https://partner.example.com/webhooks/leads).
• Method – HTTP POST (typical).
• Payload format – JSON or form-encoded. The payload includes lead fields as key-value pairs.
• Headers – Optional custom headers (e.g., API key for authentication).
• Retries – Failed deliveries may be retried (configurable).

Use case: Partners with systems that can receive and process leads automatically (CRMs, internal tools).

Configuring a Delivery Channel

1. Open the Distribution Profile and select the Partner.
2. Go to Delivery or Delivery Settings.
3. Choose Email or Webhook.
4. For Email: Enter recipient, subject template, and format options.
5. For Webhook: Enter URL, select payload format, add headers if needed.
6. Save. Test the delivery if possible (e.g., send a test lead).

Field Selection

For both channels, you can choose which lead fields to include:

• All fields – Send every field from the Entity.
• Selected fields – Pick specific fields (e.g., name, email, phone, custom fields).
• Encrypted fields – If included, they are decrypted before sending (ensure you have proper data handling agreements with partners).

Security Considerations

• Webhooks – Use HTTPS for webhook URLs. Consider adding a secret token in headers for verification.
• Email – Sensitive data in email may be a compliance concern; use webhooks for PII when possible.
• Audit – Delivery logs are stored for debugging and compliance.

Next Steps

• Add partners to profiles
• Manage partner details
• Set up the partner portal