Zapier can already send a Slack message. The problem starts when you also want Telegram for on-call, email as backup, Discord for the community, and a history you can search next month.
Most teams duplicate Zaps: New Stripe payment → Slack, then a second Zap to email, then a third if someone prefers WhatsApp. Each Zap counts against your task quota. Each one breaks separately when a webhook URL changes.
AlertHub sits in the middle. One Zapier action — Send a New Alert — and AlertHub delivers warning/critical events to every destination you configured, plus a live dashboard. Change Slack to Teams without editing the Zap.
This is the pattern behind “Zapier Telegram notification”, “Zapier WhatsApp alert”, and “one Zap, many channels.”
What you get that native Zapier notifications miss
- One task, many channels. Slack + Telegram + email + mobile push without extra Zap steps.
- Severity.
infois logged only.warningandcriticalpage people. Native Slack steps cannot do that globally. - History. Chat threads are not an incident log. AlertHub is.
- Teams. Invite colleagues to the project. They see alerts without being added to every Zap.
- Swap destinations later. New hire uses Discord? Add it in AlertHub Connections. The Zap stays untouched.
Step 1: AlertHub project
- Sign up at app.thealerthub.com (getting started).
- Create a project and copy the One-Way Secret Key.
- Connect Slack, Telegram, email, or WhatsApp under Connections.
WhatsApp is a paid destination. Slack and Telegram have free-friendly setups: Slack, Telegram.
Step 2: Accept the Zapier invite
The integration is available via public invite:
👉 Accept the AlertHub Zapier invite
Full screenshots and field names: Zapier documentation.
Step 3: Build the Zap
- Trigger — any of 8,000+ apps (Stripe, Typeform, Google Sheets, HubSpot, Gmail, Calendly…).
- Action — Alerthub → Send a New Alert.
- Connect with the project name + secret key.
- Map fields:
| AlertHub field | Tip |
|---|---|
| Alert title | Short, scannable. Include the entity: New lead: {{email}} |
| Alert description | Extra context from previous steps |
| Alert level | warning or critical if it must leave the dashboard |
| Source | Zapier, or the app name (Typeform, Calendly) |
Turn the Zap on. Test once and confirm the row in the AlertHub feed.
High-traffic Zap ideas (copy these)
These are the automations people actually search for — and they all share the same AlertHub action:
| Trigger | Title example | Level |
|---|---|---|
| Calendly — Invitee created | New meeting: {{Name}} | Warning |
| Google Sheets — New row | Ops row: {{column_a}} | Info or Warning |
| Gmail — New labeled email | VIP inbox: {{Subject}} | Warning |
| Shopify — New paid order | Shopify order {{Order number}} | Warning |
| RSS — New item | Competitor posted: {{Title}} | Info |
| Schedule — Every day | Daily Zap heartbeat | Info (proves the Zap is alive) |
More recipes: Typeform and Google Forms, Stripe via Zapier.
How to use severity well
Treat AlertHub levels like an on-call policy:
- info — audit trail (every sheet row, every RSS item). Dashboard only.
- warning — someone should see it today (new paid order, new demo booking).
- critical — drop what you are doing (payment failed, uptime down, enterprise deal).
If everything is critical, nothing is. The Zap is the right place to branch: a Filter or Paths step can send VIP customers as critical and the rest as info.
Zapier vs wiring Slack directly
| Zapier → Slack | Zapier → AlertHub | |
|---|---|---|
| Extra channels | New action / new Zap | Toggle a destination |
| Searchable log | Slack search (noisy) | Alert feed with filters |
| Mobile app for alerts | Slack app | AlertHub app + any chat |
| Change of tool | Edit every Zap | Edit Connections once |
Use Zapier for catching events in apps that are not WordPress. Use the WordPress plugin for hooks on the site itself. Prefer Make if your scenarios are already there — comparison: Zapier vs Make for alerts.
FAQ
Does this consume more Zapier tasks?
Usually fewer. One AlertHub action replaces Slack + Email + Telegram steps.
Is the integration invite-only?
Yes, via the public invite link. After you accept it, AlertHub appears in your Zapier account (it may show as Invite Only).
Can I send custom JSON?
For raw HTTP, use the Ingestion API. The Zapier action covers title, description, level, and source — enough for most no-code flows.
Next steps
Accept the Zapier invite, connect one destination, and replace your next “notify Slack” step with Send a New Alert. You will not rebuild that Zap when the team moves to Telegram.