Skip to main content

Connecting Google Chat, Discord, Opsgenie or Freshservice

Four more delivery destinations for alerts. Discord and Opsgenie are fully available; Google Chat and Freshservice are beta, with the exact limitation named.

Written for whoever runs IT7 min readUpdated

Four more places an alert can reach you, beyond Slack, Microsoft Teams, PagerDuty, Jira and ServiceNow. Two are fully available today; two are beta, each with a specific, named limitation rather than a vague one.

Discord — available

  1. Create a webhook

    In the Discord channel you want alerts in, go to channel settings → Integrations → Webhooks → New Webhook, and copy the webhook URL.

  2. Connect it in Qorionix

    Under Integrations → Catalog → Discord, choose Notify, paste the webhook URL, and press Test and save.

Discord's own webhook metadata endpoint answers a real GET request without posting a message, so the test proves the webhook exists and is reachable without sending anything to the channel.

Opsgenie — available

  1. Create an API integration

    In Opsgenie, go to Settings → Integrations → Add integration → API, and grant it Create and Read. Copy the integration key (a GenieKey).

  2. Connect it in Qorionix

    Under Integrations → Catalog → Opsgenie, choose On-call, paste the key, choose your region (EU or US), and press Test and save.

The test creates and immediately force-closes a real test alert in Opsgenie, so you may briefly see a test alert appear and resolve. Alerts and their resolutions use the same stable deduplication key derivation PagerDuty already uses, so a resolved Qorionix incident closes the matching Opsgenie alert rather than leaving it open.

Google Chat — beta

  1. Create a webhook

    In the target Google Chat space, go to Apps & integrations → add a webhook, and copy the full URL, including its key and token query parameters.

  2. Connect it in Qorionix

    Under Integrations → Catalog → Google Chat, choose Notify, paste the full webhook URL, and press Test and save, understanding that Test sends a real message.

Freshservice — beta

  1. Get an API key

    In Freshservice, go to your profile → API Key. Note your Freshservice subdomain, and a requester email address to raise tickets as.

  2. Connect it in Qorionix

    Under Integrations → Catalog → Freshservice, choose Ticketing, enter the subdomain, API key and requester email, and press Test and save. The test reads your tickets list, which does not create anything.

Tickets are created with severity mapped to Freshservice's priority scale (1–4) and the finding rendered as an HTML table in the ticket body.

Was this article wrong?

If a procedure here does not match what you see, or a limit we described has changed, tell us and we will fix the page. Email us about this article, or see how to get help if you need an answer rather than a correction.

Everything in integrations and notifications