Facebook Lead Ads to Google Sheets and Email Without Zapier

The practical no-Zapier path is a four-node n8n workflow: Facebook Lead Ads Trigger → Edit Fields → Google Sheets → Gmail. A new instant-form submission starts the workflow. n8n normalizes the fields, appends or updates one row using the Meta lead ID, then sends an internal email alert with a link to the sheet.

Check Meta's direct Google Sheets option first

Some Meta Business Suite accounts now show a direct Google Sheets connection under All tools → Instant forms → CRM setup → Google Sheets. If it appears in your account and your only requirement is to place each new form submission in one spreadsheet, try that route first. It is simpler than creating a Meta developer app and does not require a separate automation-platform subscription.

Meta rolls out and changes Business Suite features by account and region, so the Google Sheets choice may not be visible everywhere. This guide covers the n8n route because the workflow does more than copy a lead: it normalizes the data, uses the lead ID for safer writes, and sends an internal notification. The four required steps use built-in n8n nodes, so the basic workflow does not need a custom HTTP Request node.

What this workflow should do

Keep the email internal at first. An automatic message to the prospect is a separate business decision because the form must clearly support that use, the address must be valid, and local privacy and marketing-consent rules still apply.

Prerequisites for the n8n route

• A Meta Page, an active instant form, and access to the relevant ad account and Page.
• A Meta for Developers account and an app with Facebook Login or Facebook Login for Business.
• A public HTTPS n8n URL. Meta cannot deliver production webhook events to a private localhost address.
• A Google account or service account that can edit the destination spreadsheet.
• A Gmail credential, SMTP credential, or another email provider supported by your n8n instance.

n8n's current Facebook Lead Ads credential uses OAuth2. You copy the OAuth Redirect URL from n8n into the Meta app, then add the Meta App ID and App Secret to the n8n credential. For production, n8n's official setup also calls for a Privacy Policy URL, Live app mode, advanced access for the requested feature, and business verification where Meta requires it.

Meta permissions and leads access

Meta's current lead-retrieval documentation separates access by the data you request. For complete lead and ad-level data it lists leads_retrieval, pages_show_list, pages_read_engagement, pages_manage_ads, and ads_management. Webhook setup also uses pages_manage_metadata. The token must come from someone with the required Page and advertising access.

Leads Access Manager can narrow who or which integration can retrieve leads. A person being able to view the Page does not automatically prove that the app can fetch every lead. When the trigger connects but no real data arrives, check business asset access and lead access before rebuilding the workflow.

Build the workflow in n8n

1. Configure Facebook Lead Ads Trigger

1. Add Facebook Lead Ads Trigger and create its OAuth2 credential.
2. In Meta for Developers, add the n8n OAuth Redirect URL to the allowed redirect URIs.
3. Enter the Meta App ID and App Secret in n8n, then complete the Facebook authorization.
4. Select the Page and form that should start this workflow.
5. Run a test with Meta's Lead Ads Testing Tool and inspect the actual output before mapping fields.

2. Normalize the lead fields

Add an Edit Fields node after the trigger. Use the test execution to map the fields actually returned by your form. Meta forms can use custom question names, and their answers may arrive inside a field-data collection rather than as the exact column names you want.

Use a small stable record:

lead_id
created_time
full_name
email
phone
form_id
ad_id
campaign_id
source
status
owner

Store the Meta lead ID even if nobody sees it day to day. It gives the next node a durable key for a basic duplicate check and makes support investigations much easier than matching by name or email alone.

3. Write to Google Sheets without duplicate rows

Create the header row in Google Sheets first, then add the Google Sheets node. Choose Sheet Within Document → Append or Update Row, select the spreadsheet and tab, and match on lead_id. n8n also offers Append Row, but the append-or-update operation is safer when a delivery or execution is retried.

Map each normalized field to one column. Keep computed formulas and team notes in separate columns so a later field-map change does not overwrite them. A lightweight sheet can start with status = New and a blank owner, but it should not pretend to be a full CRM forever.

If several forms or channels feed the same CRM, a source lead ID is not enough to recognize the same person across systems. Use the broader n8n lead deduplication pattern to normalize identity keys, route conflicts, and update the right contact.

4. Send the internal email after the row succeeds

Put the Gmail or Send Email node after Google Sheets. This order matters: the team should not receive a success alert for a lead that failed to save. A concise internal message can include the name, email, phone, form source, submission time, and a link to the shared sheet.

Subject: New Facebook lead: {{ full_name }}

Name: {{ full_name }}
Email: {{ email }}
Phone: {{ phone }}
Form: {{ form_id }}
Lead ID: {{ lead_id }}

Open lead sheet: https://docs.google.com/spreadsheets/d/...

The placeholders above describe the message shape. Insert them through n8n's expression picker from your normalized node instead of pasting names that do not exist in your execution.

Test the path before publishing

1. Create one test lead with a recognizable test name and a safe email address.
2. Confirm the trigger execution contains the expected Page, form, lead ID, and question values.
3. Confirm one row appears under the correct headers.
4. Run the same normalized item again and confirm it updates the existing lead_id row instead of adding another row.
5. Confirm the internal email arrives only after the sheet operation succeeds.
6. Publish the workflow and create a separate production test lead.
7. Record who owns Meta access, Google access, and the alert mailbox so the integration is maintainable.

Common failures and the fastest checks

Privacy and operating rules

• Collect only the fields the sales or service process genuinely needs.
• Restrict the spreadsheet to the people responsible for follow-up.
• Do not put App Secrets, access tokens, or OAuth credentials in the sheet or email body.
• Set a retention rule for old leads and document who can delete or export them.
• Use a shared business mailbox or documented owner, not an employee's unexplained personal account.
• Add a failure alert or error workflow so a broken credential does not silently stop lead capture.

If your intake already starts with Google Forms rather than Meta instant forms, the simpler Google Forms, Sheets, and Gmail workflow may be enough. This guide is specifically for retrieving leads submitted inside Facebook or Instagram lead ads and routing them through n8n.

Sources checked

• n8n Facebook Lead Ads Trigger documentation and single-webhook warning
• n8n Facebook Lead Ads OAuth2 credential setup
• Meta lead retrieval, permissions, webhooks, and lead payload documentation
• n8n Google Sheets node operations
• n8n Gmail node operations
• Meta lead ads with instant forms and CRM retrieval overview
• Current walkthrough of Meta Business Suite's direct Google Sheets connection