Easy Setup
Works with any alert source via e-mail. No special integrations needed.
If it can send an e-mail, it works with Tiquify. Nagios, Prometheus Alertmanager, Grafana, cron jobs, scripts — anything that sends alerts via e-mail is supported out of the box.
Define rules to classify, route, and enrich incoming messages before they become tickets. Filter noise, set severity automatically, and keep your inbox clean.
Each device in your inventory gets its own unique e-mail address. Alerts sent to that address are automatically associated with the correct device.
External contacts can be included in ticket e-mail conversations even if they don't have a Tiquify account. Keep everyone in the loop without extra onboarding.
Up and Running in Minutes
Tiquify is designed to fit into your existing monitoring setup without requiring you to change tools or write integrations. If your monitoring stack can send e-mail, you’re ready to go.
Why E-Mail?
E-mail is the lowest common denominator for alert delivery. Every monitoring tool supports it. By using e-mail as the input channel, Tiquify works with:
- Infrastructure monitoring — Nagios, Icinga, Zabbix, Checkmk
- Metrics and alerting — Prometheus Alertmanager, Grafana, Victoria Metrics
- Cloud platforms — AWS CloudWatch, Azure Monitor, GCP Alerting
- Custom scripts — any script that can run
sendmailorcurl - IoT and embedded devices — anything with SMTP support
Rule-Based Preprocessing
Not every alert is worth a ticket. Tiquify lets you define rules that run on incoming messages before they create tickets:
- Filter out known-noisy alerts
- Set severity based on keywords or sender
- Route messages to the right organization
- Enrich tickets with additional context
Per-Device Addressing
Every device in your inventory gets a unique e-mail address. Configure your monitoring tool to send alerts for that device to its Tiquify address, and incoming messages are automatically linked to the correct device — no manual tagging required.
Ticket Deduplication
When the same alert fires multiple times, Tiquify adds the new message to the existing open ticket rather than creating a new one. Your team works on one ticket per issue, not one per notification. If the ticket was closed and the alert fires again, the ticket is re-opened with full context preserved.
See it in action
See how quickly you can connect your existing monitoring tools to Tiquify.
