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.

Agentic Task
CapSlack BotOperationsEngineeringNotifications & AlertsDaily Digests
PromptCreate

Every 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.

Additional information

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.

Frequently asked questions

How is my Cap balance turned into dollars?
Cap measures credits in very small units called micro-credits. The workflow converts them for you using Cap's published rate (100,000 micro-credits equals one dollar) so the message you see is always in dollars.
What counts as a recording spike?
By default, a spike is any day where the total recording minutes from your Cap app are more than 1.5 times the average of the previous seven days. You can tighten or loosen that threshold in the prompt.
Will it spam my channel when nothing is wrong?
No. On a normal day the message is one or two short lines. The workflow only gets loud when a spike or low-runway flag fires, so the daily check stays easy to skip.
Can I track more than one Cap app?
Each Cap Secret Key is scoped to one app. To monitor more than one, run a copy of this workflow per app, each with its own Cap connection and (optionally) its own Slack channel.
Does Cap notify me directly when I run low?
Not today. Cap exposes your balance and recording history, but it does not send native low-credit alerts. This workflow is how you build that alerting yourself.

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.