> For the complete documentation index, see [llms.txt](https://docs.nexos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexos.ai/workspace/integrations.md).

# Integrations

The **Integrations** page is where you connect third‑party tools to your team’s workflow. It brings your external systems into nexos.ai so your team or you can use them where integrations are supported.

### What you will find on this page

* **Popular integrations**\
  A set of commonly used integrations (based on what other teams use) so you can quickly start with the most popular options.

<figure><img src="/files/buS1jhkohQllTw5UhBhS" alt="" width="563"><figcaption></figcaption></figure>

* **Active and All views**\
  Use **Active** to see only integrations currently enabled for your organization, or **All** to browse everything available.
* **Search and Category filter**\
  Use **Search** to find an integration by name, or **Category** to filter the list (for example, Collaboration, Productivity, Developer Tools, DevOps).
* **Integration list with status**\
  Each integration shows its **status** (Active or Inactive) and when it was **last modified**, so you can track recent changes.
* **Available integrations:** Atlassian MCP server, GitHub MCP server, GitLab MCP server, Google Calendar, Google Drive, Google Mail, HiBob, Looker, Microsoft Calendar, Microsoft OneDrive, Microsoft Outlook, Microsoft SharePoint, Microsoft Teams, Slack, Google Ads and BigQuery.

<figure><img src="/files/s69aBEWKYQwQgvH1Bo6S" alt="" width="563"><figcaption></figcaption></figure>

### Activate or deactivate an integration

1. Open **Settings** and go to **Organization → Integrations**.
2. Find the integration you want (use **Search** or **Category** if needed).
3. Change its status to **Active** (enable) or **Inactive** (disable).

### Configure a specific integration

To enable and set up an integration end-to-end, follow the dedicated setup page for that integration (for example **Google Calendar**, **Google Mail**, **Slack**, and others).

### Where you can use integrations

Once an integration is enabled for your organization, you can use it anywhere your workspace supports tools, such as:

* **Chat**
* **Agents**&#x20;

### In Chat

1. Open **Chat.**
2. Select the **Tools** icon.
3. Turn on the integration you want to use for that conversation.

{% hint style="info" %}
If you see **Connect** instead of a toggle, it means you do not have a valid sign-in token for that tool yet. Select **Connect** to sign in and approve access, then return to nexos.ai and enable the integration from **Tools**.
{% endhint %}

<figure><img src="/files/jpuMpfIIbwWItwLRzgfA" alt="" width="563"><figcaption></figcaption></figure>

### In Agents

Add integration actions to give your agents access to external tools:

1. Open **Agents** and select the agent you want to update.
2. Select the **Studio** icon, then open **Settings**.
3. Scroll down to **Integrations**, then enable the integration you want the agent to use.
4. **Save** your changes, then test the agent by asking it to pull context from the connected source (for example, “Summarize the latest updates from Slack” or “Find the relevant Confluence page and summarize it”).


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.nexos.ai/workspace/integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.