Claude as a CRM assistant: what to connect and what to check
Short answer: Claude can help you read client history, prepare a call and draft a next step. For ongoing client work, give it a maintained record it can retrieve. That can be a spreadsheet, a CRM or software you build; the right choice depends on the records, permissions and maintenance you need. A confident chat answer is not proof that a record was saved.
Build a CRM, use a sheet or connect one?
| Approach | Useful when | Work you still own |
|---|---|---|
| Attach a small client list or notes | You need a one-off recap or draft | Supply current information; check the answer; save any agreed result |
| Connect a spreadsheet | Your existing sheet has a clear owner and structure | Sharing, field validation, duplicate handling and the exact connector's write permissions |
| Build a custom CRM with Claude's help | You have requirements and someone able to maintain software | Authentication, backups, data model, testing, access controls and ongoing operation |
| Connect an existing CRM | You need linked clients, work and a durable record across sessions | Choose the plan and access; verify what the assistant reads and changes |
A spreadsheet can have permissions and history; it is not inherently an unsafe choice. A custom app can work, but generating its screens is not the same as operating a reliable client system. Flori is one connected CRM option, not the only CRM with MCP.
Connect Claude to a small test project
Use the fictional Juniper brief. Create its project and tasks first. You can copy the example into any CRM; the following connection steps are for Flori.
- In Flori, open Settings, then Connections and choose Claude. The remote address is https://useflori.com/mcp.
- In Claude, open Customize, then Connectors and add a custom connector. Give it a name and the Flori address. Review the detected authentication and use browser sign-in; do not paste a personal token into the URL.
- During Flori sign-in, select the test project and read-only access. Enable Flori in the conversation's connector menu.
- Ask Claude to read that named project and its tasks. Check that the returned project and scope match the records you created.
Anthropic's current connector guide, checked October 29, 2026, lists Free, Pro, Max, Team and Enterprise support, with one custom connector on Free. Managed organizations require the appropriate owner or administrator setup before members connect. Menu labels and account policy can differ; use the official guide and Flori's Claude setup if your screen differs. No local server installation is required for this remote connection.
First prompt: a recap that makes no changes
"Read the Juniper project brief and tasks. List the five-page scope, approver, next deliverable and missing inputs. Name the record supporting each claim. Keep unknowns explicit. Do not change, send or publish anything."
Compare the answer with the saved brief. Rowan is the approver; Casey supplies content and access. If the access task is Waiting, the answer must not say the team can start the CMS build. If the sixth-page request was deferred, it must not appear as an accepted deliverable. These are expected checks on a fictional exercise, not a transcript of a completed live Claude trial.
Second prompt: a proposed task you inspect
If you want to test changes, reconnect with update access limited to the same project. Ask: "Propose a task to request the missing logo. Use the proposed-task flow, leave the due date unset, and do not change the accepted brief or create an accepted task."
Inspect the proposed task in Flori before accepting or rejecting it. Confirm the project, wording and owner, then read back the result. A proposed task remains different from a task the user explicitly authorized an assistant to create directly. Update access can permit immediate saves; not every write waits for human approval. Keep the assistant's tool-approval settings appropriate to the access you grant.
For a stronger access check, use the kit's second test project and request it by its known ID. A project-limited connection should not return its contents. With read-only access, a requested write should fail and leave the record unchanged. An empty search alone does not prove isolation.
Recover from the common failures
| Symptom | Check next |
|---|---|
| No Flori tools appear | Connector enabled in this conversation; organization's connector access |
| Project is missing | Selected workspace and project grant; exact project name or ID |
| Reading works but saving fails | Read-only versus update grant; permitted tool and plan limits |
| Assistant says it saved, but the task is unchanged | Actual tool result and saved record; do not repeat a write blindly |
| A new chat misses yesterday's decision | Read the specific saved note; the previous chat may never have saved it |
The connector does not send email, collect payments or publish a website. Ask for drafts and review them; use a separate authorized channel for external actions. Your Claude subscription and limits remain separate from Flori's plans.
FAQ
Can Claude be my CRM by itself? It can help with client work, but you still need a maintained record, appropriate access and a way to verify changes. A connected spreadsheet, existing CRM or maintained custom application can provide that record.
Will every change wait for me to approve it? No. Flori has proposal and submitted-work review paths, while some authorized direct updates save immediately. Start read-only and deliberately choose the review path when you want a proposal first.
Can I use ChatGPT instead? Flori also offers a custom connection for eligible ChatGPT accounts. Follow the current ChatGPT setup guide from Flori's connection page; account and workspace policies determine availability.
Start your workspace