Inquiry: Facebook Lead Integration Without Creating Workflow for Every New Form

[Sumit Natrajan]

We’re currently using Pabbly Connect to integrate our Facebook Lead Ads with our CRM. As of now, for every new form created under our Facebook page, we have to manually create a new workflow in Pabbly and link it to our CRM, which is turning out to be a time-consuming process.

I wanted to check if there’s an easier or alternative way to directly link our Facebook Page ID (instead of individual form IDs) with our CRM integration — so that any lead generated from any form under the connected Facebook page gets automatically pushed to our CRM without needing to create a separate workflow for each new form.

Could you please confirm if this is possible within Pabbly, or suggest a recommended workaround to handle this more efficiently?

 

[Preeti Paryani]

Hello @Sumit Natrajan,

Thank you for reaching out!

At the moment, it's not possible to capture leads from every form across all pages automatically within a single workflow. However, within a single Facebook page, Pabbly Connect does support capturing leads from all forms associated with that page — so you don’t need to create a separate workflow for each form.

 

[Sumit Natrajan]

Hello @Sumit Natrajan,

Thank you for reaching out!

At the moment, it's not possible to capture leads from every form across all pages automatically within a single workflow. However, within a single Facebook page, Pabbly Connect does support capturing leads from all forms associated with that page — so you don’t need to create a separate workflow for each form.

View attachment 55306

Hii Priti,
Thank you for the prompt response , this will work for me but the only concern is for every new page also I need to create a workflow which will again be a big task for me so is there any way where we can directly do some process via the API .

 

[Preeti Paryani]

Hello @Sumit Natrajan,

We understand your concern; however, capturing leads from all forms under every page within a single workflow is not currently feasible.

We appreciate your understanding.