Azure logic Apps fails to pass params to Twilio Send Text message

Question

This is my first logic app experience and I appreciate all the help I can get.

Set up in logic app designer: HTTP request is received module connected to Twilio Send Text Message Module with twilio connector activated. The Twilio module parameters look up input fields in the http request.

The set up runs correctly when tested manually (by entering valid data in the twilio interface on logic app designer) - SMS is sent.

The logic app fires correctly when http request arrives using the url. Two different results:
(1) if data is manually populated in the twilio fields, then SMS with this data goes through.
(2) if the twilio fields are empty, then no SMS is sent - it seems that params passed by the url are not sent or used.

I checked the url for accuracy. It is correct. I checked that params are received by the HTTP request module (added a response to send back the input params) and it is correct.

What am I missing here? Any feedback would be greatly appreciated.

Answer 1

Hi @AG

I have tested the setup at my end and it is working as expected. Please verify the below steps:

1. Created the trigger "When a HTTP request is received" and set the method as GET
2. Once the HTTP Get URL is generated I will be passing the query parameter "message" that will have my message content.
   Example : https://prod-191.westeurope.logic.azure.com:443/workflows/{workflowID}/triggers/manual/paths/invoke?api-version=2016-10-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=signature&**message**="Testing_message"
3. Configure your connection and in the Text field click on "Add dynamic content" --> Expression and enter the value as triggerOutputs()['queries']['message'] since 'message' is the query parameter in my request. You can change it according to your need and make sure that you are passing the same parameter name while calling the logic app URL.
4. Testing the URL https://prod-191.westeurope.logic.azure.com:443/workflows/{workflowID}/triggers/manual/paths/invoke?api-version=2016-10-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=signature&**message**="Testing_message" from my REST client I can see that the message is delivered with the right content.

Hope after verifying the above step the issue gets resolved. Please let me know if you need any assistance.

Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.