Integrations — what each connection actually does

This page is a status matrix, not a capability list. For each connection it states what Business-Gym reads, what it writes, and what it only proposes for you to approve. Where something is not built, it says so rather than leaving it implied.

Nothing in the write column happens on its own. Every external write listed below is human-approved, and the hard floor means that does not change at any autonomy level.

What can each connection do today?

Your CRM is already there

Every workspace has a built-in CRM — Customers, Offerings, Deals, Contacts and Leads are held by Business-Gym itself, with nothing to connect and no set-up step. Microsoft Dynamics below is a connection for workspaces that are already set up for it — you do not need it to use the sales pages.

Connect your own Dynamics 365 — coming soon. It is not something you can switch on today. See Where does your CRM data live?.

Deals in the built-in CRM are yours to create, move and archive, with no approval step in between — Create and manage deals. A deal that a connected Dynamics masters is the exception: it stays read-only here and proposes its stage moves for approval, because Business-Gym is not its system of record.

Connection	Reads	Writes (all human-approved)	Proposes for approval
Microsoft 365 — mail	Shared and personal mailboxes, message headers and bodies on demand	Sends email from the connected mailbox	Draft replies, forwards, filing, tasks
Microsoft 365 — SharePoint	Sites and files, synced into your team’s knowledge	— nothing today	—
Microsoft 365 — Teams & calendar	Department mailbox calendars	— nothing today	The daily brief, staged for you to send
Microsoft Dynamics (Dataverse)	Customers, opportunities, contacts	Creates a lead	Customer field write-backs (see limits)
Google Ads	Campaign spend, impressions, clicks, conversions	— read-only by design	—
Meta — Facebook & Instagram	Ad performance, page and Instagram inbound	Publishes posts to a Page or Instagram	Budget changes proposed by the guard
LinkedIn	Conversations, via the desktop operator	Publishes posts	Marketing posts, staged before publishing
Stripe	Revenue, subscriptions, churn	Checkout and billing-portal sessions you start	Customer invoices, staged before issuing
Analytics (Clarity, PostHog, App Insights)	Usage, friction signals, telemetry	— read-only	Product observations for the copilot
DATEV	—	—	— not connected yet

What is Business-Gym allowed to write?

Four connections can change something outside your company, and each one waits for a person:

• Email — an approved draft reply leaves from your connected mailbox.
• Facebook and Instagram — an approved post publishes to your Page or Instagram account.
• LinkedIn — an approved post publishes to the connected LinkedIn account.
• Dynamics — an approved inbound lead is created as a CRM record.

That is the complete list. No other connector writes anywhere, and none of these four acts without an approval — see working the approval queue.

Tip

The write column is deliberately short. If a connector is not listed as writing, it cannot change anything in that system — which also means you can connect it without risk while you are still evaluating.

What are the current limits?

These are real limits today, not roadmap language. They are listed because finding them in the product is worse than reading them here.

DATEV is not connected. It is the most-requested connector and nothing reaches it. Uploading documents, setting payment status and attaching bank positions are all prepared but inactive.

SharePoint is read-only. Knowledge sync is one-way — into your team’s knowledge, never back into your sites.

Calendar is read-only. Business-Gym reads department calendars; it does not create or change events.

Customer field write-backs stage an approval that does not yet complete. The approval is recorded, but the value does not reach Dynamics. Creating a lead does work. Until this is fixed, treat a write-back approval as a note to yourself, not as a change to your CRM.

Google Ads is read-only by construction. This is a design decision, not a gap — Business-Gym reports on ad spend and cannot alter a campaign, budget or bid. Meta is the connector that can propose budget changes, and those changes still wait for you.

Instagram direct messages, Meta’s Conversions API and Custom Audiences are not active, even though the surrounding Meta connection is.

Caution

Some of these limits sit behind surfaces that look ready. If an action is listed above as unavailable, the interface offering it is preparation rather than a live path — check this page before relying on one.

What happens when a step needs a connector I have not configured?

It stops honestly and waits. The step reports that the connection is missing, and the work queues rather than continuing.

No result is invented and nothing is reported as done. This matters more than it sounds: the alternative — a step that quietly reports success it did not achieve — is the failure mode that makes an automated system impossible to trust. A visible stop is the intended behaviour, not a fault.

How do I connect something?

Connections are configured in the web app, under Integrations. Two are worth doing first because they carry the most value on day one: a knowledge source so your team has something to reason from, and a mailbox so it has real work arriving. Getting started walks through both in order.

Integration setup, like billing and permissions, is web-only — see who can approve, and where.

Why does this page list so many limits?

Because the alternative is worse for you.

A capability list that describes the roadmap reads better and costs you more: you plan around something that is not there, and you find out during an evaluation or, worse, in production. This page is written from the shipped behaviour — what the code actually does today — and it is re-checked when connectors change.

If something here is out of date, it is a documentation bug worth reporting: the matrix is meant to be the honest answer, not the flattering one.