Integrations

schakl. runs on your own server and talks from there to the services your agency already uses: your payment provider, your bookkeeping package, your registrar, your DNS, Google Workspace, your marketing sources, the sites you host and your own scripts. Every integration uses your own account at that service. The key or token is stored encrypted against your organisation in the database rather than in a configuration file on the server, and you can replace or remove it at any time.

A module and an integration are different things

The two words are used precisely, and the difference decides where a setting lives.

• A module is a capability schakl. itself provides. It owns records and screens, and it is worth having with every third-party account in the world cancelled: clients, contacts, tasks, projects, hours, invoicing, domains, reporting.
• An integration is a conversation with somebody else’s service. It holds a credential for an outside account, and what it stores is a mirror of — or a pointer into — state that lives over there.

The test is one sentence: if the vendor went out of business tomorrow, is the thing gone, or is it merely poorer? Gone means integration. Poorer means module. Marketing is a module by that test even though every figure on it arrives through Google: the dashboard, the periods and the narratives are ours, and with the links removed it is an empty screen rather than an absent one.

That is why there are two screens, each first in the group of settings it governs:

• Instellingen → Modules (Settings → Modules) — what schakl. does for this workspace.
• Instellingen → Integraties (Settings → Integrations) — which services schakl. talks to.

Ticking an integration pulls in the modules it has nowhere to put its data without, and unticking a module tells you by name which integrations go with it — before you save, on a screen that does not list them.

Keys for your own scripts sit apart from both: personal keys under Instellingen → Mijn account (Settings → My account), section API en MCP, and keys that outlive somebody’s departure under Instellingen → Service-accounts (Settings → Service accounts).

Available, or on the roadmap

Every card says where it stands, and there are only two answers that matter:

Status	What it means
Available	There is a settings screen, a credential to fill in and a guide here. You can connect it today.
On the roadmap	There is nothing to connect. No screen, no field, no callback address. Those cards exist so you do not go hunting for something that is not there, and each says what to use instead.

What a green settings screen proves, and what it does not

Connecting proves your credential is valid. It does not prove that the payment method you want is switched on at the provider, that your host forwards the header the API needs, or that the amount on the first real invoice is right. Every guide here ends with a short first-run walk for exactly that reason — do it once, on a test key or a single domain, before you point clients at it.

Payments and accounting

Mollie Let clients pay an open invoice online with iDEAL, cards, Bancontact or PayPal; the confirmed payment becomes a payment line on that invoice by itself.

SnelStart Clients, issued invoices and articles into your books; who has paid comes back as an ordinary payment on the invoice.

Domains, sites and hosting

Cloudflare Read your clients' zones and DNS records, and put a real mechanism behind the domain status Doorverwijzing (redirect).

OXXA Pull the register from your registrar — expiry date, lock and nameservers — and write nameservers back.

WordPress One Application Password per website, and Rank Math's AI Visibility figures as a fifth marketing source.

Uptime Kuma The open-source monitor you already run, with monitors that become records instead of alerts.

Google

Google Workspace Calendar, Drive, Gmail and Contacts, connected per organisation with your own OAuth client and switched on per employee.

Google Ads Campaigns, spend and search terms — and, behind a policy, the budgets, keywords and exclusions you change.

Google Tag Manager A client's container: what is live, what is staged, and a publish that is its own permission.

Marketing sources Analytics, Search Console, Google Ads, SE Ranking and Rank Math as figures per client, on the client file and in your reports.

Your own scripts and assistants

REST API Anything the app can do, a script can too: one typed API with permissions per key.

API reference Every endpoint, grouped by area, with the permission each one requires.

MCP server The same API as a toolset for AI clients, with the same permissions per key.

Good to know

• A key is a permission, not a preference. Who may configure an integration is set per role under Instellingen → Rollen (Settings → Roles), separately from who may see the data it produces. A client with a portal login can never reach a connection screen.
• You connect per organisation, not per installation. There is deliberately no environment variable to put a Mollie or Cloudflare key in: it belongs to the organisation that uses it.
• A credential is a row, not a setting. An agency holds its own Cloudflare account and its clients bring theirs; one client site’s WordPress password is not “the” WordPress password. So nothing ever picks an account for you — with two, you are asked which.
• What comes from outside is kept as an observation. The integrations that mirror outside state store separately what schakl. decided and what it last found at the service, so “somebody changed this in the provider’s dashboard” becomes visible instead of being silently overwritten.
• Deleting a connected account changes nothing at that service. What the integration already produced — payments received, monitors created, tags published — stays where it belongs.

Read next

Modules What to switch on, and what a licence covers.

Invoicing The module an online payment lands in.

Domains The register and the zone that Cloudflare and OXXA fill.