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 Apps / Triggering a flow with...
Power Apps
Answered

Triggering a flow with premium connectors

(0) ShareShare
ReportReport
Posted on by 482

Dear community

 

I have a Power Apps that, upon submitting a form, stores an item in a Dataverse for Teams table. The user expects the result of that "request" to show up within a short period of time. Meaning, a flow is being triggered whenever it picks up the newly created item in that table and creates the result of said request.

This flow includes premium connectors and my users don't have a per user or per app/per flow plan, which is why I can't use the Power Apps trigger. However, in flow, when I use the "when an item is created, modified or deleted" trigger, it can include premium connectors, even when users don't have a premium plan - that's great. 

 

My problem is with the following:

I used to have the data stored in SharePoint and the flow always triggered within 1min. 1min was a "ok" time to wait for that request, but ever since I switched to Dataverse for Teams, it mostly uses the 5mins max-trigger-time. That's too long for our users.

 

Is there a way/hack to speed this up? I was thinking of creating a custom connector through the Azure API Management that triggers a HTTP flow to speed things up (API Management is way cheaper than buying premium licenses for all users).

However, I'm quite open for possible solutions.

 

Thank you in advance and kind regards,

Categories:
  • Verified answer
    Pstork1 Profile Picture
    69,665 Most Valuable Professional on at

    If your flows always triggered within a minute in SharePoint then you were lucky.  The timing on triggers in SharePoint is the same as the timing you are seeing in Teams now.  When using the automated triggers the trigger will normally happen somewhere between 0-5 minutes.  That was true for SharePoint and is still true for Teams.  Other than using instant triggers, which would require premium licensing, there is no way to get around it.  

  • mrQ Profile Picture
    482 on at

    Hi @Pstork1 

    Thanks for your response.

    I've been using flows for a few years now in combination with SharePoint. It was always around a 1min trigger. Not sure if this depends on the region... but it uses definitely much more for Dataverse for Teams, unfortunately. 

     

    Do you see any issues when I go ahead and create a custom connector through the API Management API and use a HTTP flow to trigger it instantly?

  • Pstork1 Profile Picture
    69,665 Most Valuable Professional on at

    You can try the custom connector. I don't know if that is going to help or not.

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Leaderboard > Power Apps

#1
11manish Profile Picture

11manish 236 Super User 2026 Season 2

#2
WarrenBelz Profile Picture

WarrenBelz 207 Most Valuable Professional

#3
Mohsin Ali Profile Picture

Mohsin Ali 169

Last 30 days Overall leaderboard