CompanyCam AI: Connect CompanyCam to an AI Assistant
Yes, and CompanyCam is the easiest app on your job site to connect. You generate the API token yourself, inside the CompanyCam app. No developer portal, no partner application, no approval queue, no sales call. Paste it into Carly and you’re connected in about two minutes.
Which matters more than it sounds, because your crew is already taking the photos. Everything that should happen next is what’s missing.
What changes on your job sites
Photos become client updates automatically. Your crew documents the job. The homeowner gets a short, clear update with the best photos attached, the same day. Almost every “I had no idea what was happening” complaint dies right here.
You find documentation gaps while you can still fix them. Crew was scheduled, no photos went up. You hear about it this evening, not eight months later when a dispute turns on whether the work was documented.
Your invoices become defensible. Completed work gets documented and the photos attach to the invoice, so the line item stands up without anyone digging through an app.
Damage and rework route themselves. A photo gets tagged for damage and the project manager and the sub know immediately, rather than at end of day.
Checklists trigger what comes next. A checklist finishes and the inspection request, the client notice, and the schedule update all happen.
Nothing gets filed twice. The photo is in CompanyCam, the client update goes by email, the evidence attaches to the invoice, and the project record updates. One event, all of it handled.
Why CompanyCam is the best trigger in your stack
CompanyCam has an unusual property. It’s the only system that knows what actually happened on site, and it’s filled in by the people least likely to also update your project management software, your client, or your invoice.
That makes it a fantastic starting signal and a poor ending point. The photo is proof that work happened. Everything that should follow lives somewhere else.
There’s no first-party CompanyCam MCP server, and it wouldn’t close this anyway.
MCP has no trigger mechanism and no scheduler. Its own Triggers and Events working group opens by conceding that clients learn about server-side changes by polling, and that work is still listed as on the horizon rather than shipped.
A chat assistant can find you photos from the Henderson job when you ask. It can’t notice that the Henderson job got photographed this morning and the homeowner still hasn’t heard a word.
Everything Carly can reach in CompanyCam
Far more than “the photos.” The Core API covers:
| Projects | create, update, archive, restore, assign users, collaborators, invitations, labels |
| Photos | list, retrieve, update descriptions, tags, comments |
| Videos | list and retrieve |
| Documents | list per project, upload |
| Checklists | create from a template, retrieve, list per project |
| Tags & Groups | full create, update, delete |
| Comments | read and post, on both projects and photos |
| Project notepad | write to it |
| Webhooks | create and manage through the API itself |
So Carly doesn’t just read your job site. It can tag the photo, comment on it, write to the project notepad, spin up a checklist from your template, upload the signed document, and invite the client to collaborate. It finishes the work inside CompanyCam instead of just reporting on it.
Webhooks are managed through the API with a shared secret, so Carly verifies every event genuinely came from CompanyCam before acting on it.
Connecting takes about two minutes
- Generate an access token in the CompanyCam app, on its access tokens page.
- Go to carlyassistant.com/integrations and open Connect an API.
- Paste CompanyCam’s documentation link. Carly determines the authentication method and asks only for what it needs, which here is the token you just generated.
That’s genuinely it. No portal, no approval, no waiting. The Carly CompanyCam integration page has the full capability list and the workflows worth wiring first.
Your token is encrypted, injected only on an authorized request, and redacted from saved results and activity logs. Write access is something you approve rather than something that’s on by default, and you choose which agents can use the connection.
Building something for multiple CompanyCam companies rather than your own? Use Custom OAuth on the same page instead, and Carly fills in the OAuth settings from CompanyCam’s docs.
One version note worth having: build on CompanyCam’s current Core API, not its legacy API. Anything written against the old endpoints is a dead end.
Put your jobsite photos to work
When photos are uploaded to a project, send the homeowner a short progress update with the three best photos attached, and log that the update was sent.
Every evening, tell me which active jobs had crew scheduled today but no photos uploaded.
When a photo is tagged for damage or rework, send it to the project manager and the sub on that job with the project name and location.
Carly runs these on demand, on a schedule, or the moment a photo lands. AI agents start at $35/month, and workflow steps that don’t use AI run free, and a photo workflow is mostly fetching, filtering, and attaching, none of which needs a model.
Want a hand setting it up? Book a call.
Frequently Asked Questions
Does CompanyCam have AI?
CompanyCam doesn’t ship a general AI assistant. Because its API is fully self-serve, it’s the easiest construction app to connect to an AI tool yourself, and the most valuable use is as a trigger: the photo is the signal that work happened.
How do I get a CompanyCam API key?
Generate an access token yourself inside the CompanyCam app on its access tokens page. There’s no developer portal registration, partner application, or approval step, which makes it the most self-serve API in construction software.
Can I connect CompanyCam to an AI assistant?
Yes, and it takes about two minutes. Generate the token in the app, paste it into Carly under Custom API Keys, and save. Nothing needs to be built on either side first.
What can AI do with my jobsite photos?
Turn them into client progress updates, attach them to invoices as evidence of completed work, route photos tagged for damage or rework to the right people immediately, and flag jobs where crew was on site but nothing got documented.
Can AI write back to CompanyCam, or only read?
It can write. The API supports updating photo descriptions, adding tags and comments, uploading documents, creating checklists from templates, assigning users to projects, and updating the project notepad. In Carly, write access is something you approve rather than something that’s on by default.
Do I need OAuth, or is a token enough?
A token is enough for your own company account. OAuth exists for partners distributing an integration to other CompanyCam companies, and it’s unnecessary overhead if you’re wiring up your own business.
More: Construction AI · JobTread API · Claude + CompanyCam
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."
