Weekly Procore cost code overrun early warning in Slack

Every Monday at 6am, give me an early warning on the Procore cost codes trending toward an overrun, before anyone thinks to open the budget dashboard.

Start with Procore List Projects to get the active projects. For each project, call List Budget Views to find the budget views available on it and use the project's standard budget view, falling back to the first view returned. Then call List Budget Details for that project and budget view to read every row of the budget detail report. If a project has no budget views, or its detail report comes back empty, skip it quietly and mention it in the run notes rather than failing the whole run.

For every cost code row, add committed cost and actual cost together, then divide by the revised budget to get a percent used. Flag a row only when both conditions hold: the percent used crosses 90 percent, and the revised budget is above a dollar floor of 50,000. Expose both the 90 percent threshold and the 50,000 floor as configurable inputs at the top of the workflow so they can be tuned without touching the logic. Skip any row where the revised budget is zero, blank or missing, so it cannot divide by zero or produce a false positive.

For each flagged row, compute a projected dollar variance of committed plus actual minus the revised budget, so a positive number means the cost code is already over and a negative number is the cushion still left. Rank all flagged rows across every project by that projected variance from highest to lowest, so the largest exposure in the portfolio is at the top rather than buried under whichever project happened to be listed first.

Post the result as one Slack Send a Message alert to the channel I choose. List only the flagged cost codes, in that ranked order, each line carrying the cost code and its description, the project name, the revised budget, committed plus actual, the percent used, and the projected variance formatted as dollars. Open with a one line summary of how many cost codes were flagged across how many projects. If nothing crosses the threshold, send nothing at all: no empty digest, no all clear message. A Monday alert should always mean something needs attention.

Append every flagged row to a tracking spreadsheet using Google Sheets Append Values, one row per flagged cost code, with the run date in the first column followed by project name, cost code, description, revised budget, committed cost, actual cost, percent used and projected variance. The run date on every row is what makes week over week movement visible, so always append and never overwrite earlier rows.

Two details to handle carefully. Budget detail report columns depend on how each budget view is configured, so match columns by meaning rather than assuming fixed field names: find the revised budget column, the committed cost column, and the direct or actual cost column, and if one is genuinely absent from a view, skip that project and say so in the run notes. If budget rows carry cost code identifiers instead of readable labels, resolve them with Procore List Cost Codes so the Slack message reads in plain language. Procore also rate limits requests, so page through list results and pace the calls when there are many active projects.