Find User by Id enables you to reference a user dynamically and find that user based on a string ID at IVR runtime. Use this action with data actions or data table lookup actions. For example, retrieve a user ID from a data action and pass it into the Find User by ID action to obtain a user reference. Then, use the referenced user information in a Transfer action. For information on how to find a user by email, see Find User action. For information on how to find more than one user by ID, see Find Users by ID action.

Notes:
  • The dynamic lookup limit for a unique type is 25.
  • Each lookup is unique, so multiple lookups for the same object in the flow only count as 1.
  • The total lookup limit per flow is 100.

From the Toolbox, expand the Find category and drag a Find User by Id action into the appropriate location in the task editor.

Name Description
Name field Type a distinctive name for the action. The label you enter here becomes the action’s name displayed in the task sequence.
User Id Enter the user ID that locates the user. For example, “289a802d-d6d5-4bfa-bbef-b80f60b0bc85”. At runtime, Architect performs a search for the specified user. If the system finds an exact match, it returns the user value.
User Result

When the system receives the user value, it stores that value in the variable you specify here. You can then use the variable in other areas of the flow. 

Configure found and not found paths

Name Description
Found

This path indicates that Architect located the user within the organization. 

Drag the appropriate action into the Found path so that it follows the route you want the interaction to take. For example, a transfer action.

Note: The User Result field only populates when the flow follows the Found path. 
Not Found

This path indicates that Architect did not find the matching user. 

Drag the appropriate action into the Not Found path so that it follows the route you want the interaction to take. For example, send an automatic reply or transfer the action to the main menu.

Note: The User Result field does not populate when the flow follows the Not Found path.