Availability — read this first

Important: The Claude/ChatGPT AI connector is NOT AVAILABLE YET. All setup steps below apply only once the connector is deliberately turned on. A Beta label or an existing help page does not mean that it is ready to connect today.

The connector is separate from the available Developer API. Do not create a personal API key to connect Claude or ChatGPT. Do not change advanced settings or use an invented endpoint to bypass unavailable consent.

When disabled, Settings hides the connector address and setup instructions. If you have no existing connected apps, the entire card is hidden. Existing connections can still be listed and disconnected. If you do not see the connector in Settings, it is not enabled for your workspace yet.

What the connector will let you do

The connector uses MCP and OAuth to let a supported Claude or ChatGPT installation act as you in one selected LeadKnight workspace. Available tools can read campaigns, contacts, calendar and results and create, publish or change supported content, subject to your current membership, role, seat and feature availability.

Boundary	What it means
One person and one workspace per connected app binding	The workspace is chosen during consent, not by putting another workspace in a chat instruction or tool argument.
Current access, not permanent delegated privileges	Removed membership or revoked permissions stop the corresponding access. A connection does not grant access to another person's private records or unshared accounts.
No LeadKnight approval cards for connector actions	Calls can execute immediately. The host app is instructed to ask you before publishing, sending, deleting or archiving, but LeadKnight does not enforce the host's conversational confirmation. Review consequential instructions before giving them.
App-only operations	Paid-ad launch/discard and billing changes remain inside LeadKnight. Direct LeadKnight-paid generation, research/vision and internal assistant tools are not exposed through the connector.
Existing product rules still apply	Accounts, recipient consent, sender permissions, media access, scheduling, quotas and supported workspace features remain authoritative. Ordinary content changes may still trigger the product's existing background maintenance; the connector is not a guarantee of zero incidental processing.

The in-app assistant keeps its existing approval flow. Connecting an external AI app does not change those in-app rules or grant the host unrestricted access to every API route.

Before setup becomes available

Have your LeadKnight sign-in and at least one set-up workspace ready. The consent screen can direct you to finish workspace setup if none exists.
Check your current role, seat and relevant connected accounts in that workspace.
Use a supported Claude account or ChatGPT workspace with custom MCP connection access. The current setup copy lists ChatGPT Business, Enterprise and Edu for the connector; Pro is read-only. Host workspace permissions can also affect whether creation is offered.
Decide exactly which workspace the host should use. Check the name during consent even if you normally work in a different workspace in the app.
Understand that external AI software receives data through the tools you authorize and can change supported content as you. Disconnect an app you no longer trust.

Copy the connector address once enabled

Open Settings and find Use LeadKnight in Claude & ChatGPT, marked Beta. The product name in this heading follows your workspace branding.
Locate Connector address and select Copy. Copied confirms clipboard success. If copying fails, select the address and copy it manually.
Paste that exact address into the host's MCP connector configuration. It is the configured HTTPS MCP server address, serving /mcp, not the web-app homepage, /oauth/consent, the Developer API /v1 address or an OpenAPI URL.
If the address is missing, stop setup: the connector is not enabled. This guide does not provide a hardcoded production connector URL because the address must come from the enabled Settings card.

Claude setup once enabled

In Claude, open Settings → Connectors.
Select Add custom connector and paste the copied Connector address.
Choose Add → Connect. Claude starts the authorization journey and opens the LeadKnight sign-in/consent page.
Complete the workspace and permission review below. Successful consent returns you to the host; an existing valid authorization can return you without showing a fresh decision form.

ChatGPT setup once enabled

In ChatGPT, open Plugins → + → Add custom MCP server.
Enter a name, paste the copied address under Connection and select OAuth.
Review the host's risk warning and, if you agree, select Create as a plugin, then connect.
Complete LeadKnight consent. If your host plan or workspace does not offer this setup, check that host's eligibility rather than trying an API key or a different authentication mode.

These host-menu names are the instructions currently shown in LeadKnight; third-party menus and eligibility can change. Do not treat unavailable host options as evidence that LeadKnight consent has succeeded.

The consent route is /oauth/consent. Open it from the connection you just started in Claude or ChatGPT. It requires the host-generated authorization_id; opening the bare route is not a way to create authorization.

If signed out, sign in on the LeadKnight page. You return to the pending authorization after signing in.
If there are no workspaces, follow Set up your workspace, finish onboarding and restart the connection from the host.
On Allow {clientName} to use {brand}?, inspect the app name and Returns to {host}. Read the warning: Only continue if you started connecting from Claude or ChatGPT yourself just now. Names and a return host are information to review, not proof that an unsolicited link is safe.
Under Workspace, choose the one workspace this app may act in. Review the description: the connection includes reading and supported creation/publication/changes, not a read-only checkbox selection on this screen.
Select Allow only if the app, return host and workspace are the ones you intended. The screen shows Returning you… and navigates back to the host when authorization completes.
Select Deny if you did not initiate the connection or do not agree. It returns to the host when a return URL is provided, or shows Cancelled. You can close this tab. No new permission should be assumed from a cancelled journey.
After success, return to Settings and inspect the connected-app row: app name, workspace, Connected {date} and Last used {when}. Start with a read request in the host and check that the results are for the intended workspace.

Re-consenting the same OAuth client replaces its local binding with the newly selected workspace. Switching workspaces in the web app later does not redirect an already-bound host connection. To change its target, deliberately reconnect and select the new workspace during consent; do not rely on a chat instruction saying to use another workspace.

Photos, videos and usage limits

Ask the connected app for an upload link when it needs media from your device. Use the link to open /connector-upload, complete the upload in the intended workspace, then return and say that you are done. Attaching a file only to the host conversation does not establish that LeadKnight received it. See Connector uploads for statuses, formats, compression and temporary storage.

The current connector defaults are 60 bearer requests per minute, with authenticated traffic also limited per live connection, and 1,000 eligible action-tool calls per workspace/person/UTC day. Reconnecting does not reset the shared daily allowance. Email has additional defaults of one validated send call per minute and 20 per UTC day per workspace/person, shared across connections, on top of normal mailbox and recipient rules. These are configurable limits, not entitlements to send without consent.

Protocol throttling can return HTTP 429 with Retry-After; tool refusals can appear in the host as an error result. Wait for the indicated interval. If an action's outcome is unknown, inspect the current campaign, contact, calendar or sending state before asking again. A new connector invocation is not a replay guarantee of an earlier mutation; do not repeatedly ask the host to resend an uncertain operation.

Disconnect a connected app

Open Settings and find the connected-app card. Existing connections remain manageable even when new connector setup is disabled.
Check the app and workspace in its row, then select Disconnect.
Read Disconnect {clientName}? and the immediate-access-loss warning. Select Cancel to keep it connected or Disconnect to revoke it.
Local connector access is revoked first. Removal of the upstream OAuth grant is also attempted. If the app still shows LeadKnight as connected, remove it in Claude or ChatGPT too; the Settings note can remain visible after a partial upstream cleanup.
If disconnect reports failure, select Try again or reload the list and inspect it before assuming the app is disconnected.

Disconnecting removes the app's ability to make further connector calls. It is not a request to delete data the host already received or to undo posts/messages/actions already executed.

If something goes wrong

Symptom	Cause or boundary	Next step
No connector card or address	The connector is not available yet or is disabled.	Do not attempt setup until the address is offered in Settings.
Invalid sign-in link	Missing/invalid `authorization_id` or a hand-built consent URL.	Start a fresh connection in Claude or ChatGPT; do not edit the authorization ID.
Expired sign-in link	The authorization request is no longer usable.	Restart from the host rather than reusing the old tab.
Unsupported app message	The requesting client is not supported.	Return to LeadKnight; use only supported host setup once enabled.
Not a workspace member	Selected/requested workspace is not available to your identity.	Choose a workspace you belong to and check current membership.
Already connecting	A consent decision is already in progress.	Refresh the page as instructed; inspect the host and Settings before starting duplicates.
Sign-in service unavailable	The authorization service could not be reached.	Select Try again; do not approve a different unsolicited link.
Wrong workspace in results	The connection is bound to the workspace chosen at consent.	Reconnect deliberately and choose the correct workspace.
Missing tool or refused action	Workspace feature, role/seat, host plan or app-only operation.	Check the limitation; perform app-only work in LeadKnight.
Copy error	Clipboard access was denied or failed.	Select Connector address and copy manually.
Unknown result after a change	The action may already have completed.	Inspect actual state before another instruction; avoid duplicate sends or publication.