Close CRM Connector

When Close CRM is enabled for your Armbrain workspace, its connector imports useful content from calls and meetings for one client, prospect, or company mind about every 15 minutes. Close currently grants every OAuth app full API access. Armbrain only makes read requests and never writes data back to Close.

One-time operator setup

Create an OAuth application in Close and set its callback URL to:

https://api.coppermind.app/v1/oauth/close/callback

Store the Close client ID and client secret in the gateway's CLOSE_CLIENT_ID and CLOSE_CLIENT_SECRET secrets. Never put either secret in chat, a connector record, or source control.

Close's OAuth reference is at .

Connect a client

1. Switch to the client, prospect, or company mind that should receive the Close data.
2. Open Armbrain HQ, choose Connectors, and select Close CRM. If it is not listed, Close has not been enabled for your workspace yet.
3. Click Connect Close CRM, sign in to the correct Close organization, and approve access.
4. Return to Connectors and confirm that the connector is active.

The conversational equivalent is:

connectors action=connect source_type=close

Open the auth_url returned by Armbrain. Do not ask a customer for a Close password, client secret, access token, or refresh token.

What gets imported

• Calls with notes, recording transcripts, voicemail transcripts, or Close-generated summaries.
• Meetings with calendar notes, user-authored notes, notetaker transcripts, or Close-generated summaries.
• Useful context including activity time, direction or meeting status, attendees, and the related Close lead ID.

Empty calls and meetings are ignored. Sync scans the previous 90 days so Armbrain can pick up transcripts that Close attaches after the activity ends and late-created records whose activity time is older than their creation time. Updated activities create a new versioned source reference; the normal memory pipeline handles the resulting update.

Armbrain never writes data back to Close. Disconnecting stops future syncs but does not delete memories already created from Close data.

Troubleshooting

• Connector stays in pending setup: restart the connection. OAuth links expire after five minutes.
• Wrong Close organization: disconnect and reconnect while signed in to the correct organization.
• Connector pauses after working: reconnect it. Close refresh tokens rotate, so an interrupted or revoked authorization can require a fresh sign-in.
• No memories appear: confirm that recent calls or meetings contain notes, transcripts, or summaries. Empty activity records are intentionally skipped.
• Large account does not finish in one poll: Armbrain narrows busy time windows until each can be read without a cross-page offset, then advances only after the discovered records are durable.

Close's official references cover OAuth authentication, calls, and meetings.