n8n send-and-wait for all notification channels
Built for Self-hosted n8n users building approval workflows across multiple communication channels who need flexible response collection..
“The idea is: Adding more “send and wait” integrations. I would like to use “send and wait” in a self hosted app, so I way to set this up would be great! As ther…”
The receipts — real demand
“The idea is: Adding more “send and wait” integrations. I would like to use “send and wait” in a self hosted app, so I way to set this up would be great! As there are so many way to send notifications and so, extending the notifications to send a signed confirmation link would be great!”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
Self-hosted n8n users building approval workflows across Slack, email, SMS, and other channels represent a dedicated automation community. No search volume, but the pain signal (lack of flexible send-and-wait across channels) is specific to workflow automation power users.
Competition & the opening
Sparse competition (3/10): only n8n's native integrations exist. Gap is a unified send-and-wait interface that collects responses from any notification channel without building custom logic.
What's hard to build
Requires building response collection handlers for each channel (Slack buttons, email replies, SMS responses, webhooks), managing state across distributed channels, and timeout handling. Feasibility 5/10 reflects the need for robust channel-specific SDKs and state management.
Why now
n8n's send-and-wait is bottlenecked to email; expanding to Slack/webhooks/SMS unlocks workflow approval use cases.
How you'd monetize
$199-499/mo SaaS or per-integration add-on tier