Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Custom Claude connector case studies

What kinds of connectors have you built?

Examples of custom Claude connectors span three situations: replacing a limited or read-only connector, building deeper than a directory connector for a customized setup, and creating one from scratch for a bespoke internal tool. Each example below lets Claude read, create, and update inside the system its owner already uses.

Client identities are anonymized. Every connector authenticates as the account it runs under and inherits its existing permissions, so it never grants Claude more access than that account already has. Create and update actions flow freely; delete and send stay gated behind a confirmation a person controls.

What makes a good custom connector case study?

A good custom connector case study shows the exact system, the read, create, and update actions Claude now performs inside it, and the confirmation gate on anything destructive. It names a real before-and-after for one team, anonymized, so you can judge whether the same pattern would fit your own tools and permissions.

Limited connector replaced

A services firm running its whole inbox in Gmail

System
Gmail
What Claude can now do
Claude reads a thread and drafts the reply inside that same thread, applies labels, and queues a send that a person confirms.

Replies drafted in-thread, every send gated for review

Read the case study →Built deeper than the directory

A sales team on a heavily customized Pipedrive pipeline

System
Pipedrive (custom fields and stages)
What Claude can now do
Claude creates and updates deals, activities, and custom fields across the pipeline, then logs follow-ups without leaving the conversation.

Deals and custom fields updated in the conversation

Read the case study →No connector existed

A team running an in-house referral application

System
Bespoke internal referral portal (no directory listing)
What Claude can now do
Claude reads referrals, creates and updates them, and moves each one through the workflow, with status changes a person confirms.

Referrals created and updated without manual re-entry

Read the case study →

Frequently asked questions

What outcomes do you measure?
We measure the outcome the team already cares about: time saved per task, records created or updated per week, and manual data entry removed. We report the numbers a client confirms rather than rounded estimates assembled after the fact, so a case study shows a verified outcome or a clear qualitative result, never an invented statistic.
Can connectors be built for tools with no API directory listing?
Yes. Two of these examples cover tools with no directory listing, including a bespoke internal referral portal. If the system exposes an API, or we can reach its data safely, we build a custom MCP connector from scratch so Claude can read, create, and update inside it, the same way it does for listed tools.
Are these clients named?
No. Client identities are anonymized, so each case study describes the system, the situation, and what Claude can now do without naming the company. The technical pattern (which actions run freely and which stay gated) is fully described, so you can judge fit even though the team behind it stays private.
How soon can Claude write back to my tools?
It depends on your tool's API and permissions, not on a fixed schedule. Once a connector authenticates as your account, Claude can read immediately, then create and update inside the system. Delete and send stay behind a confirmation a person controls, so write access never exceeds what that account already has.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us