All requests
In progressPublic request — anyone can read this thread

Send Detector alerts to a Slack channel, not just email

LBLaura BennettProcurement Manager ·

We monitor 31 supplier pages with Detector. Every change alert goes to a mailbox that one person reads, and by the time it is forwarded into the right channel the change is a day old.

What we actually need

  • A Slack workspace connection, set up once by an admin.
  • A default channel every alert posts into.
  • Per-monitor routing, so a monitor can override the default.

The message itself does not need to be clever. A title, the URL, what changed and a link into the dashboard covers it — we open the diff in the app anyway.

Why it matters

The value of a change alert decays fast. A supplier price page that changed this morning is worth a conversation today; the same alert on Thursday is archaeology. Email adds a person-shaped delay to every one of them.

What we do today

A rule in the shared mailbox forwards anything from Detector to a Zapier hook that posts into #supplier-watch. It works until somebody edits the rule, and it drops the diff link because the forwarded HTML gets mangled.

DetectorIntegrations
Progress
  1. Filed
  2. In review
  3. Approved
  4. In progress
  5. Shipped
84 people need this too
4 commentsSorted by oldest
LB

Laura Bennett, Procurement Manager ·
A per-monitor channel would be ideal. Pricing changes go to commercial, terms changes go to legal, and neither team wants the other's noise.

IN

Incapon ·
Approved. Shipping the workspace connection and one default channel first, then per-monitor routing on top of it.

CV

Chris Vogel, Category Buyer ·
We would take this over email entirely. Same for us on Teams if that ever comes up.

IN

Incapon ·
In progress — the OAuth install is done and alerts are posting to a test workspace. Per-monitor routing is next.