Connectors and integrations let a Project read from or act through external systems. Cromo supports two complementary connection models.
Managed integrations
Managed integrations connect common business applications through an authorization flow. Cromo integrates with:
- Google Drive and Gmail;
- Microsoft OneDrive, OneNote, and Outlook;
- Notion;
- Slack;
- GitHub.
After connecting an application, select the files, folders, mail filters, or other resources that belong in the Project, then set the filters and sync schedule.
Synced content enters the Sources pipeline, preserving its external origin before any Knowledge proposal is reviewed.
MCP connectors
An MCP connector connects a Model Context Protocol server to Cromo. It can expose:
- Tools the assistant or a Workflow can call;
- Resources that provide context;
- Prompts supplied by the server.
Cromo connects to MCP servers over Streamable HTTP.
For servers with many tools, you can hide the full tool list behind search. This keeps the assistant’s active tool context smaller while still allowing it to discover a relevant operation.
Authentication
An MCP connector can use:
- no authentication;
- a bearer token;
- custom headers.
Secret values are encrypted at rest and are not shown again after saving. Keep the original credential in your password manager or secret-management system.
Treat a connector as an operational permission, not just a data source. A tool that can create, update, send, or delete external records needs narrower credentials and more testing than a read-only resource.
Project and Workspace access
Workspace admins choose each Project’s access level for a connection: no access, read access, or full access.
Users also need the appropriate Cromo role:
- Viewers can see connector information.
- Members can use approved connectors.
- Admins and Owners can create and manage connector configuration.
Test before using
Before relying on a connector:
- test the connection;
- inspect the tools, resources, and prompts Cromo can discover;
- verify the credential belongs to the intended account;
- run a read-only operation;
- test one safe write operation if writes are required;
- document ownership and rotation procedures.
For a webhook-triggered Workflow, test the Workflow webhook separately from any connector the Workflow calls.
Connection examples
Google Drive to Knowledge
Sync the current operating procedures from an approved Drive folder. Review the generated Knowledge before using it in chat or Workflows.
Gmail to complaint intake
Use a filtered Gmail connection for complaint messages. Preserve the original email as evidence, create a Ticket record, and keep customer-facing replies in draft.
CRM through MCP
Use a read-only CRM tool to inspect lead or customer records while validating the process. Add narrowly scoped write access only after the field mappings and side effects have been tested.
A connected example prompt:
Keep Source synchronization, operational connector access, and Workflow permissions separate so each can be reviewed independently. 