ChatGPT connectors for your CRM: a safe setup

Relaticle published a setup guide recommending that organizations connect each CRM workspace to ChatGPT through exactly one connection, after a developer reported on November 5 in an OpenAI Developer Community thread that a confirmation tool call was silently routed to a different connector than the one the user had approved. The developer had two enabled connections to the same MCP server — a custom connector added in developer mode and the published app from the directory — and the server rejected the follow-up call's one-time code because it was bound to the custom connector's OAuth client. Relaticle founder Manuk Minasyan said the incident is why the company advises one connection per CRM workspace, noting that ChatGPT app writes over MCP apply immediately in Relaticle while its built-in assistant Rela asks for approval before writing.

ChatGPT connectors are now called apps and ship inside plugins. Set up a ChatGPT CRM integration safely. Authorize each CRM workspace once, through one connection. Check what your workspace role lets it do. Know where to revoke it before you begin. That setup keeps the scope clear. A CRM connection runs over MCP Model Context Protocol , the standard way ChatGPT reaches an outside app. It can read sensitive records and write changes. Choose the workspace carefully, review the consent screen, and treat every connected app as an active route into your CRM. On November 5, a developer reported a surprising connector switch in an OpenAI Developer Community thread https://community.openai.com/t/security-follow-up-tool-call-silently-routed-to-a-different-connector/1413053 . This is one user's report, not an OpenAI confirmation. The user had two enabled connections to the same MCP server. One was a custom connector added in developer mode. The other was the published app from the directory. The model called a confirmation tool through the custom connector. Its widget displayed the change, and the user confirmed it. The widget then placed a one-time confirmation code in the conversation. The follow-up call used the published app instead. The user was not told that ChatGPT had switched connections. The server rejected the redemption because it bound the code to the custom connector's OAuth client. The server's check held. It treated the two clients as distinct, even though they reached the same server for the same user. That report is why we recommend one connection per CRM workspace. I would rather an assistant ask me twice than write once without my knowledge. That is why Rela waits for approval inside Relaticle. Over MCP, that question belongs to the client you choose, so choose one you trust. Manuk Minasyan, founder of Relaticle ChatGPT apps can search and read companies, people, opportunities, tasks, and notes in Relaticle. They can also create, update, and delete those records when the connection permits it. Relaticle applies an MCP write as soon as the call arrives. Any confirmation happens in ChatGPT, before the call. In Relaticle, email is the one exception: a send waits a few minutes, and you can cancel it. Rela, the built-in AI assistant, behaves differently inside Relaticle. Rela asks before it writes inside the app. A ChatGPT connection does not pass through that approval. This difference should shape who connects. A connection's abilities follow its user's workspace role, so a Viewer's connection can only read records. A Member, Admin, or Owner can connect one that changes them, so assign someone to review its activity. The current ChatGPT setup calls connectors apps, and apps ship inside plugins. OpenAI documents the flow in its guide to connecting a plugin in ChatGPT https://developers.openai.com/plugins/deploy/connect-chatgpt . 1. Connect each CRM workspace once. For the same CRM, use either its published plugin or one custom MCP server. Do not connect both. 2. Sign in to the CRM, then choose the single workspace this connection should reach. 3. Read the consent screen and check that the listed abilities match the work you plan. 4. Decide whether the connection should write at all. In Relaticle, abilities follow your workspace role. A Viewer seat can read records but not change them. 5. Treat write access as live access, because creates, updates, and deletes over MCP apply immediately. 6. If you connect email, check who can read, draft, and send before you authorize the app. 7. Find the revoke control before your first session. Custom MCP servers follow the same basic route. In ChatGPT Plugins, select the plus button, choose Add custom MCP server , configure authentication, review the warning, and create the plugin. Account and workspace policies can restrict that process. Relaticle's ChatGPT plugin is available in the ChatGPT plugin directory https://chatgpt.com/plugins/plugin asdk app 6a92c3af04a0819180ed6652ebe09961 . Install it, sign in to Relaticle, and select one workspace during consent. That workspace selection remains attached to the connection. To use another workspace, revoke the connection and create a new one. This prevents one connection from moving silently between workspaces. The consent screen lists the abilities available through your role in that workspace. The client cannot request more than that role allows. With email enabled, every role can read and draft email. Owners, Admins, and Members can also send it. The app can work with your CRM records, including companies, people, opportunities, tasks, and notes. It can search records, read record detail, and make permitted changes. For exact behavior and integration details, see the Relaticle MCP reference https://relaticle.com/developers/mcp . Email receives an extra guardrail. When the app sends an email, Relaticle holds it for a few minutes. You can cancel it from Relaticle notifications or the Outbox. Relaticle lists connected assistants under Settings → Access Tokens → AI Connectors . Each entry identifies the assistant and workspace, and provides a Revoke control. Revocation invalidates access and refresh tokens immediately. A queued email tied to a revoked connection does not send. That makes revocation useful when a role changes, a device changes hands, or a connection no longer belongs in the workspace. An Owner or Admin can also inspect changes after the fact. The activity log shows who changed each record and which fields changed. Records created over MCP carry the “MCP Agent” creation source. If you want the broader connection model, read our guide to connecting Claude to your CRM with MCP https://relaticle.com/blog/how-to-connect-claude-to-your-crm-with-mcp . The same operational principle applies: scope the connection, understand writes, and retain a clear path to revoke it. ChatGPT connectors are access grants, and they need the same care as any other. Connect one workspace, review its role-based abilities, and keep revocation and activity review close at hand. mcp https://relaticle.com/blog/tag/mcp