Best AI Assistant for CompanyCam

The photo already got taken. Everything after it didn't.

CompanyCam solved the hard part of jobsite documentation. Crews actually take the photos, because taking them is one tap and the location tags itself. What CompanyCam does not do is anything downstream of the photo.

The damage photo gets taken and the supplement never gets written. The pre-pour shot goes in and nobody tells the PM the deck is ready. The final walkthrough gets fully documented and the client never sees a single frame of it, because sending the album is a separate job that happens on a laptop on Sunday.

That gap is not a discipline problem. It is a wiring problem. The photo is the most reliable signal any contractor generates, and in most companies it terminates in an album nobody opens.

CompanyCam AI should mean the photo starts something. Not a summary of what was photographed, but the invoice line, the client update, the checklist item marked done, the tag that routes it to the right person.

Why CompanyCam is the best trigger in a contractor's stack

Most construction software records what already happened, after someone sits down and enters it. Photos are different. They are taken at the moment the thing occurs, by the person standing in front of it, with the project and location already attached.

That makes CompanyCam the highest-fidelity event source most contractors have, and Carly treats it as one. CompanyCam manages webhooks through its own API with a shared secret, so Carly can register its own subscriptions and verify that every event genuinely came from CompanyCam before acting.

So a photo landing in a project is a start signal, not an archive entry. That is what separates this from an assistant you have to remember to ask.

How Carly connects to CompanyCam

CompanyCam is not one of Carly's native connectors. You connect it with your own credentials, and CompanyCam makes that unusually painless: you generate an access token inside the CompanyCam app itself. There is no developer portal, no application form, and no approval queue.

On carlyassistant.com/integrations, open Connect an API and paste CompanyCam's documentation link. Carly inspects the API and determines the authentication method, then asks only for what that method needs. For a personal integration that is the access token you just generated. If you are building across several CompanyCam companies rather than your own, the same flow resolves to OAuth instead, and Carly shows you the callback URL to register.

Your credential is encrypted at rest, injected only at the moment an authorized request runs, and redacted from saved results and activity logs. Write access is a setting on the connection, and you can narrow it to specific paths rather than granting the whole API.

One version note that matters: build on CompanyCam's current Core API at api.companycam.com/v2. The legacy API is a dead end.

What Carly can actually touch in CompanyCam

Considerably more than the photos. Projects can be created, updated, archived, and restored, with users assigned, collaborators added, invitations sent, and labels applied. Photos can be listed, retrieved, and updated, including descriptions, tags, and comments. Videos can be listed and retrieved. Documents can be listed per project and uploaded.

Checklists can be created from a template, retrieved, and listed per project. Tags and groups support full create, update, and delete. Comments can be read and posted on both projects and photos. The project notepad is writable. Webhooks are created and managed through the API itself.

So Carly does not just report on your job site. It tags the photo, comments on it, writes the notepad entry, spins up a checklist from your template, uploads the signed document, and invites the client to collaborate. The work finishes inside CompanyCam rather than in a message telling you to go do it.

And because Carly sits outside CompanyCam, the same photo can also create the invoice line in your accounting tool, drop a row in the job-costing sheet, and text the client. Carly connects natively to roughly 260 apps, plus anything else with a public API through your own key.