> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/administration/6.-applications.md).

# Integrations

Integrations are the external systems and platform services that Alludium can use during agent, task, project, and automation workflows.

**Location:** Administration -> Integrations

Integration management is an Administration surface. Members may still be asked to connect a personal account when a workflow needs access on their behalf.

The Integrations page brings applications, available tools, and authenticated connections into one place. Older docs may refer to Applications, Connections, and Tools as separate top-level sections; in the current product they are managed through Integrations.

## What Integrations Provide

Integrations let Alludium:

* Read live data from systems such as CRM, email, docs, project management, or search tools
* Perform actions such as creating records, updating fields, sending messages, or searching files
* Make specific tools available to agents, tasks, projects, and automations
* Track whether the workspace or user has the required connection

## Integration Detail

Opening an integration shows the integration workspace. Depending on the integration, this can include:

| Tab                  | What It Shows                                                               |
| -------------------- | --------------------------------------------------------------------------- |
| **Dashboard**        | Summary, health, linked agents, setup state, and recent connection context. |
| **Available Tools**  | The actions the integration exposes.                                        |
| **Your Connections** | Existing connections and connection setup options.                          |

## How Integrations, Connections, And Tools Fit Together

These three concepts still matter, but they now sit inside the Integrations model.

**Application** means the external system or platform capability, such as Google Drive, Slack, Affinity, Brave Search, or Alludium Docs.

**Connection** means authenticated access to that application. A connection can be user-scoped or workspace-scoped depending on the integration and sharing model.

**Tool** means a specific action exposed by the integration, such as searching docs, listing files, creating a task, or reading CRM records.

## Typical Setup Flow

1. Open **Integrations** from an Admin or Owner account.
2. Search for the system you want to use.
3. Open the integration detail page.
4. Review available tools.
5. Create or verify a connection if the integration requires one.
6. Attach the relevant tools to an agent, project setup, task workflow, or automation.

Some platform-provided integrations do not require a user API key. Others require OAuth, an API key, or provider-specific setup.

## Security Model

Connections are scoped and revocable. Agents do not receive raw credentials. Instead, Alludium uses the configured connection to call the relevant tool when the workflow is allowed to do so.

Before granting access, consider:

* Whether the connection should be personal or shared
* Which tools the workflow actually needs
* Whether write actions are required
* Which agents, tasks, or project setups will depend on the connection

## Troubleshooting

If a tool is not available:

* Check that the integration exists in Integrations.
* Check whether a connection is required.
* Open the integration detail page and review Available Tools.
* Confirm the agent, task, project setup, or automation has access to the tool.
* Reconnect or rotate credentials if the connection is inactive or expired.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alludium.gitbook.io/alludium-docs/administration/6.-applications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.