> ## Documentation Index > Fetch the complete documentation index at: https://docs.mercora.io/llms.txt > Use this file to discover all available pages before exploring further. # Integrations > Connect Mercora to the tools your team already uses: Microsoft 365, WhatsApp, Google Sheets, QuickBooks Online and your CTRM. Admins connect for the workspace; each member can connect their own accounts. Integrations connect Mercora to the systems around it: the mailboxes and chats where deals and documents arrive, the spreadsheets your team keeps, and the CTRM or accounting system you book in. This page helps you find where each one is set up and how admins control what Mercora may do with it. Every integration lives under **Settings → Integrations**, with a search box at the top. ## Workspace and personal connections The Integrations page has two halves. | | **Workspace** | **Personal** | | - | - | - | | What it is | One connection for the whole workspace: "Set up once for everyone". | Your own account, so the Copilot can work with it: "Your own accounts, for Copilot". | | Examples | Microsoft 365, WhatsApp, Google Sheets, Agiblocks, QuickBooks Online | Your WhatsApp number, your own Microsoft 365 sign-in | | Who connects it | Workspace admins only. Members don't see this half. | Each member, for themselves | Some workspace connections are set up by the Mercora team for your workspace, rather than with a key you paste, for example WhatsApp and Agiblocks. Their pages show whether the connection works and let admins choose what Mercora may do with it. Each tile shows where it stands on the right: | Tile shows | Meaning | | - | - | | **+** | Ready to connect. Click the tile to open its page. | | A check mark | Connected and working. | | A warning sign | Connected, but something needs attention. Open the page to see what. | | **Pending**, **Off** | Waiting to finish connecting, or switched off for the workspace. | | **Not set up** | A status-only tile, such as **Email inbox** or **Vessel tracking**, that isn't set up for your workspace yet. Ask the Mercora team. | | **Coming soon** | Not available for your workspace yet, such as ION Aspect, Dynamics 365 Business Central or Xero. The tile can't be opened. | Some tiles read **Coming soon** until a workspace module is turned on. For example, **QuickBooks Online** stays Coming soon, and its page can't be reached, until an admin turns on the **QuickBooks Online** module. See [QuickBooks Online](https://docs.mercora.io/integrations/quickbooks.md). ## What Mercora may do with a connection Connecting an app doesn't let Mercora do everything with it. On an app's page, **What automations can do with it** lists each action Mercora can take, and whether it: * **Reads**, and then **Runs on its own**, or * **Changes Mercora** or **Leaves Mercora**, and then **Always asks first**: a person approves each call. Every action starts off. A workspace admin switches on, one by one, under **Allowed**, what automations and the Copilot may use; the heading counts how many are on, such as "0 of 5 actions allowed". Anything that leaves Mercora always waits for an **Approve**, and each write is sent only once, so a retry never makes a second one. While an app isn't connected yet, **Before it runs** says so instead. ![The What automations can do with it table, with the Action, What it does, Before it runs and Allowed columns](https://mintcdn.com/placeholder-f4ffdeec/22McaegbdDRSI41b/images/integrations/automation-actions-table.png?fit=max\&auto=format\&n=22McaegbdDRSI41b\&q=85\&s=1231a9cfbc589f8f2e0241d7a57e343c) The Agiblocks actions before the app is connected: every action starts off, and each row says whether it only reads or leaves Mercora. ## Available integrations > **[Microsoft 365](https://docs.mercora.io/integrations/microsoft-365.md)** > > Email, SharePoint files and Teams for the Copilot and automations, as your workspace or as each member. > **[WhatsApp](https://docs.mercora.io/integrations/whatsapp.md)** > > The Copilot on your phone, deal capture, hedge requests and approvals from WhatsApp. > **[Google Sheets](https://docs.mercora.io/integrations/google-sheets.md)** > > A shared hedge sheet that Mercora appends to and completes with fills. > **[QuickBooks Online](https://docs.mercora.io/integrations/quickbooks.md)** > > Connect your QuickBooks Online companies to Mercora. > **[External systems (Agiblocks)](https://docs.mercora.io/integrations/external-systems.md)** > > Push invoices, B/Ls, contracts, deals and hedges to your CTRM, and let the Copilot read its reporting data. The workspace half also shows status-only tiles with nothing to set up there. **Email inbox** shows when the last forwarded trade email arrived (see [Email ingestion](https://docs.mercora.io/documents/email-ingestion.md)), and **Vessel tracking** shows whether live vessel positions are available. ## Who can use what Connecting an integration is the first step. Using it also depends on: * **Modules.** Many features behind an integration have their own module, such as **Deal Capture**, **Hedging** or **External systems sync**. See [Modules](https://docs.mercora.io/concepts/modules.md). * **Permissions.** Each member still needs the role permissions for the data and actions involved. See [Roles and permissions](https://docs.mercora.io/concepts/roles-and-permissions.md). ## Next steps > **[Microsoft 365](https://docs.mercora.io/integrations/microsoft-365.md)** > > Most workspaces start here: mailboxes, SharePoint files and Teams. > **[Automations](https://docs.mercora.io/workflows/automations.md)** > > Put a connection to work in a standing instruction. > **[Modules](https://docs.mercora.io/concepts/modules.md)** > > Turn on the workflows that use your integrations. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.