Email Notifications Integration

A Notification Destination, Not a CRM

Email Notifications is the simplest LeadSync destination -- and the right one when your follow-up workflow lives in someone's inbox rather than in a CRM. The moment a Facebook, Google, LinkedIn, or TikTok lead is submitted, LeadSync sends a formatted email to whichever recipient list you configure, with every lead form field laid out as label: value rows so the recipient can read the lead at a glance and reply / call / forward without opening any dashboard.

Where a CRM destination creates a structured contact record (and triggers automated nurture, scoring, segmentation, etc.), the email destination just delivers the data to humans -- one email per lead, sent through LeadSync's transactional email infrastructure. Useful for solo operators, small sales teams, agency client handoffs, and any workflow where the inbox is the pipeline.

Multiple Recipients, Comma-Separated

A single connection can deliver to as many recipient addresses as you need -- enter them as a comma-separated list in the Email field. Useful patterns: a sales rep plus a manager (for visibility), a sales pod plus a dedicated leads@ shared inbox (so the lead is searchable later), or one address per agent on a small team (so everyone sees every lead simultaneously and the fastest responder wins).

For agencies running paid social on behalf of clients, the recipient list is also the cleanest handoff: put the client's sales address on the connection and they receive the lead directly, while you can include your own monitoring address on the same line for QA. Each recipient gets the same email payload -- there's no per-recipient branching or conditional logic.

Customisable Subject, Introduction, Signature, and Logo

On paid plans, the email template is fully editable from the LeadSync settings: a custom subject line (with #form and #page placeholders that interpolate the lead form name and the originating Facebook Page), a custom introduction paragraph above the lead data, a custom signature block below it, and an optional logo embedded inline as a CID image attachment. Unlimited-plan users can also customise the From address so emails arrive branded with your own domain.

For Meta lead workflows with CAPI Conversions API enabled, every email also includes lead-scoring buttons (Good / OK / Poor) at the bottom -- one click sends the quality signal back to Meta as an event, helping the algorithm optimise future ad delivery toward higher-quality prospects without you opening a separate scoring tool.

Frequently Asked Questions

There is no hard cap. Enter a comma-separated list in the Email field on the connection settings, and LeadSync sends the same payload to every recipient on every new lead. Common patterns: rep + manager, sales pod + shared leads@ inbox, or every agent on a small team for race-to-respond workflows.

Subject line at the top (your custom template with #form and #page placeholders interpolated), then a brief introduction paragraph, then every lead form field laid out as Label: Value rows, then your signature block, then -- for Meta leads with CAPI enabled -- lead scoring buttons (Good / OK / Poor). Recipient sees the full lead at a glance and can reply, call, or forward immediately.

Yes (paid plans). Set a custom subject template in your LeadSync settings using #form (replaced with the lead form name) and #page (replaced with the originating Facebook Page name). Example: "New lead from #form on #page" gives every notification a contextualised subject so inbox triage stays sane.

Yes. Paid plans support a custom logo (uploaded once and embedded inline as a CID attachment), a custom signature (HTML), and a custom introduction paragraph. Unlimited plans additionally allow customising the From email address so notifications arrive from your own domain rather than the default LeadSync sender.

Yes -- every field on the lead form is rendered as a Label: Value row. The label is auto-derived from the field key (so "preferred_contact_time" becomes "Preferred Contact Time"). On paid plans you can hide specific metadata keys (ad_id, campaign_id, etc.) from the email body if you want a cleaner read.

For Meta (Facebook / Instagram) leads on accounts with CAPI Conversions API enabled, each lead email includes Good / OK / Poor buttons. Clicking a button sends a quality signal back to Meta as a server-side event, which helps Meta's algorithm optimise future ad delivery toward higher-converting prospects. The buttons can be turned off per-list if you don't want them.

Yes. Toggle the Send CSV option per list and LeadSync attaches a one-row CSV (named new_<form_name>_lead.csv) alongside the inline body. Useful when downstream automation parses the CSV (Zapier email triggers, mailroom-to-spreadsheet workflows, etc.).

Yes. LeadSync supports email notifications as a destination for lead forms across Facebook, Instagram, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source is its own connection, so you can route different ad sources to different recipient lists -- handy when separate sales pods own different paid channels.

Within seconds of the lead webhook firing. There is no batching or queuing -- each lead triggers an immediate transactional email send. From "user taps Submit on the ad" to "email lands in your inbox" is typically under five seconds.

Available Integrations

How It Works

A Notification Destination, Not a CRM

Multiple Recipients, Comma-Separated

Customisable Subject, Introduction, Signature, and Logo

Frequently Asked Questions

Start Syncing Leads to Email Notifications