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

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Error on Automate trig...
Power Automate
Unanswered

Error on Automate trigger (The input trigger ‘manual’ of type ‘Request’ did not match its schema definition)

(0) ShareShare
ReportReport
Posted on by 22

Hi all,

I have sort of an odd error (for me) when building out a Flow.  I’m working on a project to collect YouTube video data using Googles video data API (video.list).  The flow works well in testing each object until I add the Add to each and SQL insert row. 

Background:

The flow is structured in this manner:

Graphical reference:

michaelBurch_0-1597926785286.png

 

michaelBurch_1-1597926785293.png

 

Issue:

As I build the flow, all testing works great (test, add dynamic content (HTTP_URI=video ID), run) until I add the SQL Insert row.  Then I get the following error:

michaelBurch_2-1597926785296.png

 

 The odd this is if I add the entire URI string to the HTTP_URI during a test it will run fine.

I’m really stuck here.  I’ve rebuilt the Flow a few times to no avail.  Any help would be greatly appreciated.

Michael

Categories:
I have the same question (0)
  • michaelBurch Profile Picture
    22 on at

    Please let me know if there is any additional information I can provide to facilitate a response.  Any assistance would be really appreciated. 

  • Verified answer
    thjeffri Profile Picture
    Microsoft Employee on at

    Hi michaelBurch,

     

    First off, this is a slick idea, so kudos to you on that.

     

    Power Automate knows the URI field on the HTTP action needs a URI to be passed in, so it's forcing the input to be a URI.  In most scenarios this is helpful, since it prevents you from running the flow with invalid inputs.  The twist is that since you are only inputting part of the URI from the Power Apps trigger, the input doesn't actually need to be a URI, just a string.

     

    One simple way to get around this would be to add an "Initialize variable" step, set the type to "string", and then for the Value use "Ask in Power Apps".  You can then use the string variable in your portion of the HTTP request.  Something like this:

    thjeffri_0-1598294559545.png

     

    This way, you avoid Power Automate forcing you into providing a URI input.

     

    Let me know if this helps,

     

    Tom

     

  • michaelBurch Profile Picture
    22 on at

    Hello Tom,

    This worked PERFECTLY!!!

    I really appreciate your guidance on this!  And thank you for the compliment on the project; it is a really fun one.

    Thank you, again

    Michael

     

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

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 522 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 364 Moderator

#3
abm abm Profile Picture

abm abm 243 Most Valuable Professional

Last 30 days Overall leaderboard