Actions in Chat
Access integrations, Agents, Skills, Knowledge bases, Prompts, and Workflows in chat using @.
Actions in Chat
Actions in Chat brings your tools directly into any conversation. Type @ to access integrations, Agents, Skills, Knowledge bases, Prompts, and Workflows.
How Actions in Chat Works
Trigger the action menu
Type @ in any chat input field to open the actions menu. This works in both regular chats and when conversing with specific Agents.
Search and select your tool
Start typing to search through your available options, or browse through the first 20 items displayed. The search covers:
- Integrations: Connect to external services and APIs
- Agents: Access specialized AI helpers you've created or that are shared with you
- Skills: Reuse packaged instructions and tools
- Knowledge bases: Reference searchable document collections
- Prompts: Use templates from your prompt library
- Workflows: Trigger automations you have access to
Confirm your selection
Either press Enter to select the highlighted option or click directly on the tool you want to use. The chat interface will update to show your selection.
Verify the connection
Once added, you'll see the tool's logo and name displayed in blue within the chat interface, confirming the active connection.
Adding Multiple Tools
After adding your first integration or tool, a + button appears in the chat interface. Click this button to add additional tools to the same conversation.
This approach works well when you know you need multiple specific tools for a complex task.
You can type @ again at any point in the conversation to add more tools. This method feels natural when you discover you need additional resources mid-conversation.
Both methods give you the same functionality, so choose whichever feels more intuitive for your workflow.
Key Differences from Agent Integrations
- Agent Integrations — Programmatic Control: Integrations are pre-configured with specific actions and workflows defined during Agent creation. Predictable Behavior: The Agent knows exactly which actions to call and when, based on your setup.
- Actions in Chat — AI-Driven Selection: The model analyzes your request and chooses appropriate actions from available integrations dynamically. Flexible Access: You have the same integration capabilities as Agents, but with real-time decision making.
Cross-Context Usage
Actions in Chat works seamlessly across different conversation types:
- Regular Chats: Access any tool to enhance your standard conversations
- Agent Conversations: Add integrations or call other Agents while chatting with a specific Agent
- Mixed Workflows: Combine multiple Agents, integrations, and knowledge sources in a single conversation
Troubleshooting
Check permissions: Ensure you have access to the integration, Agent, Skill, Knowledge base, Prompt, or Workflow you're looking for.
Verify spelling: Double-check the name you're typing matches the actual resource name.
Try broader terms: If searching for a specific name doesn't work, try searching for related keywords.
Confirm integration status: Check that the integration is properly configured and active in your workspace.
Review permissions: Ensure the integration has the necessary permissions to perform the requested actions.
Check connection: If the integration's connection expired or was revoked, you'll see a reauthorize prompt in chat. Learn what this means and how to reauthorize your OAuth connection.
Next Steps
Now that you understand Actions in Chat, explore these related features:
- Creating Integrations: Build custom integrations for your specific workflow needs
- Agent Creation: Design specialized Agents that work seamlessly with Actions in Chat
- Knowledge bases: Search document collections with @mentions
FAQ
Use an action when ajan should do something in another tool, retrieve information from an integration, or trigger a connected capability. Use normal chat when you only need reasoning, writing, summarization, or analysis without interacting with another system.
The action may not be enabled, the user may lack permission, the connected account may not have access, or the prompt may not clearly require the action. Check the integration connection, action availability, scopes, and the exact request.
Actions receive the information needed to perform the requested operation, based on the action configuration and current conversation. Results from the action can be added back into the chat context and may influence the next model response.
Yes. When an action needs your confirmation, its inputs appear in the chat so you can review and edit them first. Rich text fields like email bodies show a rendered Preview of the content, with a Source view for the underlying HTML or Markdown.