SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

How do I make an HTTP request from a Studio flow?

Objective

This article shows you how to add and configure the Make HTTP Request widget so your Studio flow calls your own API or a third-party service mid-execution and uses the response in later widgets.

 

Product

Studio

 

Environment

Twilio Console

 

User Account Permission/Role(s) Required

Editing a flow requires the Studio flows create and update permissions on the account.

 

Procedure

  1. In the Twilio Console, select Orchestration in the left sidebar.
  2. Select Studio, then Flows.
  3. Select the flow you want to edit to open the Editor tab.
  4. Open the widget library and drag Make HTTP Request onto the canvas.
  5. Select the new widget to open its configuration panel.
  6. Enter the endpoint in Request URL.
  7. Choose GET or POST in Request method.
  8. For a POST request, choose the Content type, such as Application/JSON, and enter the payload in Request body.
  9. To send parameters, select Add HTTP parameter, enter the parameter's name as the key and its content as the value, then select Save. Repeat for each parameter.
  10. Select Authenticate with Twilio if the endpoint should receive Twilio's request signature.
  11. Select Save.
  12. Open the Transitions tab and choose where the flow goes next for If success and If fail.
  13. Select Publish to make the change live.

 

Additional Information

  • For GET requests the parameters are appended to the URL as a query string; for POST requests they are sent in the request body alongside or instead of Request body, depending on the content type you choose.
  • The response is available to later widgets in the flow, so pair this widget with Split Based On... to branch on what your service returned.
  • Always wire up If fail, a slow or unavailable endpoint otherwise leaves the flow with no path forward.

 

This content was generated by AI and reviewed, edited, and verified by a human.

Have more questions? Submit a request
Powered by Zendesk