This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
n8n counts an execution every time a Slack Trigger fires: every message, edit and bot post. Not Today is a small Cloudflare Worker in front of n8n that checks Slack's signature and forwards only what a workflow acts on. Free, open source, npx nottoday.
Hi Product Hunt 👋 I'm Sigit Kusuma, and I made Not Today: saving your n8n executions, one "nope" at a time.
I built this after watching a Slack alert bot on n8n Cloud burn through its monthly executions on messages it threw away at the first check. It only cared about a few mentions, but every message in every channel it was in started a run.
The cause: n8n counts an execution every time a trigger fires, and a Slack Trigger fires on every message, edit, reaction and bot post. A filter inside the workflow comes too late: by the time the IF node says no, the run already counts.
Not Today moves that filter in front of n8n. It's a small Cloudflare Worker in your own Cloudflare account. It checks Slack's signature, answers Slack straight away, and forwards only the requests a route matches, byte for byte, so your existing Slack Trigger node keeps working without changes. Everything else is dropped and counted as an execution saved.
You set it up with npx nottoday, which opens a console on your own machine. It installs the Worker, walks you through the Slack app, and lets you build routes like "only messages that mention someone on the on-call list" or "only DMs to the bot". You can try a message against a route before saving it.
The one rule: a route's filters must be at least as loose as the workflow's own checks. It may forward something the workflow then ignores; it must never drop something the workflow would act on. That's why every route starts in shadow mode, where it records what it would drop without dropping anything, until you switch it to enforce.
It runs on Cloudflare's free plan, your tokens stay on your machine, and message text is never logged. GitHub, Telegram and generic webhooks already work in the engine and are next in the console.
I'd love to hear which Slack workflows eat the most executions for you, and what you'd want filtered next.
No comment highlights available yet. Please check back later!
About Not Today on Product Hunt
“Saving your n8n executions, one "nope" at a time”
Not Today was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #120 on the daily leaderboard. n8n counts an execution every time a Slack Trigger fires: every message, edit and bot post. Not Today is a small Cloudflare Worker in front of n8n that checks Slack's signature and forwards only what a workflow acts on. Free, open source, npx nottoday.
Not Today was featured in Open Source (69k followers), Developer Tools (522.6k followers), GitHub (41.5k followers) and No-Code (6.1k followers) on Product Hunt. Together, these topics include over 149.6k products, making this a competitive space to launch in.
Who hunted Not Today?
Not Today was hunted by Sigit Kusuma. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Not Today stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Sigit Kusuma
Hi Product Hunt 👋 I'm Sigit Kusuma, and I made Not Today: saving your n8n executions, one "nope" at a time.
I built this after watching a Slack alert bot on n8n Cloud burn through its monthly executions on messages it threw away at the first check. It only cared about a few mentions, but every message in every channel it was in started a run.
The cause: n8n counts an execution every time a trigger fires, and a Slack Trigger fires on every message, edit, reaction and bot post. A filter inside the workflow comes too late: by the time the IF node says no, the run already counts.
Not Today moves that filter in front of n8n. It's a small Cloudflare Worker in your own Cloudflare account. It checks Slack's signature, answers Slack straight away, and forwards only the requests a route matches, byte for byte, so your existing Slack Trigger node keeps working without changes. Everything else is dropped and counted as an execution saved.
You set it up with npx nottoday, which opens a console on your own machine. It installs the Worker, walks you through the Slack app, and lets you build routes like "only messages that mention someone on the on-call list" or "only DMs to the bot". You can try a message against a route before saving it.
The one rule: a route's filters must be at least as loose as the workflow's own checks. It may forward something the workflow then ignores; it must never drop something the workflow would act on. That's why every route starts in shadow mode, where it records what it would drop without dropping anything, until you switch it to enforce.
It runs on Cloudflare's free plan, your tokens stay on your machine, and message text is never logged. GitHub, Telegram and generic webhooks already work in the engine and are next in the console.
I'd love to hear which Slack workflows eat the most executions for you, and what you'd want filtered next.