# Daily Cap recordings digest in Slack and Notion

> Every weekday at 9am, your team gets a Slack recap of yesterday's Cap recordings, and every video lands in a searchable Notion library.

- Workflow type: agent
- Services: Cap, Slack Bot, Notion
- Categories: Personal Productivity, Operations
- Published: 2026-06-26

## What it does

- Posts one tidy Slack message each morning listing every Cap recording uploaded in the last 24 hours.
- Adds every new recording to your Notion recordings library so the team can search the archive later.
- Shows the title, length, owner, and share link for each video so people can jump straight to what they need.
- Stays quiet on days with no new uploads, so the channel never gets a 'nothing to report' ping.

## What you'll need

- A Cap account with developer access so we can pull yesterday's recordings.
- A Slack workspace and the channel you want the daily digest posted in.
- A Notion workspace with a database to log recordings into (a 'Recordings Library' or similar).

## Prompt

Build me an agent workflow that posts a daily morning digest of new Cap screen recordings to my team's Slack channel and logs each recording into a Notion database.

Trigger: cron, Monday through Friday at 9am local time.

On each run, do the following:

1. Use Cap's List Videos operation to fetch every recording uploaded in the last 24 hours. Cap has no webhooks, so polling on the cron schedule is the right pattern.

2. If the list is empty, exit the workflow gracefully without posting anything. The channel should not see a 'nothing to report' message on quiet days.

3. If there are new recordings, send a single message to a designated Slack channel using Slack Bot's Send a Message operation. Format the message as one bullet per recording with: title, duration (formatted as mm:ss), owner name, and the Cap share link. Open with a short header like 'Yesterday's Cap recordings' and use Slack mrkdwn for the bullets.

4. For each new recording, also call Notion's Create a Page operation to add a row to my 'Recordings Library' database. The row should include: Title, Duration, Owner, Share Link, and Uploaded At (the recording's creation date). Use the database id I supply.

Inputs the workflow should accept: the Slack channel id to post in, the Notion database id, and optionally the timezone for the 9am schedule (default to my account timezone).

Make it idempotent enough that re-running it on the same day does not double-post to Slack or create duplicate Notion rows for recordings already logged.

## How to customize

- Change when it runs. Move it earlier, later, or include weekends if your team records over the weekend.
- Swap the Slack channel, or send it to a private team channel instead of a public one.
- Adjust what gets logged in Notion. Add columns for project, tags, or internal notes, or drop the ones you do not use.
- Filter the digest to specific owners or recording name patterns if you only care about a subset.

## FAQ

### Does Cap notify us the moment a video is uploaded?

Not yet. Cap does not offer real-time alerts, so we check on a schedule each morning. That fits a once-a-day team digest perfectly.

### Will the workflow spam Slack on quiet days?

No. If nobody recorded anything in the last 24 hours, we skip the post entirely so the channel only sees real activity.

### How do I change which Slack channel it posts to?

Update the channel in the workflow settings and the next morning's digest will post there.

### Do I need a paid Notion plan?

No. This works on any Notion plan. We just need a database shared with the General Input connection.

### Can I log recordings somewhere other than Notion?

Yes. You can swap Notion for Google Sheets, Airtable, or another tool by editing the workflow.

Use this prompt in General Input: https://www.generalinput.com/prompts/daily-cap-recordings-digest-in-slack-and-notion