Answered

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

(0) Share

Report

Posted on by michaelBurch

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:

PowerApps Trigger
HTTP GET from URI with 1 Dynamic Content to insert the Video ID
- URI: https://www.googleapis.com/youtube/v3/videos?part=id%2Csnippet%2Cstatus%2CcontentDetails&id=@{triggerBody()['HTTP_URI']}&key=xxxxxxxxxxxxxxxxxxx
Response
Parse JSON
Apply to each
- SQL Insert row

Graphical reference:

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:

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:

Building flows

I have the same question (0)

All responses (3)

Answers (1)

michaelBurch 22 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Verified answer

thjeffri Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

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:

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

Let me know if this helps,

Tom

Was this reply helpful? Yes No
michaelBurch 22 on at

Like (1)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No