How to connect Nautis to Claude and ChatGPT

Connect Nautis to Claude ChatGPT when you want those chats to answer from your real workspace data instead of a pasted export. Nautis offers two ways to connect, per the Connect Claude, ChatGPT and other AI tools help (updated 31 Oct 2026): the MCP connector for Claude, ChatGPT, and other apps that support custom connectors (browser sign-in, no key to handle), and an API key for chatbot builders, scripts, and tools that ask for a fixed token, including ChatGPT custom GPT Actions. If you allow it, the tool can also create and update records. Writes wait for approval by default unless you change Agent Autonomy. This is different from Integrations, which goes the other way and lets Nautis agents act inside tools like Slack.

Connect Nautis to Claude ChatGPT: pick the right path

Find it by clicking your organization name in the sidebar, then the Developers tab. That tab holds API Keys, the connector and API addresses, and Connected AI Apps. Your plan must include developer access. If it does not, the Developers tab will not appear and the connector shows Not available on your plan. Organization Owners, Admins, and Developers can open the Developers tab. Only Owners and Admins can create or delete API keys. Any member of the organization can connect an AI app through the connector once they have the connector address; the app then acts as that person, limited by their role and by what is shared with them. Only Owners and Admins can approve writes that are waiting for approval.

Connect with the MCP connector

1. On the Developers tab, find MCP connector for Claude / ChatGPT and click the copy icon.
2. In Claude or ChatGPT, open the connector settings, add a custom connector, and paste the address. Menu names are controlled by those apps and may vary by plan.
3. A browser window opens. Sign in to Nautis if you are not already.
4. On the Connect App screen, choose your Workspace. Only workspaces whose plan includes this are listed.
5. Check what the app will be able to do. Reading data from the modules in your plan is always included. Create and update records is an optional checkbox, and it starts unticked. Tick it only if you want the app to make changes.
6. Click Allow access, or Cancel to back out. You return to the app, and it appears under Connected AI Apps on the Developers tab.

Claude or ChatGPT do not get your Nautis password. With the connector, you sign in on Nautis's own page in your browser, and the app receives its own access rather than your password.

If you connected without write access and want it later, disconnect the app, connect it again, and tick Create and update records.

Create an API key

1. On the Developers tab, click Create API Key.
2. Fill in Name (something that tells you what it is for), Allow write access (lets the key create and update records; this cannot be changed later, so create a new key instead), and Expiration optional (Pick a date if the key should stop working on a set day).
3. Click Create API Key.
4. Click Copy to Clipboard, then Done. Copy the key now; you will not be able to see it again.
5. Paste the key into your tool, along with the API base URL from the Developers tab. For technical details, click View API docs.

Each key in the list shows its name, the start of the key, Read-only or Read and write, and when it was last used. The intro text on the Developers tab describes read access, which is the default. To see what a key can really do, check its Read-only or Read and write label.

If you lost an API key, you cannot see it again. Create a new key and delete the old one. For an API key that needs write access later, create a new key with Allow write access.

Use ChatGPT custom GPT Actions

1. Create an API key as above.
2. On the Developers tab, copy OpenAPI spec for ChatGPT Actions.
3. In your custom GPT's Actions settings, import that address.
4. Set authentication to API Key, then Bearer, and paste your key.

What read access covers, and what write can change

Read access covers the modules your plan includes and your workspace has active: Contacts, Leads, Task Boards, Tasks, Goals, Meetings, Fundraising Deals, Invoices, Expenses, Notes, Note Folders, Business Plans, Business Plan Templates, Data Rooms, GTM Workspaces, Financial Plans, Company Brief, Routines, AI Advisors, Sheets, Startup Health, Investor Readiness, Business Profile, Bookmarks, Short Links, Brand Kits, Decisions, and Credentials. Credentials shows names and details only, never the secret values. A connected tool can see a credential's name and details such as its type and web address, but never the secret value.

Write access adds creating and updating records in areas such as contacts, leads, notes, tasks, goals, decisions, expenses, data rooms, fundraising deals, business plans, GTM, sheets, routines, and your company profile. Deleting records is never allowed. The one exception is removing rows inside a Sheet, which always waits for approval. Tools can add or update a routine, but they cannot make one run on demand.

Connected tools only see modules your plan includes and your workspace has active. Connections also act within the connecting person's permissions. If a tool cannot find a module, check those three constraints.

Approve what a connected tool wants to change

By default, writes do not happen straight away. When a tool with write access tries to create or update something, Nautis holds it and tells the tool it is waiting for approval. An Owner or Admin opens Chief of Staff, then Approvals, and decides. Once approved, it runs as the person behind the connection.

To let writes run without approval: open Chief of Staff, Settings, then Agent Autonomy; find AI Copilot and connected-app writes and choose Run without asking. You can also set individual actions under Per-action overrides. This setting also covers the AI Copilot in chat. It does not cover deleting or sending emails and social posts, which have their own settings.

Two kinds of write ignore this setting. Always wait for approval: removing rows from a Sheet, and marking a business plan as approved. Never wait for approval: adding or updating a Credentials Vault entry (a waiting approval would have to store the secret, so these run straight away). They still need write access and the right role permissions.

Writes from connected apps appear in the AI Governance activity log. Full connector steps live in Connect Claude, ChatGPT and other AI tools. For ask-first habits on outbound email specifically, see AI that asks before acting on email.

Revoke access

To disconnect an AI app: on the Developers tab, under Connected AI Apps, click the trash icon next to the app, then confirm in the Disconnect App dialog by clicking Disconnect. The app loses access immediately. To reconnect it, go through the approval steps again.

To delete an API key: on the Developers tab, under API Keys, click the trash icon next to the key. The key is deleted right away, with no confirmation step. Anything using it stops working.

Owners and Admins see every connection in the organization. Everyone else can only manage their own, and members without the Developers tab need to ask an Owner or Admin to disconnect one.

Limits and plan edges

Limits: 120 requests a minute per key or connection, 10 new API keys an hour per person, and 25 writes waiting for approval per key or connection. Requests waiting for approval expire on their own if nobody decides. A connection that goes unused for 30 days expires; connect again to restore it. If your plan loses developer access, keys and connections stop working but are not deleted; they work again if access returns. If your workspace is paused for billing, keys and connections stop until you choose a plan.

How this differs from Integrations

Integrations go the other way and let Nautis agents act inside tools like Slack. Connecting Claude or ChatGPT lets those outside tools work with your workspace under the connecting person's permissions (connector) or as the organization owner (API key). Do not treat a connected chat as a way around the separate autonomy settings for deleting or for sending emails and social posts.

An illustrative setup path (not a customer story)

The walkthrough below is an illustrative example only. It is not a real company log, measured result, or customer quote. Every capability named is one the help page documents.

A founder opens Developers, copies the MCP connector address, adds a custom connector in Claude, signs in on Nautis, picks the workspace, and leaves Create and update records unticked. They ask Claude about Fundraising Deals and Invoices that appear in the live modules. Answers match what they see in Nautis. Later they disconnect, connect again with Create and update records ticked, and ask Claude to create notes on two leads. Those creates wait in Approvals. An Admin approves one and rejects one. AI Copilot and connected-app writes stay on the default that asks for approval rather than Run without asking. They check AI Governance for the approved write, then delete an old unused API key with the trash icon so nothing still holds that token.

Start with read access, then decide on writes

Connect Nautis to Claude ChatGPT with read access first. Reading data from modules in your plan is always included on the connector. Only tick Create and update records, or create an API key with Allow write access, when you are ready to clear Approvals. Keep AI Copilot and connected-app writes off Run without asking until that queue is a habit. Revoke apps and keys you no longer need. If developer access later leaves the plan, expect keys and connections to stop until access returns; clean up what you do not need when the Developers tab is available again.