FINANCE

Alert when runway crosses a danger threshold

On each runway recompute, check the new months-of-runway against configured thresholds and page finance via Slack and PagerDuty only when it crosses below a warning or critical…

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled runway check
  • ActionRead latest runway figure from SnowflakeSnowflakeSnowflake
  • LogicCompare against warning/critical thresholds
  • OutputPost breach alert to SlackSlack
  • OutputOpen PagerDuty incident if criticalPagerDutyPagerDuty

What it does

This workflow watches the runway number itself. Each time runway is recomputed in Snowflake or written to the model, it compares the value against two thresholds you set (for example 9 months warning, 6 months critical). If runway is healthy, nothing happens. If it dips below warning it posts a Slack alert; below critical it also opens a PagerDuty incident so the breach can't be missed over a weekend.

When to use it

Use it when you want runway to be quiet most of the time and loud exactly when it matters. Suited to teams who don't want another daily report but do need a hard tripwire as cash tightens.

How it works

  1. 1A schedule reads the latest runway figure from Snowflake.
  2. 2The value is compared against warning and critical thresholds.
  3. 3If runway is above warning, the run exits with no noise.
  4. 4Below warning, a contextual alert (current runway, burn, delta) goes to Slack.
  5. 5Below critical, a PagerDuty incident is opened in addition to the Slack alert.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect PagerDutyIncidents, on-call, escalations.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.