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 an action to my login or signup flow?

Objective

This article shows you how to attach a registered action to your login or signup flow in Identity Management, set what happens if it times out, and control the order your actions run in.

 

Product

Identity Management

 

Environment

Twilio Console

 

Procedure

  1. In the Twilio Console, select Identity & security in the left sidebar.
  2. Select Identity Management, then Actions.
  3. Select the tab for the flow you want to change: Login for Post-Login Actions, or Signup for Post-Signup Actions.
  4. Select Add login action or Add signup action.
  5. In the Add action window:
  6. Choose the Action from the list of actions in your library. Its webhook URL fills in automatically. If the action you need does not exist yet, select + Create a new action at the bottom of the list to register it here.
  7. Set Timeout behavior to ALLOW or DENY — what happens if the action does not respond in time.
  8. Set Timeout (ms).
  9. Select Add.
  10. A confirmation appears and the action is listed in the table with its Order, name and URL, and Timeout Behavior.

To change an action's timeout settings, open the actions menu at the end of its row and select Edit.

To change the order actions run in, select Reorder actions, rearrange them in the Edit action order panel, and select Save.

To take an action out of the flow, open the actions menu and select Remove, then confirm.

 

Additional Information

The timeout must be between 5,000 and 20,000 milliseconds. New actions default to 10,000 milliseconds and DENY.

Post-login actions run before a token is issued after login. Use them to inject custom claims, apply IP or geo-based restrictions or deny the request, enrich the user profile, and more.

Post-signup actions run in order immediately after a user's record is created. Use them to send welcome emails or alerts, provision external resources, and more.

When you edit an action already in a flow, its name and webhook URL are read-only, those are managed in the action library. Removing an action from a flow does not delete it from the library.

If a flow has no actions, the table shows No actions yet.

 

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

Have more questions? Submit a request
Powered by Zendesk