Quick Actions
Quick Actions are pre-configured prompts that appear in the chat welcome panel. They provide one-click access to common operations, making it easy for users to perform frequent tasks without typing.
Understanding Quick Actions
When users open a new chat, they see Quick Action buttons above the message input. Clicking a button sends a pre-configured prompt to the AI assistant, which then executes the action.
Quick Actions are useful for:
- Standardizing common requests — Ensure consistent phrasing
- Reducing typing — One click instead of typing a request
- Guiding users — Show what's possible with Hublvu
- Accelerating workflows — Fast access to frequent operations
Viewing Quick Actions
- Go to Quick Actions in the AI section of the sidebar
- See the list of configured quick actions
- View which actions are enabled and for which groups
Creating Quick Actions
Basic Configuration
- Click New Quick Action
- Configure the quick action:
| Field | Description |
|---|---|
| Name | Display label on the button (keep short) |
| Description | Tooltip shown on hover |
| Prompt | The text sent to the AI when clicked |
| Icon | Optional icon for visual recognition |
| Enabled | Whether this action is active |
- Save
Writing Effective Prompts
The prompt is what gets sent to the AI. Write it as if a user typed it:
Good prompts:
- "Show me the status of all production servers"
- "List recent failed flow runs from the last 24 hours"
- "Check database connection health"
Less effective prompts:
- "Status" (too vague)
- "Please kindly show me..." (unnecessary words)
Using Variables
Quick Actions can include variables that prompt users for input. Variables use double curly brace syntax.
Example prompt:
Check connectivity to {{server_name}}
When clicked:
- User is prompted to enter a value for
server_name - The value is substituted into the prompt
- The complete prompt is sent to the AI
Variable syntax: \{\{variable_name\}\}
Group Assignment
Control which user groups see which Quick Actions.
Assigning to Groups
- Open a Quick Action's configuration
- Go to Groups tab
- Select which groups should see this action
- Save
Common Patterns
| Pattern | Description |
|---|---|
| All users | Assign to all groups (general purpose actions) |
| Role-specific | Different actions for different teams |
| Admin-only | Sensitive operations for administrators |
Organizing Quick Actions
Display Order
Quick Actions appear in the order configured. Drag and drop to reorder:
- Go to the Quick Actions list
- Drag actions to change their position
- Most-used actions should be first
Categories
Group related actions together:
- Put similar actions adjacent
- Use consistent naming conventions
- Consider user workflows
Recommended Limits
- 5-8 actions per user view is ideal
- Too many actions create decision paralysis
- Use group assignment to show relevant actions to each team
Examples
Operations Team Quick Actions
| Name | Prompt |
|---|---|
| System Status | "Show me the current status of all monitored systems" |
| Recent Alerts | "List alerts from the last hour with severity high or critical" |
| Check Server | "Check the health of server {{server_name}}" |
Database Team Quick Actions
| Name | Prompt |
|---|---|
| DB Health | "Check database cluster health for {{environment}}" |
| Slow Queries | "Show slow queries from the last 30 minutes" |
| Connection Pool | "Show connection pool status for all databases" |
General Quick Actions
| Name | Prompt |
|---|---|
| My Runs | "Show my recent flow and guide runs" |
| Help | "What can you help me with?" |
| Find Flow | "Find a flow for {{problem_description}}" |
Best Practices
Button labels should be 2-3 words max. "System Status" not "Check Current System Status".
The prompt should be a complete request. Don't rely on users to add context.
One variable per action is usually enough. Multiple variables slow users down.
Try each Quick Action to ensure the AI responds appropriately.
Check which Quick Actions are used frequently. Remove unused ones.
Troubleshooting
Quick Action Not Appearing
- Verify the action is Enabled
- Check group assignment includes the user's group
- Clear browser cache and refresh
Unexpected AI Response
- Review the prompt wording
- Test the prompt manually in chat
- Ensure required tools are available
Variable Prompt Not Showing
- Verify variable syntax uses double curly braces
- Check for typos in variable names
- Ensure no extra spaces inside braces
Related Topics
- Chat — Using Quick Actions as a user
- User Management — Managing groups
- Agents — AI agent configuration