![]() ![]() Here's an example of getting the body of the text message. On the second flow, you can follow the blog post advice on grabbing values, however, I have found it's faster to use Filter Array to grab the key / value pairs you need. The second flow should just have the $formdata json which I'm providing below ![]() The first flow should be the entire content of the json sent from Twilio. Make sure both triggers have the correct JSON (I just used the sample payload option for both). On the second flow, you 'receive' the $formdata array Okay, I've confirmed this has been working for a few days:Ĭreate a flow to receive Twilio texts (on Twilio, use POST and the address of the Power Automate trigger)Īdd one action with HTTP POST that 'passes' just the $formdata array from the body to another flow using a POST trigger I can't wrap my head around why adding an action that uses a connection would cause the flow to fail I'm pretty sure this has something to do with using POST, but my googling has revealed no answers. However the trigger doesn't have header settings so I'm not sure if this is related or not. ![]() Removing the JSON schema from the trigger does nothingĬreating a brand new flow with just the trigger and SQL recreates the errorĮxpanding my trigger shows the message: Remember to include a Content-Type header set to application/json in your request. I have other Request triggers and they still work, HOWEVER they are GET Troubleshooting: Removing the action using a connection fixes the flow I created new flows using SQL and they work There's a problem with the flow's trigger. Fix the trigger, Learn moreĬlicking Fix the trigger takes me to my trigger with the error BadRequest and no other info Once I add the outside connection and test again, the flow will not run and I see this error: It works well, until I add an action that uses an outside connection (Twilio send a text or SQL server). I've created a flow to receive Twilio texts and process them per this documentation: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |