> ## Documentation Index
> Fetch the complete documentation index at: https://docs.langdock.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Actions in Chat

> Access any integration, Agent, Folder, or saved prompt directly in chat using the @ symbol for seamless workflow integration.

# Actions in Chat

Actions in Chat transforms your Langdock experience by bringing all your tools directly into any conversation. Instead of switching between different interfaces, you can access integrations, Agents, Folders, and saved prompts with a simple @ symbol, creating a unified Chat where everything you need is just a mention away.

<Info>
  Actions in Chat works in both regular chats and Agent conversations, giving you consistent access to your tools regardless of where you're working.
</Info>

<Info>
  **Knowledge Folders are now called Folders.** Find them in the [Library → Folders](/en/using-langdock/library/folders).
</Info>

## How Actions in Chat Works

<Steps>
  <Step title="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.

    <Tip>
      The @ symbol acts as your universal access point to all Langdock resources, making it easy to remember and use consistently.
    </Tip>
  </Step>

  <Step title="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 shared with you
    * **Folders**: Reference specific document collections
    * **Saved Prompts**: Use templates from your prompt library

    <Note>
      Only the first 20 matching results appear initially. Type specific names to narrow down results and find exactly what you need.
    </Note>
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.

    <Check>
      The visual indicator ensures you always know which tools are active in your current conversation.
    </Check>
  </Step>
</Steps>

## Adding Multiple Tools

<Tabs>
  <Tab title="Using the + Button">
    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.
  </Tab>

  <Tab title="Using @ Again">
    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.
  </Tab>
</Tabs>

## Key Differences from Agent Integrations

<CardGroup cols={2}>
  <Card title="Agent Integrations" icon="robot">
    **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.
  </Card>

  <Card title="Actions in Chat" icon="at">
    **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.
  </Card>
</CardGroup>

<Warning>
  Actions in Chat can only access integrations and tools that you could also use when creating an Agent. The available actions are determined by your permissions and the integrations configured in your workspace.
</Warning>

## 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

<Tip>
  This cross-context functionality is particularly powerful for complex workflows where you might need to consult multiple specialized Agents or access different data sources within the same conversation thread.
</Tip>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Tool not appearing in search">
    **Check permissions**: Ensure you have access to the integration, Agent, or Folder 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.
  </Accordion>

  <Accordion title="Integration not responding">
    **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**: Some integrations may require re-authentication or have temporary connectivity issues.
  </Accordion>
</AccordionGroup>

## Next Steps

Now that you understand Actions in Chat, explore these related features:

* **[Creating Integrations](/en/using-langdock/guides/integrations/create-integrations)**: Build custom integrations for your specific workflow needs
* **[Agent Creation](/en/using-langdock/guides/agents/agent-creation)**: Design specialized Agents that work seamlessly with Actions in Chat
* **[Folders](/en/using-langdock/library/folders)**: Organize your documents for easy access via @ mentions

<Check>
  Actions in Chat creates a unified interface where all your Langdock tools work together, eliminating the need to switch contexts or remember different access methods.
</Check>