Daily CompanyCam jobsite photo recap in Slack

Every weekday at 5pm, we scan today's active jobsites for photos and comments, then post a per-site narrative to Slack for the office team.

Agentic Task
CompanyCamSlackOperationsDaily DigestsAI Reports
PromptCreate

Every weekday at 5pm local time, roll up today's CompanyCam jobsite activity into a single narrative recap and post it to a Slack channel so office staff can see what happened on site without opening the app.

Start by calling CompanyCam List Projects with a modified_since filter set to the start of today in the org's local timezone (ISO8601). That returns every project that had any activity today, most recent first. Paginate until the response comes back short or empty.

For each project, call CompanyCam List Project Photos and keep only photos captured today (using the photo's captured_at). Skip any project that ends up with zero new photos — do not include it in the digest at all.

For photos that look meaningful (a caption present, a comment count above zero, or a notable tag such as before, after, damage, punchlist, or completion), call CompanyCam List Photo Comments to pull the crew comments. Use those captions and comments as context when drafting the narrative — a note like "roof deck ready for shingles" should shape what the recap says.

For each qualifying project, write a short narrative recap (roughly 2-4 sentences): what got done today, any notable tags, and which crew member captured the most photos (by counting photos per creator_id / creator_name). Keep the tone factual and specific — refer to real captions or comments where they add color.

Combine everything into a single Slack message. Each project gets its own section with the project name as a bold header, the narrative, and a direct link back to the project in CompanyCam (https://app.companycam.com/projects/<project_id>). Cap the whole digest at a reasonable length — target under about 3000 characters. If there are too many projects to fit, keep the ones with the most photos or the most notable tags and mention the count of any that were trimmed.

Post the finished digest as one message using Slack Send a Message to the configured channel. Do not post anything if every project was skipped for zero new photos — send a single line saying "No jobsite activity logged today" instead, so office staff know the workflow ran and it was a quiet day, not a broken automation.

Additional information

What does this prompt do?
  • Finds every CompanyCam project that had activity today
  • Reads the day's photos and any captions or crew comments left on them
  • Writes a short narrative per site covering what got done, notable tags like before/after or damage, and which crew member captured the most photos
  • Posts the whole roll-up as one Slack message with a direct link back to each project
What do I need to use this?
  • A CompanyCam admin login on a Pro, Premium, or Elite plan so we can read projects, photos, and comments
  • A Slack workspace and a channel where the daily recap should land
How can I customize it?
  • Change when it runs (5pm every weekday is the default, but any schedule works)
  • Point it at a different Slack channel or a direct message
  • Filter to specific project labels if you only want a recap for certain crews, regions, or trades

FAQs

What if a jobsite had no photos today?
It gets skipped. The recap only includes sites that actually had new photos, so the message stays short on quiet days.
Does the summary mention photo tags?
Yes. Notable tags like before/after, damage, punchlist, or completion make it into the per-site narrative so anyone reading knows what to look at first.
Can office staff jump straight to the project in CompanyCam?
Yes. Every site in the recap includes a direct link back to that project, so anyone in the channel can click through and see the photos in full.
Is it one message per site or one combined message?
One combined message. Each project gets its own section, and the digest is capped at a reasonable length so Slack stays readable.
Do crew captions and comments show up in the summary?
Yes. The agent reads captions and any comments left on the photos and uses that context in the narrative, so a note like 'roof deck ready for shingles' actually shapes what the recap says.

Related templates

Nudge Dynamics 365 deal owners about stale pipeline in Slack

Every weekday morning, an agent reviews your open Dynamics 365 pipeline and privately DMs each rep only the deals that need attention today.

Microsoft Dynamics 365
Slack
Agentic Task
Catch deployments that made your app slower or less reliable

Every hour we compare the 30 minutes before and after each release, and only speak up when a deployment genuinely degraded speed or reliability.

New Relic
Slack
Linear
Agentic Task
Log daily Mercury balances and alert when cash runs low

Every weekday morning, every account balance is logged to a spreadsheet, and you only hear about it in Slack when one drops below the limit you set.

Mercury
Google Sheets
Slack
Deterministic Code
Update Dynamics 365 deals automatically after every Gong call

After every recorded sales call, an agent updates the right deal in Dynamics 365 and posts a Slack recap of exactly what changed.

Gong
Microsoft Dynamics 365
Slack
Agentic Task
File contact sales form leads into Dynamics 365 without duplicates

Every contact sales form submission lands in Dynamics 365 as a clean lead, updating the record you already have instead of creating a second one.

Google Forms
Microsoft Dynamics 365
Slack
Deterministic Code
Turn every New Relic alert into a tracked Jira ticket

Every New Relic alert opens a Jira bug with the full context and a Slack heads up, then closes itself with the incident duration when it recovers.

New Relic
Jira
Slack
Deterministic Code

Stop chasing your crews for end-of-day updates.

Let the photos your team already takes turn into a Slack recap the office actually reads.