web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Limit on the Number o...
Power Automate
Suggested Answer

Limit on the Number of Flows a Single Microsoft Form Can Trigger

(1) ShareShare
ReportReport
Posted on by 48

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!

webhooks.png
Categories:
I have the same question (0)
  • Suggested answer
    venturemavenwill Profile Picture
    1,198 Super User 2026 Season 1 on at
    If all of your Power Automate Flows have the same trigger "When a new response is submitted", you could consider simply building your flows into child flows. This should be pretty easy because every one of your process probably uses a connector like "Get response details" anyway, so you just need to make sure to ask for the "response id" in your child flows, and you will be able to get the information you need. 
     
    Once you have your child flows set up, you can add them to a single parent flow, which will serve as the trigger, as parallel actions. 
  • Suggested answer
    Riyaz_riz11 Profile Picture
    4,120 Super User 2026 Season 1 on at
    Hi,
     

    Solution 1: Dispatcher Pattern (Recommended)

    Create one main flow that handles all form responses, then branches to sub-flows: 

    Main Dispatcher Flow:

      
    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.

    Sub-flows Structure: 

    Each sub-flow:
    1. When an HTTP request is received (trigger)
    2. Parse JSON (form response data)
    3. Process specific logic
    4. Return response

    Solution 2: Single Flow with Multiple Branches

    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

    Solution 3: Use Child Flows

    Create reusable child flows and call them from the main flow:

    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) 

    Child Flows:

    Each child flow:
    1. Manually trigger a flow (with input parameters)
    2. Process specific logic using input data

    Solution 4: Power Platform Solutions Approach

      Use Power Platform Solutions to organize your flows better:
    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

    Solution 5: Queue-Based Processing

    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.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 607

#2
Valantis Profile Picture

Valantis 495

#3
Vish WR Profile Picture

Vish WR 429

Last 30 days Overall leaderboard