Daily Cap credit burn rate check in Slack
Each morning at 8am, get a short Slack update with your Cap balance, weekly recording burn, and how many days of runway you have left.
Cap
Slack BotOperationsEngineeringNotifications & AlertsDaily DigestsEvery morning at 8am, run a Cap credit burn rate health check and post the result to a Slack ops channel. This is an agent workflow on a cron trigger.
Step 1. Call Cap Get Usage to read the current balance (balanceMicroCredits) and the aggregate video stats.
Step 2. Call Cap List Videos for the last 7 days so you can see daily recording volume and total duration per day. Use the createdAt and duration fields to bucket videos by day.
Step 3. Compute three numbers: today's spend so far, the 7-day moving average daily burn (Cap charges 5,000 micro-credits per minute of video), and how many days of runway remain at the current 7-day average pace. Convert micro-credits to dollars using 100,000 micro-credits = $1.
Step 4. Use Slack Bot Send a Message to post to the channel #cap-ops. Include: the current balance in dollars, the 7-day average daily burn (in dollars and minutes), the projected days of runway, and a clearly marked flag if today's recording minutes are more than 1.5x the 7-day average OR if projected runway is under 14 days.
Keep the message short and skippable on normal days (one or two lines is fine). Only get loud when a flag fires. Use Slack mrkdwn formatting (*bold* for the flag line, plain text for the numbers). The exact wording and emphasis can vary day to day, which is why this is an agent workflow rather than a fixed script.
What does this prompt do?
- Every morning at 8am, checks your Cap balance and the past week of recordings.
- Calculates a 7-day average burn rate and projects how many days of runway you have left at the current pace.
- Posts a short, skippable Slack message to your ops channel with balance in dollars, weekly burn, and projected runway.
- Loudly flags days where recording volume spikes above 1.5x the weekly average, or where runway drops under 14 days.
What do I need to use this?
- A Cap account and a developer Secret Key from the Cap dashboard.
- A Slack workspace with the General Input bot installed.
- The name of the Slack channel where you want the daily update to land (for example, #cap-ops).
How can I customize it?
- Change the time of day or restrict it to weekdays only.
- Adjust the spike threshold (default 1.5x the weekly average) or the runway warning (default under 14 days).
- Swap the destination channel, send it as a direct message, or tag a specific person when a flag fires.
FAQs
How is my Cap balance turned into dollars?
What counts as a recording spike?
Will it spam my channel when nothing is wrong?
Can I track more than one Cap app?
Does Cap notify me directly when I run low?
Related templates
When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.
Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.
Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.
Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.
Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.
When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.
Stop guessing how much Cap credit you have left.
Connect Cap and Slack once, and Geni posts a short balance and runway check every morning at 8am.