Capability Catalog
Nexus exposes a governed catalog of tools to the AI Assistant. These "Capabilities" allow the system to securely interact with your business systems under your direct authorization.
Audience: All users looking to understand what the AI can do and how it manages data.
Current Version
1.0
Documentation aligned to the current operational build of Chat, Automations, Contacts, and workflow runtime.
Scope
1
A standalone documentation page with a stable URL you can share directly.
Quick Start
How the system is meant to be used
Step 1
Read the platform overview first so you understand how Chat, apps, and runtime work together.
Step 2
Start your first conversation in Chat with a real business outcome, not just a general prompt.
Step 3
Let Nexus turn that intent into a durable record, workflow, or next-step artifact.
Step 4
Connect the systems required for context, communication, and execution as setup requires.
Step 5
Move into the relevant app surface to review, manage, approve, and operate the resulting work.
Operating Principle
Chat compiles. Apps operate. Runtime executes.
Nexus is not a chatbot that happens to call tools. It is a structured operating system where conversational intent is translated into durable records, validated state, and auditable actions.
This docs site is the product-level reference for how that model works today and how the current 1.0 surfaces fit together.
Audience
All users looking to understand what the AI can do and how it manages data.
Capability Catalog
Nexus exposes a governed catalog of tools to the AI Assistant. These "Capabilities" allow the system to securely interact with your business systems under your direct authorization.
Philosophy
The AI should never have "black box" access. Every capability is an explicit, described tool that maps back to a specific integration, operation, and security scope.
Technically Managed By
- Core Tools: Identity context, connection status, and model orchestration.
- Connectors: Platform-specific tools for Google, Microsoft, GitHub, Slack, HubSpot, etc.
- Governed Access: Every tool call is logged, traceable, and subject to user-authorized scopes.
How Users Should Use and Manage It
- 1Refer to this catalog to understand what the AI can help with.
- 2Check your integration status in Settings if the AI reports a connection issue.
- 3Use the chat traces to see exactly which tools the AI is calling during a task.
How It Fits in Nexus
- The Capability Catalog is the "hand-eye coordination" of the Nexus OS.
- It defines the boundary between conversational reasoning and physical execution.
- It ensures broad platform transparency across all connected services.
What Matters
- Communication: Unified Email (Gmail/Outlook), Calendar, Slack messaging, and Microsoft Teams.
- Sovereign Files: OneDrive, SharePoint, and local Workspace file management (read/write/list).
- Development: GitHub repo management (tree, sync, commit, push, PR), and Brave Search / URL Fetching.
- Social & CRM: LinkedIn (personal/company), X/Twitter (threads/replies), HubSpot, and Trello.
- Infrastructure: Coolify project/service management, deployments, logs, and database backups.
- Publishing & Media: Ghost CMS (posts/newsletters), and DALL-E 3 image generation.
- Integration Lab: Scaffold and register new custom tools by reading API documentation URLs.
Reference Notes
Next Step
Use the docs as the product contract.
As new apps and runtime behaviors ship, extend this documentation hub first so users and internal teams have one clear reference for how Nexus is supposed to work.