Ask Claude to “connect my Facebook lead ads to HubSpot” in October 2026 and you get a confident plan, a few tool calls, and then a polite admission that it cannot do the one step that matters. It can build the campaign. It can create HubSpot contacts. It cannot move a lead from one to the other.
This post explains why that gap exists, what you can actually do from Claude today, and the three-part setup that gets an AI assistant into the loop without pretending the gap is closed. If you want the plain step-by-step for the LeadSync and HubSpot side, the Facebook Lead Ads to HubSpot guide covers that in detail.
What Claude Can Do With Meta Ads in 2026
Meta launched its Ads AI Connectors, including an official MCP server, in open beta on 29 April 2026. MCP (Model Context Protocol) is the standard that lets an assistant such as Claude or ChatGPT call a product’s functions as tools. Meta’s pitch was blunt: “no developer credentials, API setup, or coding required” (Meta Business News, 2026).
Once you add the server to Claude, it can:
- Pull performance reports across campaigns, ad sets and ads
- Create and edit campaigns, ad sets and ads (new ads start paused)
- Manage catalogs and datasets
- Check Conversions API signal health
- Set up A/B tests and read activity logs
We covered the full tool list in Meta Ads AI Connectors: What the MCP Server Means for Lead Ads. The short version for lead-gen advertisers is that it is a campaign tool, not a lead tool.
What Claude Can Do With HubSpot
HubSpot’s remote MCP server became generally available on 13 April 2026 and works on every HubSpot account, with some tools gated by tier (HubSpot changelog, 2026). It is in Claude’s connector directory, so adding it is a click and a HubSpot sign-in.
From Claude you can read contacts, companies, deals, tickets and marketing objects, and create or update contacts, companies, deals, tickets and activities. That is genuinely useful once leads are in HubSpot: “show me every lead from the kitchen renovation campaign this week that has no owner” is a one-line request.
What it does not include is anything to do with advertising. HubSpot’s documentation for the server makes no mention of ads or lead ads (HubSpot developer docs, 2026). HubSpot’s native Facebook lead sync still lives in the Ads tool, and a human with ad account admin, page admin and Business Manager leads access has to set it up (HubSpot Knowledge Base).
The Gap: Nobody Retrieves the Lead
So Claude can talk to both ends. Why can it not join them?
Because Meta treats lead data as a protected resource. Reading leads from an Instant Form needs the leads_retrieval permission, which requires App Review and then Business Verification. Meta’s own documentation spells it out: “Standard Access only works with your own test Pages and forms. Serving real advertisers requires Advanced Access through Meta App Review” (Meta for Developers).
Meta’s Ads MCP server does not expose lead retrieval, and a third-party teardown of the tool list noted that Instant Form creation “isn’t in the tool list either, which matters for lead-gen accounts” (adsuploader, 2026). The same wall applies to every automation platform. Zapier’s Facebook Lead Ads trigger requires the page to sit in a business portfolio, requires your account to have “full control access for the business asset”, and ends with “Authenticate through Facebook in the new browser window” (Zapier Help).
Here is where each tool stops, as of October 2026.
| Tool | Build the campaign | Read Facebook leads | Write HubSpot contacts | Needs a human Facebook login |
|---|---|---|---|---|
| Claude + Meta Ads MCP | Yes | No | No | Yes, once, for the ad account |
| Claude + HubSpot MCP | No | No | Yes | No (HubSpot sign-in instead) |
| Zapier or Make | No | Yes, after setup | Yes | Yes, in their dashboard |
| LeadSync | No | Yes, in real time | Yes | Yes, once, in LeadSync |
The human click is not a limitation of any one product. It is Meta policy, and it is the reason a sync tool with an approved app still sits between the ad and the CRM.
The Three-Part Setup That Works Today
You can have an assistant doing real work on both sides of the lead within an hour. The lead itself travels through LeadSync.
Step 1: Connect Meta’s Ads MCP server to Claude
In Claude, open Settings, then Connectors, then Add custom connector, and paste the server address, which is https://mcp.facebook.com/ads. Sign in with Facebook Login for Business and pick the business portfolios and ad accounts Claude may reach. Claude Code and ChatGPT follow the same pattern; Meta’s announcement links the setup for each (Meta Business News, 2026).
Now ask for the campaign. A prompt like “create a leads campaign for my Melbourne kitchen renovation offer, A$40 a day, Instant Form objective, audience 30 to 65 within 25 km” gets you a paused draft to review in Ads Manager.
Step 2: Create the Instant Form in Ads Manager
This is still manual. Open the draft, attach or create the Instant Form, and publish. If you are deciding between an Instant Form and sending traffic to a landing page, Instant Forms vs website forms covers the trade-offs.
Step 3: Connect LeadSync to the page and to HubSpot
Sign up at leadsync.me/pricing (7-day free trial, no card), connect the Facebook page, pick the form, then add HubSpot as the destination and sign in to HubSpot when asked. Map the form fields to HubSpot properties. Those two sign-ins are the human approvals Meta and HubSpot require, and they happen once per page and once per portal.
From then on every lead lands in HubSpot within seconds of the form being submitted. The HubSpot integration page lists what gets mapped, including campaign and ad attribution.
Step 4: Push a test lead through
Use Meta’s Lead Ads Testing Tool to submit a test lead and watch it arrive in HubSpot. The guide to testing Facebook lead ads walks through the tool and the common reasons a test lead does not show up.
Step 5: Connect HubSpot’s MCP server to Claude
Back in Claude, add HubSpot from the connector directory and sign in. Now the assistant can see the leads LeadSync delivered. Useful prompts:
- “List contacts created today with source Facebook and no owner, and assign them round-robin to the sales team.”
- “Draft a follow-up email for every lead from the kitchen campaign that has not been contacted in 24 hours.”
- “Which ad produced the most contacts this week, and what is their average deal value?”
That last one is where the loop closes. Claude can read the answer in HubSpot, then switch to the Meta connector and move budget toward the ad that is producing real pipeline.
What Still Needs a Human (and Will for a While)
- Granting Facebook access. Meta policy. One click per page, inside LeadSync.
- Granting HubSpot access. OAuth sign-in, once per portal.
- Creating the Instant Form. Not in Meta’s MCP tool list as of October 2026.
- Field mapping in LeadSync. Done in the dashboard today. This is the step an assistant could reasonably take over, which brings us to the next section.
Everything else, from campaign creation to follow-up, an assistant can already handle.
What Is Coming: A LeadSync API and AI Connector
LeadSync has the approved Meta, LinkedIn, TikTok and Google apps, and it already treats lead delivery as a pipeline you configure. The missing piece for assistants is a way to drive that pipeline without a human in the dashboard.
The version on the table is deliberately small. After you have granted Facebook and CRM access once, an assistant could:
- See every connected ad account, page, form and destination
- Attach a new form to a CRM or email list and map the fields
- Check whether the last leads were delivered, and why one failed
- Resend a lead, or push a test lead through the whole pipeline
- Hand you a single link whenever a step needs your approval
It would ship as a REST API with a connector for Claude and ChatGPT on top. Whether it ships at all depends on how many people want it. If that is you, join the waitlist at leadsync.me/developers. It takes a minute, and the use case you type in decides what gets built first.
If you already have your own code and want leads now, the Webhook destination sends every lead to your endpoint with the full payload, including ad and campaign attribution. Agencies running dozens of client pages through one endpoint do exactly that today.
Frequently Asked Questions
Can Claude connect Facebook Lead Ads to HubSpot on its own?
Not in 2026. Claude can create Meta campaigns through Meta’s Ads MCP server and can read and write HubSpot contacts through HubSpot’s MCP server, but no connector retrieves Facebook leads. Lead retrieval needs an approved Meta app and a human granting page access, so a sync tool like LeadSync still sits between the two.
Does Meta’s Ads MCP server deliver leads?
No. Meta’s Ads MCP server covers reporting, campaign and ad creation, catalogs, Conversions API signals, experiments and activity logs. It does not retrieve leads from Instant Forms and does not create Instant Forms. Lead delivery still goes through an approved lead-sync app or a manual CSV download.
Does the HubSpot MCP server handle Facebook Lead Ads?
No. HubSpot’s remote MCP server, generally available since 13 April 2026, works with CRM objects such as contacts, companies, deals and tickets. It has no advertising or lead ads tools. HubSpot’s own Facebook lead sync is configured by a human in the Ads tool, not through the MCP server.
Why does a human still need to click Facebook Login?
Meta gates lead retrieval behind the leads_retrieval permission, which requires App Review followed by Business Verification. Standard access only works with test pages. The page owner has to sign in and approve the app, and that approval cannot be delegated to an AI assistant or an automation platform.
What is the fastest setup if I want AI in the loop today?
Connect Meta’s Ads MCP server to Claude to build and manage the campaign, connect LeadSync to the Facebook page and HubSpot so each lead lands in HubSpot within seconds, then connect HubSpot’s MCP server to Claude to review and act on new contacts. The only manual steps are the two Facebook and HubSpot approvals inside LeadSync.
Will LeadSync have an API or a Claude connector?
It is scoped and waiting on demand. The planned version lets an assistant see your connections, attach a form to a CRM, map fields, check delivery, resend leads and push a test lead, after you grant Facebook and CRM access once. Join the waitlist to be told first.
