Configure an Agent
Step-by-step guide to configure and activate an agent in Junet
Step 1: Access Admin Panel
- Open Junet and log in with your credentials
- Navigate to Admin Panel:
- Click on your Avatar in the top right corner.
- Navigate to the Admin Panel button
Step 2: Go to AI Configuration
- In the Admin Panel, locate AI Configuration
- Click on Connections & Agents
This is where you manage all your agents and their connections to external services.
Step 3: Select an Agent
- You'll see a list of available agents
- Click on the agent you want to configure
- If you don't have an agent yet, you may need to create one first
- Existing agents will be listed with their current status
Step 4: Enable the Agent
-
Enable the Agent toggle
- Turn on the agent to make it available for use
-
Choose the LLM Model:
- Select which AI model this agent should use.
Model Selection Tip: Use higher quuality models for critical agents that need deep understanding. Use smaller Models for simpler tasks to save costs.
Step 5: Add a Connection
Now you'll connect your agent to an external service (like Jira, Confluence, or a custom API).
- Click "+ Add Connection"
- Fill in the connection details:
For Jira Connection:
Connection Name (Affects chat results)
- Enter a descriptive name, e.g., "Jira"
- This name is used by the system to identify when to use this connection
Description (Affects chat results)
- Brief description, e.g., "Jira"
- Helps the routing system understand this connection's purpose
Atlassian Base URL
- Your Jira instance URL
- Example:
https://junet-team.atlassian.net
Atlassian Username
- Your Atlassian account email
- Example:
user@company.com
Atlassian API Key
- Generate this from your Atlassian account settings
- Will be displayed as dots (••••••••) for security
User Groups (Optional)
Select which user groups can use this connection:
- "All Users" - Everyone in your organization
- Specific groups - Limit access to certain teams
Configuration Options
Set as Default
- Toggle on if you want this to be the default connection
- Use this connection as the fallback when no specific connection is chosen
Enabled
- Toggle on to enable this connection for use
- You can temporarily disable connections without deleting them
Step 6: Create the Connection
- Review all your settings
- Click "Update Connection" (or "Create Connection" if new)
- Wait for the confirmation message
Connection created! Your agent can now access the external service.
Step 7: Verify Agent is Active
After configuring your agent and connections:
-
Go back to the Chat UI
- Click the back button or navigate to the main chat
-
Open Active Agents
- Look for the robot icon (🤖) in the chat interface
- Click on it to see a list of active agents
-
Verify your agent is listed
- You should see your configured agent in the "Active Agents" list
- Example: "Jira" with identifier "JIRA"
Testing Your Agent
Try asking a question related to your agent's domain:
For a Jira Agent:
- "What are my open tickets?"
- "Show me high-priority issues"
- "What's the status of project XYZ?"
For a Confluence Agent:
- "Find documentation about deployment"
- "What are the onboarding guidelines?"
- "Show me the latest meeting notes"
For a Custom API Agent:
- Questions specific to your API's domain
- The agent will use your connection to retrieve relevant data
Troubleshooting
Agent Not Appearing in Active Agents
Possible causes:
- Agent is not enabled (check toggle in Step 4)
- No connections are configured
- Connection is disabled
- User group restrictions
Solution:
- Go back to Admin Panel → AI Configuration
- Verify agent is enabled
- Verify connection is enabled
- Check user group permissions
Connection Fails to Authenticate
Possible causes:
- Invalid API key or credentials
- Incorrect base URL
- Service is down or unreachable
- Firewall or network restrictions
Solution:
- Verify your credentials are correct
- Test the API key in the external service
- Check the base URL format
- Ensure Junet can reach the external service
Agent Doesn't Respond to Questions
Possible causes:
- Agent name/description doesn't match query intent
- Router Agent can't determine this is the right agent
- Connection issues
Solution:
- Make agent name and description more specific
- Try asking more explicit questions
- Check connection status in Admin Panel
Best Practices
Naming Conventions
Use descriptive names: Name your connections clearly (e.g., "Jira Support Tickets", "DevOps Confluence Space") so the routing system can make better decisions.
Security
- Rotate API keys regularly for security
- Use service accounts instead of personal accounts
- Limit permissions to only what the agent needs
- Review user group access periodically
Organization
- Group related connections by team or project
- Document agent purposes clearly
- Test agents after configuration changes
- Keep credentials updated when services change