SALES

Overdue Commitment Sweep with Linear Escalation

Runs a nightly sweep over logged call commitments, finds the next-steps that passed their promised date without completion.

CategorySales
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule
  • ActionQuery overdue open commitments from PostgresPostgreSQLPostgres
  • LogicFilter out resolved or rescheduled items
  • ActionOpen a Linear issue per slipped commitmentLinearLinear
  • ActionAlert the rep's manager in SlackSlack
  • OutputMark commitments escalated in PostgresPostgreSQLPostgres

What it does

This scheduled workflow scans previously captured call commitments stored in Postgres, detects any whose promised due date has passed and that aren't marked done, and escalates each one as a Linear issue with a Slack ping to the rep's manager.

When to use it

Use it when capturing commitments isn't enough and you need enforcement. It's for sales operations teams that want a reliable nightly check ensuring slipped promises get owned and resolved rather than silently aging.

How it works

  1. 1A nightly schedule triggers the sweep.
  2. 2The workflow queries the Postgres commitments table for open items past their due date.
  3. 3A logic step filters out items already resolved or recently rescheduled.
  4. 4For each genuine slip, a Linear issue is created with the original promise, deal context, and days overdue.
  5. 5A Slack message is sent to the owning rep's manager summarizing the escalations.
  6. 6The commitment record is updated in Postgres to mark it escalated, preventing duplicate issues on the next run.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.