Connect to outside systems: Microsoft 365, the Bridge and APIs

Your module can use Microsoft 365, reach machines inside your own network, and work with outside services, without anyone typing a password into it.

Copy page for AIUpdated November 9, 2026

Your work doesn't stop at the edge of Data Visions, and neither do your modules. There are three doors out, and each one is locked down so a module only goes where it said it would.

Integrations: Microsoft 365 and more

Your workspace connects an outside service once, under System settings › Integrations, and decides which modules may use which parts of it: the mailbox, the calendar, the files. Your module never holds a password or key. Today that's Microsoft 365; more are coming.

Example: a support module reads the help mailbox and turns each email into a ticket.

See Integrations.

The Bridge: inside your own building

The Bridge is a small program on a computer inside your company's network. It lets your modules reach things the internet can't: a machine on the shop floor, a server in the back office, a camera system. Data Visions grants a module the Bridge; your Workspace Admins see the Bridges under System settings › Bridges.

Example: a maintenance module reads the run hours off a machine every night.

See The Bridge.

Bridge connectors: on a person's PC

The Bridge on someone's own computer has connectors. The most loved one: shared folders. Your agent can ask to see a folder on someone's PC, and they say Once or Always right there on their screen. Nothing is shared until they say yes.

See Bridge connectors.

Outside APIs

A module can also call a service on the internet directly, like a weather or shipping service. It must declare the address first, and the module check reviews it. See Outside hosts and Python packages.

And the other way in: AI connectors

Claude, ChatGPT and other AI apps can connect to your workspace and use your modules for you. See Build modules with Claude.

Can't find what you need? Contact support.