Integrations
Employees act through your real business tools — email, CRM, accounting, shops, social. You connect a tool once; you decide which employees may use it.
Connect a tool
Connect from the Integrations page — usually by pasting an API key or completing a sign-in. The catalog spans email & calendar, files, CRM & sales, support, team messaging, project & dev, finance & payments, shops & shipping, marketing, analytics, HR, e-signature and automation.
Credentials are stored encrypted and never shown back in full. The tools you named at signup appear pre-starred.
- 1Find a tool by name…
- 2…or browse by category. Connecting is a one-time key or login.
- 3Model providers power the thinking itself; the green dot marks what's active.
- 4Tool not in the catalog? “Build a connector” wires up any API or webhook.
Who gets access
Employees only use connectors you gave them access to — set per employee in its editor, or let the manager grant access on your go-ahead. Custom connectors let you wire in any tool with an HTTP API, so even an app not in the catalog can be added.
Reading vs. writing
On the Security page you can decide per connected tool — separately for reading and writing — whether employees act freely, must ask a human first, or are blocked. «Read Gmail but never send» is one toggle. Anything you leave alone keeps the default: reads run, writes follow the approval rules.
Swiss specifics
Swiss needs are first-class: Swiss QR-bills are read deterministically (checksum-verified), not guessed at by a model. The Zefix connector looks up the commercial register — company, UID, legal seat — instead of guessing. Pingen turns a PDF into real postal mail, always drafted first; dispatch needs your approval.
«Coming soon» tiles
Some tools are visible in the catalog but not yet connectable — either the provider requires partner onboarding, or its API terms require a dedicated sign-in integration rather than a pasted key. Those return once the proper flow ships.