002 Machines 03 / 07
Overdue Monitor
Overdue invoices reach the right account manager in a daily digest, before finance has to escalate.
- Status
- Running
- Since
- Running since July 2026
- Built with
- n8n · Redash · Slack
- Proof
- Co-owned with RevOps
01 The miss
Invoices sat twenty-plus days overdue and nobody acted until finance escalated.
Corrected Overdue Monitor K.A.
02 The machine
An n8n workflow on Redash and Slack. Every day it reads the overdue invoices, groups them by account manager and posts each one a digest. Notes and snoozes are read back from the channel. Finance ops gets a Monday summary. Co-owned with RevOps.
03 How it runs
- How Overdue Monitor runs, step by step:
- Redash to Group
- Group to Daily digest
- Group to Monday summary
- Daily digest to Listen (a guard)
- Listen to Group (fed back)
04 Under the hood
- On version 5.1.1.
- Notes and snoozes are read back from the Slack channel, so a snoozed invoice stays out of the digest.
- Retries the warehouse query and stays inside Slack's block and character limits.
- Reads the free-text notes people leave in the channel.
- Code in Apify's GitHub, co-owned with RevOps.
schedule: every dayread: overdue invoices # Redashgroup_by: account_managerpost: one digest each # Slacklisten: # read back from the channel - notes - snoozes # a snoozed invoice stays quietmonday: summary for finance opsversion: 5.1.1The workflow as a node list, written for this page. The n8n export stays in a company repo.
05 What changed
- Each account manager gets a daily digest of their overdue invoices.
- Finance ops gets a Monday summary.
06 What I can show
The code lives in a company repo, so this page describes it.