Announcements
Hi everyone,
I've run into an issue while building automation using Microsoft Forms and Power Automate. I have a single Microsoft Form that I want to connect to multiple workflows. However, after creating a few flows(upto now there have been 75 workflows) with the same Form as the trigger, I'm now getting this error:
“Too many webhooks for the form.”
After doing some research, it seems like there's a limit to how many flows can use the "When a new response is submitted" trigger for the same Form.
Can anyone confirm:
What is the maximum number of flows that can be triggered by a single Microsoft Form?
Is there a workaround if I need to connect the same Form to more than 5 workflows?
Would using a dispatcher pattern (one main flow that branches into sub-flows) be the recommended approach here?
I'm working with a large automation setup and need to monitor or process form responses in multiple ways, so any guidance would be appreciated.
Thanks in advance!
Create one main flow that handles all form responses, then branches to sub-flows:
1. When a new response is submitted (Forms trigger) - ONLY ONE 2. Get response details 3. Parse/analyze response data 4. Multiple parallel branches or conditions: - Call Flow A (HTTP trigger) - Call Flow B (HTTP trigger) - Call Flow C (HTTP trigger) - etc.
Each sub-flow: 1. When an HTTP request is received (trigger) 2. Parse JSON (form response data) 3. Process specific logic 4. Return response
Consolidate all logic into one comprehensive flow:
1. When a new response is submitted 2. Get response details 3. Switch/Condition blocks for different processing paths: - If response contains X → Process Type A - If response contains Y → Process Type B - If response contains Z → Process Type C 4. Parallel branches for simultaneous processing
Create reusable child flows and call them from the main flow:
1. When a new response is submitted 2. Get response details 3. Run child flow 1 (pass response data) 4. Run child flow 2 (pass response data) 5. Run child flow 3 (pass response data)
Each child flow: 1. Manually trigger a flow (with input parameters) 2. Process specific logic using input data
1. One main form handler flow 2. Multiple solution-aware flows that process data 3. Use Dataverse or SharePoint lists as intermediate storage 4. Trigger subsequent flows based on data changes
Use a queue system for complex scenarios:
1. Main Flow: - When form submitted - Add response to SharePoint list/Dataverse table - Set processing flags 2. Multiple Processing Flows: - Triggered by "When an item is created/modified" - Process specific aspects based on flags - Update completion status
If I have answered your question, please mark it as the preferred solution ✅ . If you like my response, please give it a Thumbs Up 👍. Regards, Riyaz
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Haque 607
Valantis 495
Vish WR 429