What are connectors?
Business Summary: Connectors link Nimbus to the tools your team already uses — so AI runs can read live data and, when you approve, take action in those systems.
A connector is a secure link between Nimbus and an external system — your CRM, ERP, document store, messaging platform, or data warehouse. Connectors give agents the data and tools they need to produce credible analysis and, when approved, update your systems of record.
Without connectors, agents can only work from what you type in chat or upload manually. With connectors, they pull live metrics, query records, and — through governed Action connectors — post updates back to the tools your teams already use.
Intelligence vs Action connectors
Nimbus organizes connectors into two types. The type tells you whether a connector reads data or writes changes.
| Type | What it does | Example |
|---|---|---|
| Intelligence | Reads and analyzes data — does not modify external systems | Salesforce reads your pipeline; Google Analytics pulls traffic metrics |
| Action | Writes or triggers changes after human approval | HubSpot updates a deal stage; Slack posts an approved summary |
flowchart LR
Intel[Intelligence reads] --> Agent[Agent analysis]
Agent --> Approval[Human approval]
Approval --> Action[Action writes]
Action --> External[External systems]
Most teams connect Intelligence sources first, then enable Action connectors when they are ready for governed automation.
See Intelligence vs Action connectors for phase details and governance rules.
Why connectors matter
Connectors answer three practical questions before you spend NTUs on a run:
- Can the agent see the data it needs? Intelligence connectors supply CRM pipelines, finance actuals, news signals, and more.
- Can the agent act when you approve? Action connectors enable writes — messages, spreadsheet updates, ticket creation — under governance rules.
- Is setup credible before the run starts? Agents declare connector requirements so Nimbus can tell you what is missing upfront.
Connecting sources early is one of the highest-impact steps in onboarding. See the Onboarding checklist.
How connectors fit your workflow
You connect sources once at the organization level under Connectors in the sidebar. When you scope a workstream, you assign which connectors that goal will use. Agents pull from those connections during each run.
| Concept | How connectors fit |
|---|---|
| Agent | Each agent declares which connectors it expects for credible runs. |
| Workstream | You bind connectors when scoping a goal in Perception. |
| Company Wiki | Document connectors can sync files into wiki vaults for search. |
| Governance | Action writes typically require human-in-the-loop approval before execution. |
Connector availability
Each card in the catalog shows a status badge:
| Badge | Meaning |
|---|---|
| Available | You can connect and use this connector now. |
| Beta | Early access — connectable, but behavior may change. |
| Coming Soon | Listed for planning; connect is disabled until release. |
Browse the full list on Connectors in the sidebar. See Connector catalog.
Ready to try it?
- Open Connectors in the sidebar.
- Search for your system (for example Salesforce, Google Drive, or Slack).
- Click the connector card and follow the sign-in flow to authorize access.
- Return to the Onboarding checklist or Creating a workstream to assign the connector to a goal.
Step-by-step guide: Connecting a connector.
Example scenario
A finance lead connects Google Drive (Intelligence) so the Finance agent can read board-pack templates, and Slack (Action) so approved summaries post to #board-prep after a checkpoint. They connect both once at the org level, then bind them when scoping a Board prep — Q2 workstream.
What to do next
- Connect a system → Connecting a connector
- Read vs write rules → Intelligence vs Action connectors
- Browse the catalog → Connector catalog
FAQs {#faqs}
Q: Do I need connectors before creating a workstream? A: You can create a workstream without them, but runs will be weaker or blocked if the agent requires data you have not connected. Connect Intelligence sources first.
Q: Can one connector be both Intelligence and Action? A: Some integrations support both phases. The catalog shows which phase each binding uses.
Q: Who can connect connectors? A: Typically org admins or members with connector permissions. See Managing connections.
Q: Do connectors sync to the Company Wiki? A: Document connectors can feed wiki vaults. See Connectors and the Wiki.
Q: What if my app is not listed? A: Browse the full catalog — many SaaS apps are available. See Connector catalog or ask support about Enterprise options.