Just because you have connected integrations to your elvex account doesn't mean every agent automatically has access to them. Each agent needs to be explicitly given access to the integrations it should use. This is true whether you built the agent yourself or you're using one someone else created.
The key concept
When you connect an integration to your elvex profile, you're giving elvex permission to use that tool on your behalf. But agents are scoped independently; no agent inherits your full integration access automatically. You decide which integrations each agent can use, and users decide which of their personal accounts each agent can act on.
If you built the agent
As the agent builder, you need to enable integrations in the agent configuration before the agent can use them:
Open your agent and click View full config
Navigate to the Actions section
Find the integrations section and toggle on the integrations your agent needs
To limit what the agent can do, expand an integration and enable only the specific actions it requires rather than all actions
Save your changes
Only integrations your company admin has enabled at the global level will appear here.
If you're using an agent someone else built
The agent builder controls which integrations the agent has access to. As a user, your job is to connect your own personal accounts to those integrations so the agent can act on your behalf. You can do this in two ways:
Option 1: Through the chat
Simply start a conversation with the agent and ask it to use an integration. If your account isn't connected yet, the agent will prompt you to connect it.
Option 2: Through the Actions Directory
Open a conversation with the agent
Click the Actions Directory icon in the top right corner of the chat
Find the integration you want to connect and click Connect
Follow the authorization flow to link your personal account
Best Practices
Security and permissions
Principle of least privilege: Only enable the actions your agent actually needs; more access means more surface area for unintended behavior
Review regularly: Periodically review which integrations and actions are enabled
Test functionality: Verify that enabled actions work as expected before sharing an agent with your team
Performance
Selective enabling: Don't enable all actions if your agent only needs a few
Remove unused integrations: Disable integrations that aren't being used
Agent design
Match use case: Enable integrations that align with your agent's specific purpose
User expectations: Document which integrations your agent uses in its description or welcome message so users know what to connect
Troubleshooting
Actions not available
Check that your company admin has enabled the integration at the global level in Settings > Integrations
Verify the integration is toggled on at the agent level in the Actions settings
Confirm you have a personal connection to the integration
Connection issues
Try disconnecting and reconnecting the integration from your personal settings
Verify you have the necessary permissions in the external service
Check if the integration requires additional configuration
Actions not working in conversations
Confirm the specific actions are enabled, not just the integration itself
Review the agent's instructions to ensure it knows how to use the actions
