CompanyCam logo

CompanyCam

Photos

Job-site photo documentation: let Ruby reference photos by project.

32 tools
API KEY
Reads by default, writes opt-in

Ask Ruby

“Pull the latest photos for the Oak Ave project.”
“Which jobs have no before photos on file?”
“Show me roof photos tagged this week.”
“Do we have signed-work-authorization photos for job 4471?”
What Ruby can do

27 read tools

Ruby reads from CompanyCam and grounds her answers in your data. Every connection starts read-only: she surfaces, summarizes, and drafts, and your team takes the action.

Listchecklists

List All Checklists (GET /checklists)

Getcurrentcompany

Retrieve Company (GET /company)

Getcurrentuser

Retrieve Current User (GET /users/current)

Listusers

List All Users (GET /users)

Getuser

Retrieve User (GET /users/{id})

Listprojects

List Projects (GET /projects)

Getproject

Retrieve Project (GET /projects/{id})

Listprojectphotos

List Photos (GET /projects/{project_id}/photos)

Listprojectassignedusers

List assigned users (GET /projects/{project_id}/assigned_users)

Listprojectcollaborators

List project collaborators (GET /projects/{project_id}/collaborators)

Listprojectinvitations

List project invitations (GET /projects/{project_id}/invitations)

Listprojectlabels

List Project Labels (GET /projects/{project_id}/labels)

When you turn writes on

5 write tools, off by default

Let Ruby document in CompanyCam as well as read it, so what it finds lands on the job instead of in a message someone has to act on.

An admin switches a connection to read-write in Settings > Integrations. From then on every write waits for a human’s approval before it leaves, by default, and every one lands in your audit log with what changed.

Createproject

Changes data in the connected account. Create a project Create a new CompanyCam project (a job site). Search first with listProjects so you do not create a duplicate of an existing job. (POST /projects)

Updateproject

Changes data in the connected account. Update a project Change a project's name, address, or coordinates. Only the fields you send are changed. Get the id from listProjects. (PUT /projects/{id})

Createprojectphoto

Changes data in the connected account. Add a photo to a project Attach a photo to a project from a publicly reachable image URL. CompanyCam fetches the URL itself, so it must be reachable without authentication. (POST /projects/{project_id}/photos)

Createprojectcomment

Changes data in the connected account. Add a comment to a project Post a comment on a project's timeline. Additive: nothing existing is changed. (POST /projects/{project_id}/comments)

Createphotocomment

Changes data in the connected account. Add a comment to a photo Post a comment on a specific photo. Get the photo id from listPhotos or listProjectPhotos. Additive: nothing existing is changed. (POST /photos/{photo_id}/comments)

Why connect it to Ruby

Built for restoration, not bolted on.

Grounded answers

Ruby reads CompanyCam live and cites what she found, so answers reflect your actual data, not a stale export.

Reads by default

Every connection starts read-only. Ruby surfaces and drafts while your team takes the action; writes are opt-in per connection, human-approved by default, and always logged.

Managed, secure auth

Connect with one click. Tokens are encrypted and scoped per company; revoke access any time.

Knows restoration

Ruby understands jobs, claims, drying logs, and AR, so CompanyCam data lands in the right operational context.

Use it from anywhere

Connect once, then just ask.

Connect CompanyCam once in Ruby. Ask in the Ruby app, or bring the same secure connection into the assistant your team already uses.

Ruby

Ask in the Ruby app and get an answer grounded in CompanyCam and the rest of your connected stack.

Claude

Bring the same secure CompanyCam connection into Claude so it can answer with your live data.

ChatGPT

Use CompanyCam from ChatGPT with the same per-company, permissioned access Ruby uses.

Frequently asked questions

Do I need developer credentials to connect CompanyCam?

You paste an API key from your account in Settings > Integrations. There is nothing to build; Ruby stores it encrypted and scoped to your company.


Can Ruby change anything in CompanyCam?

Not unless you turn it on. Every CompanyCam connection starts read-only. An admin can switch a connection to read-write in Settings > Integrations; from then on each write Ruby makes waits for a human's approval before it leaves (by default; the same admin can switch that off) and is recorded in your audit log either way.


Is my CompanyCam data secure?

Credentials are encrypted at rest and access is scoped per company. You can revoke the connection at any time from Settings > Integrations, which immediately cuts Ruby off.


Can I use CompanyCam alongside my other tools?

Yes. Ruby reasons across every tool you connect at once, so she can tie CompanyCam to your CRM, accounting, email, and documentation in a single answer.