cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
edmm94
Advocate I
Advocate I

Using HTTP POST with Twilio

Hello Everyone,

 

I am hoping to get some assistance on a POST I am trying to make to the Twilio REST Api. My scenario is as follows, we have a customer survey stored in Twilio as a Studio execution. These executions can be triggered by a POST to their rest API. I have tested it in Postman and got it working in Postman. 

 

My end goal is to use MS flow to handle the POST that way I can feed the execution a phone number based on other parameters from our organization. 

 

Has anyone worked with this before? Here is a capture of the HTTP data that Postman sends across as a request. 

 

 

POST /v1/Flows/FWXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/Executions HTTP/1.1
Host: studio.twilio.com
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW
Authorization: Basic AccountSID:Auth Code
User-Agent: PostmanRuntime/7.19.0
Accept: */*
Cache-Control: no-cache
Postman-Token: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX,XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Host: studio.twilio.com
Accept-Encoding: gzip, deflate
Content-Length: 284
Connection: keep-alive
cache-control: no-cache


Content-Disposition: form-data; name="To"

+15551112222
------WebKitFormBoundary7MA4YWxkTrZu0gW--,
Content-Disposition: form-data; name="To"

+15551112222
------WebKitFormBoundary7MA4YWxkTrZu0gW--
Content-Disposition: form-data; name="From"

+15552221111
------WebKitFormBoundary7MA4YWxkTrZu0gW--

 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Good news, @AKRogers @edgonzales , I got it working!!!!

 

The key is to understand how the form data boundaries work, basically the form data needs to include a boundary that is declared by the user in the header. In your body , you use the boundary to delimit all the form data parts. In the body, you'll need to add two extra hyphens as a prefix of the declared boundary, when you are done adding the last type of form data you close the POST with the boundary plus two suffix hyphens. (code snippet below).

 

The header must be

Content-Type multipart/form-data; boundary=----YOURBOUNDARYHERE

 

Body 

------YOURBOUNDARYHERE
Content-Disposition: form-data; name="To"

+PHONE NUMBER HERE
------YOURBOUNDARYHERE
Content-Disposition: form-data; name="From"

+PHONE NUMBER HERE
------YOURBOUNDARYHERE--

 

 

 

Once I got the syntax, it was actually super easy. This exponentially expands the capabilities of using Twilio with flow. Thanks for all your advice!

 

 

View solution in original post

18 REPLIES 18

@edmm94,

 

Sounds like you might need a little more power than the out of the box actions that are available for Twilio in Power Automate (MS Flow).  Have you looked into using HTTP actions to POST to Twilio?  If you have, please screenshot what you're doing and we can talk a bit more about where you might be stuck.  If you haven't started, just know that the HTTP connector is premium.  

 

Ashley

If you found this helpful, consider giving it a thumbs up!

edgonzales
Most Valuable Professional
Most Valuable Professional

@edmm94 

Hi there. So, the HTTP action should work for this (it's a Premium connector).  Have you already tried that?  Here's an article covering the action and how I used it to connect to Yelp.

 

-Ed-

 

If you liked this reply, please give it a thumbs up! If this reply has answered your question or resolved your challenge, please consider marking it as a Solution. This helps other users find it more easily via search.

Hi Ashley,

 

Yes! I have been trying to use the HTTP Post connector. 

 

I have tried a number of things. I just thing I keep tripping myself up on syntax. I even tried posting from Postman to a MS Flow URL in order to see what request came across but that did not work the way I thought it would. 

 

Here a screenshot of the latest.

 

Post Headers.png

 

Body

{
  "$content-type": "multipart/form-data; boundary=--------------------------329424697522232853751243",
  "$content": "LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTMyOTQyNDY5NzUyMjIzMjg1Mzc1MTI0Mw0KQ29udGVudC1EaXNwb3NpdGlvbjogZm9ybS1kYXRhOyBuYW1lPSJUbyINCg0KKzE2MzA2MzI4ODUyDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tMzI5NDI0Njk3NTIyMjMyODUzNzUxMjQzDQpDb250ZW50LURpc3Bvc2l0aW9uOiBmb3JtLWRhdGE7IG5hbWU9IkZyb20iDQoNCisxMjA1NDQyMDUzMg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTMyOTQyNDY5NzUyMjIzMjg1Mzc1MTI0My0tDQo=",
  "$multipart": [
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"To\""
      },
      "body": {
        "$content-type": "application/octet-stream",
        "$content": "XXXXXXXXXXXXXXX"
      }
    },
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"From\""
      },
      "body": {
        "$content-type": "application/octet-stream",
        "$content": "XXXXXXXXXXXXXXXX"
      }
    }
  ]
}

 

Response from Twilio

Response.png 

 

Hi @edgonzales thanks! Yes, I have been trying with the HTTP action but this article is really clearing things up. I posted a reply to another comment on here with what I have tried.

 

 

@edmm94, how's this going for you?  From your error message yesterday it looks like what you're sending to Twilio wasn't recognized, and it may just be a formatting/syntax thing as you mentioned.  I realize you aren't simply trying to send a text, but I set up a trial and tested out the Send a message action so that I could use Peek Code to see what the body of that request to Twilio looked like.  Here's the successful body:

 

15.png

 

Include your connection information in your headers in the HTTP action, and in the Body portion specify the "From" and "To," which is what appeared to be missing or invalid from your call.

 

Let us know how it goes!

Ashley

If you found this helpful, consider giving it a thumbs up!

Hi Ashley,

Yes I did play around with this originally. It was not successful.

I have however dug to find more educational content to better understand the proper syntax that Twilio’s REST API is expecting.

This helped me a lot to understand what might be required from me in terms of a multipart form data POST. https://stackoverflow.com/questions/3508338/what-is-the-boundary-in-multipart-form-data

I’ll have some time tonight to play around with it and hopefully will have an update.

Thanks for your help!

Good news, @AKRogers @edgonzales , I got it working!!!!

 

The key is to understand how the form data boundaries work, basically the form data needs to include a boundary that is declared by the user in the header. In your body , you use the boundary to delimit all the form data parts. In the body, you'll need to add two extra hyphens as a prefix of the declared boundary, when you are done adding the last type of form data you close the POST with the boundary plus two suffix hyphens. (code snippet below).

 

The header must be

Content-Type multipart/form-data; boundary=----YOURBOUNDARYHERE

 

Body 

------YOURBOUNDARYHERE
Content-Disposition: form-data; name="To"

+PHONE NUMBER HERE
------YOURBOUNDARYHERE
Content-Disposition: form-data; name="From"

+PHONE NUMBER HERE
------YOURBOUNDARYHERE--

 

 

 

Once I got the syntax, it was actually super easy. This exponentially expands the capabilities of using Twilio with flow. Thanks for all your advice!

 

 

My pleasure; great job!!

Ashley
Anonymous
Not applicable

I was also having a problem trying to POST to make a phone call, but I found a simpler method. If you use for Headers the key Content-Type and value application/x-www-form-urlencoded , you can the use the following as the Body:

To=%2B15555555555&From=%2B15555555555&Url=HTTPXMLURL

 

brave_rTBZeDjxsl.png

 

with %2B representing + and HTTPXMLURL in my case I used a link to a GitHub location that I put the TwiXL file:

 

<?xml version="1.0" encoding="UTF-8"?>
<Response>
<Say voice="alice">Assistance at the Employee Entrance. Repeat, assistance at the Employee Entrance.</Say>
</Response>

Very cool, I will play around with this.

 

I ended up continuing to play with the Twilio API and began passing across optional parameters in JSON within the post to add context within my Twilio Flow. So I might just stick with how I currently have everything formatted to work.

 

It is good to know that there is a secondary way to achieving the same result though.

Hi @edmm94

I am facing the same problem and I can't make it work.

Would it be possible to send a screen shot of the flow/HTTP step.

 

I would really appreciate this.

 

TIA 🙂

 

@Maryam-8516 Sure thing, it might help if you send me a screenshot of your setup as well.  In my screenshot in authentication, I have it set to Basic with my Account SID and API password

 

 

 

 

Anonymous
Not applicable

How did you end up passing the optional parameters to Twilio through the REST API?

@Anonymous  the optional parameters are sent as JSON. They would like something like this 

 

------WebKitFormBoundaryXXXXXXXXXXXX
Content-Disposition: form-data; name="Parameters"

{
"Department": "Value",
"OnsiteTech": "Value",
"UID": "Value",
"SiteName": "Value",
"ContactName": "Value"
}
------WebKitFormBoundaryXXXXXXXXXXXX
Content-Disposition: form-data; name="To"

+PHONENUMBER
------WebKitFormBoundaryXXXXXXXXXXXX
Content-Disposition: form-data; name="From"

+PHONENUMBER
------WebKitFormBoundaryXXXXXXXXXXXX--

Anonymous
Not applicable

Unfortunately, when I add in the Parameters bit, I'm back to getting the "Missing required parameter To in the post body" error message. Here is my HTTP POST request. I'm fairly certain I copied your solution correctly.

 

FlowIssue3.png

 

If I take out the Parameters part, and just have the "To" & "From", the call works perfectly.

Simply brilliant! thanks a lot for sharing this - I applied the same logic in order to get a Salesforce token via Power automate, below the code in case that somebody might need it too:

 

 

------salesforceXX
Content-Disposition: form-data; name="username"

USERNAME
------salesforceXX
Content-Disposition: form-data; name="password"

PASSWORD+SECURITYTOKEN
------salesforceXX
Content-Disposition: form-data; name="grant_type"

password
------salesforceXX
Content-Disposition: form-data; name="client_id"

XXXXXXXXXXXXXXXXXXXXXXX
------salesforceXX
Content-Disposition: form-data; name="client_secret"

YYYYYYYYYYYYYYYYYYYYYYYY
------salesforceXX--

 

 

 

cleve
Advocate I
Advocate I

Not sure if things have changed since this thread was last active, but I can fully confirm setting custom boundaries does not work. I reached out to Twilio and they gave me what I needed. Thank you to Alex C on their support team. Their solution matched what @Anonymous posted.

This worked out for me. I am using a POST request to trigger a flow on Twilio with the original trigger starting from Power Automate. 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (4,075)