Daily Slack alert when a Clockify project goes over budget

By General Input

Every weekday morning, we check your Clockify projects against their estimates and message your team in Slack only when one is trending over budget.

Integrations

  • Clockify
  • Slack Bot

Type

Agentic Task

Categories

  • Operations
  • Finance

Every weekday at 7am, run a project budget early-warning check across my active Clockify projects and only alert my team in Slack when a project is genuinely at risk. On days when every project is healthy, stay completely silent and send nothing.

Start by pulling my active projects with Clockify's Get all projects on a workspace, requesting hydrated detail so I get each project's time estimate and budget estimate fields. Exclude archived projects, and let me optionally restrict to billable projects or a single client. When I need the full estimate detail for a specific project, follow up with Find a project by ID (hydrated). Then get the hours and cost tracked so far by running Generate a summary report grouped by project for the project's current period, falling back to month to date when a project has no defined period.

Compare tracked hours and tracked cost against each project's time estimate and budget estimate. Work out how far through the period we are, compute the burn rate, and flag any project that has already crossed the warning threshold (default 80 percent of budget or hours consumed) or is trending to blow past its estimate before the period ends based on the current run rate. For anything trending over, project the expected overage in hours and dollars.

Some projects will not have a time or budget estimate set. Do not skip those. Fall back to flagging on raw tracked hours and burn rate instead, for example a project whose logged hours are accelerating sharply week over week or that has already logged an unusually high number of uncapped hours.

When at least one project is at risk, post a single prioritized alert to my Slack channel using the Send a Message action so it posts as a bot. Order the projects worst first, and for each one give the project name, the percent of budget or hours consumed, and the projected overage. Keep it a tight, scannable summary rather than a full table, and note at the end that the other active projects are on track. If nothing is at risk, do not send a message at all.

Make the warning threshold and the target Slack channel configurable, defaulting to 80 percent and a channel I specify.

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seatsPause marketing emails to escalated customers, then restore them