Connect your tools and data

A calendar event or customer email helps the team when it is available alongside the related business record. Integrations manages supported connections and module settings, so you can choose which sources and capabilities your workspace uses.

Open Integrations in your workspace to inspect provider connections, module controls, and the MCP connection key. Which providers you have available depends on the adapters included in your installation, so a listed or planned provider is worth checking, not assuming, before you build a workflow around it.

Make your first connection useful

Choose a workflow before adding credentials. If you want to work with invoices, start with the Stripe invoicing example. If you want recurring customer billing, start with the Stripe subscriptions guide. If you want an external assistant to read and propose workspace actions, start with MCP setup. Connect only the accounts and permissions that workflow requires.

For a supported provider, follow its setup controls, verify the connection and inspect its reported state. Credentials are handled through the platform's server-only connection storage. Public module settings are for ordinary configuration; do not paste secrets into them.

After setup, test the intended workflow with a controlled record. Saving credentials establishes configuration, while a successful verified operation establishes that the connection works for that task. If the connection becomes degraded, inspect its failure and correct access or provider settings before retrying.

Connecting a service that is not built in

The open-source adapter interface is the route for adding another service or data source: a developer or coding assistant implements the authentication, maps incoming data to the right business records, and exposes whichever actions make sense to support. Start with integration adapters and inbound webhooks.

Being extensible means you can build that connection yourself, using the same interface every built-in adapter uses. It is a different claim than every service already having one ready to go, or any API being connectable with zero implementation work; the provider's own API, permissions, rate limits, and terms are what determine how much work that is.

Choose the capabilities available to a workspace

Optional modules control which areas of the application a workspace uses. Plugins can require particular modules or provider connections. Their individual guides explain setup, permissions, costs and what happens when you disable them.

Connect an external AI assistant

Generate a workspace MCP key from the integration controls and follow the client guide. The key is shown once. Store it as a secret in the client's configuration; do not put it in a chat message, screenshot or public repository.

The client uses the workspace's registered tools and approval rules. It can help with supported questions and actions while your records remain in the database you control. Providers may process data sent through their services, and connected AI or email usage can incur their normal charges.

Review configuration through the assistant

Ask AI and authorized MCP clients can read redacted connection status and prepare a provider disconnect, a Drive folder selection, a Google connection check or a bounded sync. Review the exact values and consequences in Work before approving. If the connection or configuration changes first, prepare a new preview and approve that version.

Drive selection accepts up to ten unique folder IDs. Saving the selection changes future reads and retains previously stored documents. A sync reads only the selected connected sources and records its results. Sources run in order; an incomplete source stops the remaining work. Completed work stays saved, so inspect the source receipts before retrying only the incomplete source.

Sync Workspace can sync Gmail and Calendar before you select Drive folders. Drive then records Not configured, with no Drive files read. A Drive-only sync requires a folder selection. If another sync is already running, Setup reports that no new sync started; this is not a completion receipt.

Disconnect removes the workspace's stored credentials and disables its environment fallback. Historical records remain, and an upstream request already in flight cannot be recalled. Reconnecting, entering or rotating secrets, granting Google consent and creating one-time integration keys require the secure human controls in Integrations. Never paste those values into an assistant conversation.