Claude + CompanyCam: What the Integration Can (and Can't) Do in 2026
No — there’s no official Claude CompanyCam connector, and CompanyCam hasn’t built one. CompanyCam isn’t in Anthropic’s connectors directory. But here’s the honest upside: of the jobsite apps, CompanyCam is one of the easiest to wire up, because it publishes a proper self-serve public API that anyone can get a key for, a community-built connector exists, and there’s a real Zapier connector too. No approval queue, no partner gate.
Here’s what’s actually available, how you’d connect it today, where the limits bite, and what to use if you want photo-documentation work that runs on its own.
The API is open and self-serve — that’s the good part
CompanyCam’s Core API lets you read, create, update, and delete most of what’s in the app — Projects, Photos, tags, users. You generate an API key yourself (an admin role on the account is needed; API access is on the Pro, Premium, and Elite plans, per CompanyCam’s help center). No 1–2 week review, no per-site activation code — the gate that slows down tools like Mindbody or Procore isn’t here.
It also supports instant event notifications: the moment a photo is tagged or a checklist is completed, CompanyCam can ping another system in real time — no waiting around. That’s a solid foundation for trigger-based workflows, once you have something to catch the alert (Claude can’t; more below).
So a technical person can get Claude reading and writing CompanyCam projects fairly quickly. It’s a build, but a light one by this category’s standards.
How you’d actually connect Claude to CompanyCam today
No first-party connector exists, so the routes are unofficial but low-friction:
- A community-built connector. There’s a CompanyCam connector that wraps the API — create, list, update, archive, restore, and delete projects, plus list/add/manage photos. You supply your own API key when you set it up.
- Zapier. Zapier’s CompanyCam integration exposes CompanyCam actions to Claude through Zapier — still your own credentials underneath, plus Zapier’s per-task metering. Handy if you don’t want to run anything yourself.
- Your own build against the Core API, connected to Claude.
Any of these adds CompanyCam as a custom connector to Claude — the standard way outside apps plug in (an MCP server). The remote kind on claude.ai requires a paid Claude plan; the local kind runs through the Claude desktop app or Claude Code.
The limits that actually matter
Even with the API being this friendly, the shape is “an assistant you operate,” not “an agent that runs”:
- No triggers, no monitoring. CompanyCam can send an instant notification the moment a photo is tagged or a checklist is completed — but Claude can’t receive one. It only runs inside a conversation you start. No “when a job’s photos are tagged ‘complete,’ email the client the gallery.” You have to be in the chat, prompting.
- Conversation-only. Claude lists a project’s photos or adds a tag when you ask; it doesn’t sit on your account watching the field and following up. Close the chat and nothing continues.
- Scheduled, not event-driven. The closest thing to autopilot is Claude’s scheduled tasks, which fire on a fixed clock rather than when a new photo lands — Claude has no inbox to receive one. That’s not an always-on agent watching jobsite uploads.
So Claude is good for “summarize what got photographed on the Maple Street job this week” and not built for “send the client a progress gallery every time a crew wraps a phase.”
If you want CompanyCam work that runs on its own: Carly
The moment you want something to happen around CompanyCam without you in the chat — email the homeowner a progress gallery when a job is tagged complete, alert the PM when no photos hit a project in 48 hours, roll up the week’s jobsite documentation for the owner — you’ve crossed past what Claude is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers. CompanyCam connects to Carly via your own API key — paste it on carlyassistant.com/integrations — and Carly works the API and event notifications for you:
- When photos are tagged complete, Carly assembles the gallery, drafts the client update, and sends it.
- When a project goes quiet, Carly flags the PM that no photos have come in and drafts the nudge to the crew.
- Every Friday, the week’s photo activity across active jobs rolls up into one owner digest.
- Actually sends and updates — drafts and sends email across Gmail and Outlook with attachments, updates tasks, and syncs your CRM.
- No-code setup. Describe the workflow in plain English; Carly interviews you and builds it with you.
- Connects to anything — 200+ native integrations (see integrations), plus any tool with an API via your own key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude’s CompanyCam options vs Carly
| Claude (community or Zapier setup) | Carly | |
|---|---|---|
| List, tag, manage projects & photos | Yes, via your API key | Yes, via your API key |
| Reacts when a photo is tagged or checklist done | No | Yes, on events |
| Client progress gallery, unprompted | No | Yes, on events or schedule |
| Fires on triggers, not just a timer | No | Yes (cloud) |
| Sends the emails itself, not just drafts | No — drafts only (Gmail + Outlook) | Yes |
| What it takes to set up | Build/Zapier + paste your API key | Paste your API key |
| Pricing | Pro $20 / Max $100–$200 (+ Zapier tasks) | AI agents from $35/mo |
Claude with a community or Zapier setup is a CompanyCam console inside a chat. Carly is a teammate that acts on jobsite photos as they land.
Frequently Asked Questions
Does Claude work with CompanyCam?
Not officially — there’s no Claude CompanyCam connector and CompanyCam hasn’t built one. But CompanyCam is one of the easier jobsite apps to connect: it has a self-serve public API (docs.companycam.com), a community-built connector, and a Zapier connector, so you can wire it to the Claude desktop app or Claude Code as a custom connector. Either way, it only works inside a conversation you start.
Is the CompanyCam API hard to get?
No. It’s self-serve — you generate an API key yourself with an admin role, on the Pro, Premium, or Elite plans. There’s no approval review or per-site activation, and it can send real-time notifications for events like tagged photos and completed checklists.
Can Claude watch for new jobsite photos and act on them?
No. CompanyCam can send a notification on new or tagged photos, but Claude can’t receive one and only acts inside a conversation you start. For photo-triggered client updates and alerts that run unattended, you need a trigger-based agent like Carly.
What if I want CompanyCam to act on its own — client galleries, stale-project alerts?
That’s outside what Claude does. Carly connects to CompanyCam via your API key, fires on photo events and schedules 24/7 in the cloud, and can email clients progress galleries, flag quiet projects, update records, and send weekly digests. AI agents start at $35/month.
More: Claude + Jobber · Claude + Housecall Pro · Claude connectors · Can Claude send emails · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
