Log your Snyk vulnerability counts to Sheets every morning

Every weekday at 7am, snapshot our open Snyk vulnerability counts by severity, append them as one dated row in a Google Sheets tracking tab, and post a one line summary to Slack. The point is a consistent daily metrics log that can drive a burndown chart, not a written report.

Step 1, fetch the issues. Use the Snyk operation "Get issues by org ID" against the organization I connect, paging through every result until the feed is exhausted so the counts cover the whole org rather than just the first page. Count only issues that are currently open, ignoring anything resolved or ignored.

Step 2, count by severity. Group the open issues into exactly four buckets using each issue's effective severity: critical, high, medium, and low. Any severity value outside those four should be left out of all four counts rather than folded into the nearest bucket. A bucket with nothing in it is a 0, never a blank.

Step 3, read the previous row. Before writing anything, use the Google Sheets operation "Get Values" to read the existing rows in the tracking tab and pick up the most recent entry, so the four counts from the last run are available for comparison. If the tab has no data rows yet, treat this as the first run.

Step 4, append today's row. Use the Google Sheets operation "Append Values" to add exactly one row to the tracking tab, with five columns in a fixed order: date, critical, high, medium, low. Use today's date in YYYY-MM-DD format and write the counts as plain numbers so the sheet can chart them. Always append, never overwrite an existing row, and always write one row per run even when nothing changed.

Step 5, post the Slack line. Use the Slack operation "Send a Message" to post a single line to the channel I choose, showing today's date, the four counts, and the change against the previous row in parentheses, for example: Snyk 2026-08-07: 3 critical (+1), 12 high (-2), 44 medium (0), 87 low (+5). Show a signed number for every severity, including 0 when a count is unchanged. On the first run, when there is no previous row, post the four counts with no change values.

Keep this deliberately narrow. Do not summarize, prioritize, or comment on the numbers, do not name individual vulnerabilities or projects, and do not skip the run or the Slack message on a quiet day. The same four numbers written to the same place every day is the entire product.