n8n is an open source workflow automation platform. You connect nodes into a flow, run it in their cloud or on your own server, and extend it with code when a node does not exist. If you want to own the stack, n8n is a serious option.
Waveloom is a background agent for founders and operators. It reads Gmail, Slack, Notion, Linear, HubSpot and Google Calendar, follows web watches, and surfaces a handful of cards a day in one feed. Each card has a one-line reason. When a reply is needed, there is an editable draft. It executes two background actions, reply by email and reply in Slack, and only after explicit approval.
What each is for
| n8n | Waveloom | |
|---|---|---|
| What it is for | Building and hosting your own workflows | Deciding what in your inbound matters |
| You build | Node-based flows, with code when needed | Nothing. Connect sources, set watches |
| Human in the loop | Where you add one | Always, for anything that sends |
| Best when | You want control and a known sequence | You want judgement over unknown input |
Where n8n is the right call
You want the workflow on infrastructure you control. You have engineers who will extend it. Your sequences are known and repeatable, and you want them to run without asking anyone. n8n gives you that, and open source means the logic is inspectable and portable.
n8n also lets you wire AI models into flows. Useful, but it is still a flow you designed. The model does what that step says.
Where Waveloom is the right call
You do not want to build or host anything. You want something to read your tools and tell you only what needs you.
Waveloom processes items in small batches and scores each for confidence. Low confidence is dropped, not parked. If unsure, nothing happens. A hard cap limits how many cards a batch can create and how many notifications go out per day, a topic that already has a card doesn't get a second one (new events join its thread), and quiet hours hold notifications. Most of what it sees, it decides not to mention, and the feed shows the counts so you know it looked.
Cards that do appear come with a reason and, when relevant, a draft. A Linear issue stalled while a customer waits. A competitor page that changed in a way your watch cares about. You approve, edit, or dismiss. Nothing is sent without you.
A morning brief arrives once a day, and is skipped when there is nothing solid to put in it.
Using both
These do not compete. n8n runs the sequences you own. Waveloom watches the inbound you cannot script.
What Waveloom will not do: self-host, expose a builder, run outreach, send on its own, or act as a chatbot. If those are requirements, n8n is the better tool. See use cases for examples, and the market research watch for web watches.
Where this stands
Waveloom is in an invite-only founding beta. The cohort is small on purpose, so thresholds can be tuned with people who will say when a card was wrong. Join the waitlist.