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 add a widget to a Studio flow?

Objective

This article shows you the general pattern for building a Studio flow on the canvas, opening the widget library, dragging a widget in, configuring it, saving it, and wiring up where the flow goes next. Every widget-specific article builds on these steps.

 

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. With read-only access the canvas cannot be changed.

 

Procedure

  1. In the Twilio Console, select Orchestration in the left sidebar.
  2. Select Studio, then Flows.
  3. Select the flow you want to build, which opens the Editor tab.
  4. Open the widget library from the control panel beside the canvas.
  5. Drag the widget you want from the library onto the canvas. Studio gives it a default name, such as send_message_1.
  6. Select the widget on the canvas to open its configuration panel.
  7. Rename the widget in Widget name if you want something more descriptive, then fill in the widget's fields.
  8. Select Save in the configuration panel.
  9. Open the Transitions tab in the configuration panel and, for each outcome the widget can produce, choose the widget the flow should move to next.
  10. Connect the widget to the rest of your flow by drawing a connection from the preceding widget's outcome to this widget.
  11. Select Publish when you are ready for the change to handle live traffic.

 

Additional Information

  • Transitions save on their own shortly after you pick a destination; the widget's fields save when you select Save.
  • Widget names must be unique within a flow, and are the names you will see in the execution logs' Widget name column when debugging.
  • Every flow starts with a Trigger widget, which has separate outcomes for incoming calls, incoming messages, and REST API triggers. Connect your first widget to the outcome that matches how the flow will be started.
  • A widget with required fields left empty blocks publishing. The publish error names how many widgets are missing required configuration.

 

 

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

Have more questions? Submit a request
Powered by Zendesk