I will automate facebook lead ads to your CRM with make or n8n


About this gig
Stop copying Facebook leads between tools. I build a Make or n8n workflow that sends leads from one Facebook lead form to your supported CRM, spreadsheet, or notification channel.
Your package includes agreed field mapping, a test with sample data, and practical handoff notes. Standard adds a second destination and one routing rule. Premium supports up to three destinations, two routing rules, a basic failure alert, and a walkthrough. We confirm API access and compatibility before starting.
WhatsApp notifications require your approved business setup, API provider, and any required templates. Platform subscriptions, API usage, messaging charges, ads setup, and ad spend are separate. This offer routes existing leads; it does not promise new leads or sales. Custom APIs, historical data migration, AI agents, and ongoing monitoring need a separate scope. English and Spanish support are available.
Get to know Carlos Jimenez
Websites SEO and AI Automation in English and Spanish
- FromUnited States
- Member sinceMay 2025
Languages
English, Spanish
My Portfolio
FAQ
Which tools can you connect?
Tools supported by Make or n8n, subject to your plan and API permissions. Send the exact source and destination before ordering so we can confirm compatibility.
Is WhatsApp included?
It can be a destination with your supported, approved business API setup and required templates. Provider and messaging fees are separate. Personal WhatsApp session automation is not included.
Do you run the ads or guarantee leads?
No. This package routes leads from your existing lead form. Ad campaigns, ad spend, lead volume, and sales are outside this offer.
How do you get access?
Invite me through each platform supported access controls. Do not send account passwords. We agree on minimum access and remove temporary access after handoff.
What happens after delivery?
You receive test evidence and handoff notes. Hosting, ongoing monitoring, third-party API changes, and new features are separate. Revisions cover the agreed workflow, not new destinations or scope.

