Neocortex
Build & connect6 min read

BUILD & CONNECT

Connect your systems

Plan integrations and grant only the access a workflow needs.

Overview

In the current Neocortex dashboard, Settings → Integrations presents a searchable provider list, saved connection statuses and the Composio catalogue. Provider availability and setup depend on the deployment; this guide distinguishes the current UI from general integration design advice.

01

Inventory the need

Name the system, business owner, data involved, required operations and expected outcome.

02

Choose the narrowest access

Prefer scoped identities and read-only access when writes are not necessary. Avoid using a personal administrator account for automation.

03

Configure securely

Follow the connector’s current setup guidance and store credentials in approved secret storage. Never paste real tokens into a support request.

04

Test permissions and failures

Verify authorised and unauthorised access, expired credentials, rate limits, timeouts and partial failures.

05

Operate the connection

Assign an owner, review scopes periodically and monitor failures and unusual activity.

06

Plan for change

Document rate limits, API versioning, data mapping, deprecation and the process for safely disconnecting the integration.

07

Connect in Neocortex

Open Settings → Integrations, find the provider and follow its supported API-key or OAuth flow. Confirm the resulting connection status; do not assume a redirect or pasted key means the connection is active. If the page reports that credential storage or the connections table is not ready, resolve the in-product administrator warning before relying on saved connections.

Worked example

Integration readiness checklist

Before connecting a business system, document the operating boundary and the proof that the connection is safe to use.

  1. 1Name the system owner, business purpose and data classification.
  2. 2List required operations and explicitly exclude unnecessary scopes.
  3. 3Configure credentials through approved secret storage, not source code or prompts.
  4. 4Test valid access, denied access, expired credentials and rate limits.
  5. 5Verify the expected result in the source system and document how to disable the connection.

Was this guide useful?

Send feedback or flag a gap. Include the article link so the team can improve the right guide.

Suggest an improvement
Neocortex documentation · Digital Response