Skip to main content

Sign in with your NeetoEngage account

  1. Open Customize > Connectors, click Add, then click Add custom connector.
    Menu under the Add button in Claude's Connectors settings, with the single item Add custom connector

    Add custom connector is the only item under the Add button.

  2. Enter the name NeetoEngage and paste the server URL:
  3. Click Continue and sign in to NeetoEngage. See What the sign-in looks like.
NeetoEngage then works in claude.ai, the Claude desktop app, Claude mobile, and Cowork.If you do not see Add custom connector, your Team plan admin must allow custom connectors under Organization settings > Connectors.To disconnect, open Customize > Connectors and remove NeetoEngage.

What the sign-in looks like

1

Connect your workspace

Enter your workspace subdomain, or paste your workspace URL. For acme.neetoengage.com, enter acme. If you do not know it, select Find your workspace subdomain on that screen. It opens the Workspace subdomain page.
2

Sign in

Sign in to that workspace, if you are not signed in already.
3

Choose what the assistant can do

Read and Stay connected are always on. Tick Create and update and Delete only if the assistant needs them.One connection can reach more than one workspace at the same time. The workspace you entered is always connected. If your email belongs to other workspaces, tick any you also want under Additional workspaces to connect. The permissions you approve apply to all of them.
4

Authorize

Click Authorize.
To add a workspace or a permission later, sign in again and tick it.

Use an API key

An API key reaches the whole workspace, not only what you can see. Use it for automation. See Authentication.
  1. Add the server to ~/.claude.json:
  2. Restart Claude Code.
Replace YOUR_API_KEY with a key from your workspace. Learn how to generate your API key.

Confirm the connection

Ask the assistant “List the tracks in my NeetoEngage workspace.” If it answers with your tracks, the connection works. For more prompts, see Examples. If it does not work, see Troubleshooting.