Hi @IFly0. Short answer: you’re not missing a setting. Starter genuinely doesn’t give you one workflow that catches every Meta instant form submission, so what you’re running into is expected behavior, not a gap in your setup.
Here’s why, as I understand it. Meta creates and hosts the form. HubSpot syncs each submission in, but it treats every instant form as its own distinct source, not as a member of a shared “Meta lead” category. Starter’s automation is scoped to that individual form, so when marketing spins up a new ad with a new form, you’re not missing a trigger. You’re just hitting a wall that’s built into the plan.
What I’d actually do, based on HubSpot resources like this.
Standardize on one master Meta Instant Form. Keep the questions and fields the same, and vary the campaign, ad set, and creative instead of cloning the form each time. Build a single workflow against that one synced form. This holds up as long as the follow-up action is identical across ads, things like a notification, one email, a task, or setting a consistent source value.
If marketing genuinely needs different questions or routing per campaign, don’t keep fighting this inside Starter. You’ve got two honest paths from there: route every Meta lead through something outside HubSpot, like Zapier, Make, or n8n, that catches the webhook and centralizes the logic, or move up to a tier that supports contact-based workflows. A custom API integration can write clean, consistent data onto the contact record either way, but it won’t unlock the “enroll on any Meta form” trigger you’re picturing. That has to live outside HubSpot or above Starter, not inside it.
One thing worth doing no matter which path you pick: lock down the lead form schema so marketing duplicates an approved form instead of building new ones from scratch. It’s a small guardrail, but it saves you from messy attribution and broken reporting down the road.
Hope that clears up what’s actually possible on your plan.