Pipedream is not a competitor. Waveloom's connections to Gmail, Slack, Notion, Linear, HubSpot and Google Calendar run on Pipedream Connect. We are a customer. This page exists because the honest answer to "Waveloom or Pipedream" is worth writing down.
Two different products
Pipedream is an integration platform built for developers. You write workflows with code steps, wire them to triggers from a large set of apps, and deploy without managing servers. Pipedream Connect is the part that lets a product embed integrations: provider-managed OAuth, so a user can link their Gmail or Slack to your app without you building and maintaining each provider's auth flow.
That second part is what Waveloom uses.
Waveloom is a background agent for founders and operators. It reads the sources above, follows web watches, and surfaces a handful of cards a day. Each card says why it matters. When a reply is needed, there is an editable draft. Two background actions exist, reply by email and reply in Slack, and both require your approval. Most items are dropped by design: a confidence bar, processing in small batches with a hard cap on cards per batch and notifications per day, one card per topic with new events joining its thread, quiet hours.
Waveloom has no builder, no code steps, no canvas. The judgement about what matters is the product.
What each is for
| Pipedream | Waveloom | |
|---|---|---|
| What it is for | Building integrations and workflows in code | Deciding what in your inbound matters |
| You build | Code-step workflows, or embedded integrations via Connect | Nothing. Connect sources, set watches |
| Human in the loop | Where your code puts one | Always, for anything that sends |
| Best when | You are a developer wiring systems together | You want a filter and an approval step |
Why we build on it
Connecting six providers, keeping their OAuth flows current and handling token refresh and revocation is a full-time job. It is not the job Waveloom exists to do. Pipedream Connect handles the connection layer so we can spend the work on triage, confidence, drafts and the rules that keep the feed quiet.
It also keeps disconnecting clean. Revoke the connection and Waveloom stops reading that source and clears the raw data it pulled from it. Cards already in your feed stay.
When you want which
If you are a developer and you know what you want to happen, Pipedream is the better tool. You write the steps, they run. If you are building a product that needs to talk to your users' apps, Connect is worth a serious look.
If you are a founder or operator who wants something to read your inbound, tell you only what needs you, and draft the reply for your approval, that is Waveloom. You do not write anything. You connect, and it watches.
Using both is normal. Your Pipedream workflows keep running. Waveloom sits alongside and decides what deserves a card. See use cases for examples, and the market research watch for the web side.