Integrations
Integrations connect Nexus to the systems that provide context and execution power, including communication tools, CRMs, calendars, social channels, and other business platforms.
Audience: Operators connecting source systems and engineers extending the integration catalog.
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
Operators connecting source systems and engineers extending the integration catalog.
Integrations
Integrations connect Nexus to the systems that provide context and execution power, including communication tools, CRMs, calendars, social channels, and other business platforms.
Philosophy
Nexus should feel like one operating system, not a collection of disconnected app logins. Integrations are how external systems become usable context and executable capability inside the platform.
Technically Managed By
- Integrations manage account connections, credentials, scopes, and connector health.
- Connected systems feed Chat, Contacts, Inbox, Calendar, and Automations with live context and execution capability.
- Workflow readiness depends on whether the required integrations and bindings are present and healthy.
How Users Should Use and Manage It
- 1Connect the systems you want Nexus to see, reason over, or act through.
- 2Review scopes, health, and connection status before relying on an integration in automation.
- 3Reconnect or reauthorize stale integrations before troubleshooting downstream workflow issues.
How It Fits in Nexus
- Integrations are the connectivity layer of Nexus.
- They make external tools part of the operating system instead of separate silos.
- They are a prerequisite for many workflows, communication features, and identity resolution behaviors.
What Matters
- Integrations feed workflow execution, contacts identity resolution, and inbox/calendar context.
- Automation setup should mark workflows as setup-required when credentials or bindings are missing.
- The platform already exposes operational tools for integration-backed automation registration.
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.