Integrations

Connect Mercora to the tools your team already uses, and control what Mercora may do with each one.

Integrations connect Mercora to the mailboxes, chats, spreadsheets and systems your team already works in. This page shows where they live and how admins control what Mercora may do with each one.

Find your integrations

Every integration is under Settings → Integrations, which has two halves:

• Workspace: one connection for everyone, set up by a workspace admin. Members don’t see this half.
• Personal: your own accounts, such as your WhatsApp number or Microsoft sign-in, so the Copilot can work with them.

Some workspace connections, such as WhatsApp and Agiblocks, are set up by the Mercora team, so there is no key to paste. Each tile shows its status:

• +: ready to connect. Click the tile to open its page.
• A check mark: working. A warning sign: something needs attention; open the page to see what.
• Pending or Off: still connecting, or switched off for the workspace.
• Not set up: a status-only tile, such as Email inbox (Email ingestion) or Vessel tracking, that isn’t set up for your workspace yet. Ask the Mercora team.
• Coming soon: not available for your workspace yet, and can’t be opened. Some tiles, such as QuickBooks Online, stay Coming soon until an admin turns on their module.

Available integrations

• Microsoft 365: shared mailboxes, SharePoint files and Teams.
• WhatsApp: the Copilot on your phone, deal and hedge capture from groups, and approvals by reply.
• Google Sheets: a hedge sheet that Mercora keeps up to date.
• QuickBooks Online: connect your QuickBooks Online companies.
• External systems (Agiblocks): push reviewed work to your CTRM, and let the Copilot read its reporting data.

Control what Mercora may do

Connecting an app doesn’t let Mercora do everything with it. Each integration page lists, under What automations can do with it, the actions Mercora can take with that app.

• Every action starts off. A workspace admin switches on, under Allowed, the actions automations and the Copilot may use. The heading counts them, such as “0 of 5 actions allowed”.
• Actions that only read Run on their own once allowed.
• Actions that change Mercora or leave it Always ask first: a person clicks Approve on each call. Each write is sent only once, so a retry never makes a second one.

The Agiblocks actions before the app is connected: every action starts off, and each row says whether it only reads or leaves Mercora.

Connecting is only the first step. Many features behind an integration also need their own module, such as Deal Capture, Hedging or External systems sync, and each member needs the matching role permissions.

Next steps

• Microsoft 365: most workspaces start here.
• Automations: put a connection to work in a standing instruction.