[DP-2] User-Based Action Path

What does this pattern do?

Change personal structured data within a system, and inform the user if it succeeded or failed based on the user details.

View Purple Chat

Example Use Cases

1. HR: Update my emergency contacts
2. Operations: Register myself for a company event
3. Sales: Create a new lead assigned to me
4. Security: Reset MFA for user

Design Considerations

Design time

1. Start in the Paths workspace.
2. Start collecting slots which need to be changed or submitted to a service. You can collect any of our slot types
3. Configure any custom attributes that are needed if your API does not accept email addresses.
4. Add an API Action using your slots. Make sure to include an email or user attribute so your system knows which user is executing this action.
5. Run any additional validation in your automation tools.
6. Set up your generative intent & launch rules.

Run time

• Your copilot will ask all questions sequentially & will not "shortcut"
• Your copilot will only inform the user if the API action succeeded or failed.