Content & Documents · Integration
CompanyCam
Add CompanyCam to your product for your customers, and give your AI agents governed access to it.
CompanyCam organises everything under projects, and each photo carries the coordinates and capture time recorded on the phone rather than the moment it reached the server, so ordering by upload time gives the wrong sequence for field work. The v2 API takes a bearer token, but a personal access token is bound to one user while an OAuth app token is scoped to the whole company, and the two see different project sets. Tags are company-wide strings applied to both projects and photos, which makes tag plus date range the practical way to page a large backlog. Photos, documents and comments are separate resources hung off a project, so assembling a full job record takes several calls. Webhooks on photo and project creation are more dependable than polling a busy company account. fastn keeps each customer's token, handles the OAuth refresh and tracks connector changes as the API evolves.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own CompanyCam account so job photos appear against your records without manual uploads.
Pull photos for a project by tag and date range to assemble a completion report.
Write comments back onto photos so field notes from your product are visible in CompanyCam.
Create a CompanyCam project when a job is opened in your system, keeping the two id sets mapped.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to list photos added to a named project this week, with each request audited per tenant.
Have an agent check whether a project has any photos tagged for a required inspection step.
Let an agent add a review comment to a specific photo under an approved tag.
Example prompt
Show me the photos added to the Maple Street project this week.
Set up CompanyCam in 4 steps
- 01Enable the CompanyCam connector from your fastn dashboard.
- 02Have each customer authorise their own CompanyCam account, so calls run under their credentials rather than a shared key.
- 03Decide which files, documents and versions your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the CompanyCam integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a CompanyCam integration without building it. Your customers connect their own CompanyCam account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a CompanyCam update is not your on-call problem.
- One integration serves your product and your agents. The same governed CompanyCam connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Notion
Box
DocusignOften used alongside
Tools the same teams tend to run next to CompanyCam, across other categories.
Shopify
Stripe
Jira
AsanaCompanyCam integration FAQ
How do I add a CompanyCam integration to my product?
Enable the CompanyCam connector in your fastn dashboard, then let each customer authenticate their own CompanyCam account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no CompanyCam client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own CompanyCam account?
Yes. Every connection is scoped to the individual customer, so each authorises their own CompanyCam account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this CompanyCam integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to list photos added to a named project this week, with each request audited per tenant.
Who maintains the CompanyCam integration?
fastn does. When CompanyCam changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the CompanyCam integration run under?
Each customer's own CompanyCam grant. Where CompanyCam holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in CompanyCam automatically?
Where CompanyCam supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the CompanyCam integration?
A common starting point: let a customer connect their own CompanyCam account so job photos appear against your records without manual uploads. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the CompanyCam integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding CompanyCam does not change your per-connector cost. You can start free with 3 connected accounts.
Add CompanyCam to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.