The trap in n8n, Zapier, and Make is a Slack (or Telegram, or email) node at the end of every scenario. When the team leaves Slack — or when you want Android push on a server you run — you edit thirty workflows.
AlertHub is the last node. HTTP Request (n8n) or the AlertHub Zap/Make action sends one event. Gotify lives in Connections. Warning → Gotify priority 5; critical → 8. Info is dashboard only.
Guides you already have for Slack/Telegram last-hops: n8n, Zapier, Make. Do not rebuild those Zaps. Add Gotify.
Gotify must be HTTPS and reachable from the internet.
When which tool
| Situation | Prefer |
|---|---|
| Self-hosted workflows, branches, code nodes | n8n → AlertHub → Gotify |
| No-code SaaS, 8k+ apps | Zapier or Make → AlertHub → Gotify |
| Stripe / Shopify / GitHub host webhooks | Native URL, skip the automation tool |
| WordPress hooks | Official plugin |
Compare Zapier vs Make: Zapier vs Make for alerts.
Setup (once)
- Same ingest as today: n8n HTTP POST to
https://api.thealerthub.com/sendAlert, or the Zapier/Make AlertHub action. Secret key on the project. - Delete duplicate Slack/Telegram nodes after Gotify is confirmed — or keep Slack for the team (hybrid).
- Gotify Apps →
https://your-gotify/message?token=…in Connections → Gotify.
n8n: Ingestion API. Zapier invite and fields: Zapier docs. Make: Make docs.
Alert 1: n8n error workflow → Gotify 8
n8n’s Error Workflow should POST critical with the workflow name and $json.execution.id. Broken automations page Android; business events can stay warning. Do not also notify Slack from the error workflow if AlertHub already fans out.
Alert 2: Zapier / Make Filter then AlertHub
Keep Filters in Zapier/Make (amount, status, environment). Map warning vs critical vs info in the AlertHub action. Gotify never sees info. That is how you avoid paging on every Typeform spam submission — see also Typeform via Zapier.
Alert 3: Airtable / HubSpot without a chat module
Airtable and HubSpot via Make already end in AlertHub. Paste Gotify; the scenario stays one module. Same for any of the 8k Zapier apps: one Send Alert action.
Ideas to squeeze more value
- One Gotify app for all scenarios.
ah_source=n8n:billing,Zapier:forms,Make:crm. - Do not POST to Gotify from a code node. You will forget the token on the next rotate.
- ntfy if you refuse to run Gotify. Same last node, ntfy Connection.
- Native Stripe/Shopify webhooks skip n8n when the host can POST — Stripe → Gotify.
FAQ
Is there an official n8n node?
HTTP Request is enough. Same ah_* JSON as the API.
Self-hosted n8n cannot egress?
Then AlertHub never sees the event. Allowlist api.thealerthub.com.
Will Zapier tasks multiply per channel?
No. One AlertHub action. Gotify (and Slack) are AlertHub Connections, not extra Zap steps.
Next steps
Send one test warning from n8n or Zapier, paste Gotify, then remove the duplicate chat modules.
Related: Gotify setup · n8n to Slack/Telegram · Stripe → Gotify