Leads in

Meta Lead Ads & Google LSA

Meta Lead Ads and Google Local Services Ads have no direct connection; relay them through n8n (templates included) or Zapier.

Neither platform can post to Light AI on its own: Meta delivers leads only to apps it has reviewed, and Local Services Ads leads can only be pulled through the Google Ads API. Use an automation tool in between. Both n8n templates post to POST /v1/leads with an external_ref, so a lead relayed twice is never duplicated.

Meta Lead Ads#

Import Meta Lead Ads → Light AI from Downloads into n8n.
Connect the Facebook Lead Ads Trigger to the page and form.
Add a Light AI API key credential (Header Auth: Authorization = Bearer lai_live_…, scope leads:write).
Check the mapping in the Code node (custom questions such as the address or service), then activate.

Meta field	Light AI
`full_name` / `first_name`, `last_name`	`contact.*`
`email`, `phone_number`	`contact.email`, `contact.phone`
`street_address`, `city`, `state`, `zip_code`	`address.*`
`leadgen_id` (lead id)	`external_ref` (`system: meta_lead_ads`, `namespace`: the page id)
`custom_disclaimer_responses`	`consent`
ad, campaign and form ids	`attribution`

Zapier and Make work the same way: their Facebook Lead Ads trigger feeds a request to POST /v1/leads (or to an inbound source with capture and map).

Google Local Services Ads#

You need Google Ads API access (a developer token) for the LSA account.
Import Google LSA → Light AI from Downloads. It polls the local_services_lead resource every 15 minutes.
Set the customer id and the Google Ads OAuth credential, check the API version in the request URL, then activate.

Each LSA lead is sent with source: google_lsa and external_ref: { system: "google_lsa", id: <lead id> }. Message and phone leads without an e-mail are accepted when they carry a phone number.

Note

Field names in Google and Meta APIs change between versions. The templates are starting points: run one test lead through each before going live.