The integrations game.

Most of the number is a webhook wearing a logo.

When an alerting platform advertises hundreds of integrations, most of that number is the same thing wearing different logos, a webhook with a parser. For alert intake, a robust generic webhook built for purpose covers most tools on day one, which means the count measures marketing effort more than capability. Integration counts are real in a few places. Alert intake is not one of them.

The anatomy of an alert-intake "integration" is simple. The monitoring tool can POST JSON, because every tool can. The platform maps the fields. Someone draws the logo card. Repeat for every tool with a webhook and you have a wall of hundreds. None of it is fake, exactly, each one works. It is that the unit being counted is a parser, and parsers are cheap.

The comparison sites then finish the job, because a number that is easy to compare is a number that gets compared. Integration count sits in every grid, weighted like it measures engineering, when for intake it mostly measures how many logo cards got drawn. It is the one metric on the page that the vendor can grow without making the product better.

Integration depth does exist, and it is worth paying for where it lives. Chat collaboration that puts the platform inside Teams or Slack as a participant, with actions and state, not just notifications. Ticket destinations where a record created downstream stays in sync both ways, including closure. Identity and SSO. On-call schedule exchange. These are stateful, bidirectional, and genuinely hard, a platform with ten of them did more engineering than a platform with four hundred intake logos.

Alert intake reduces to one motion, a payload arrives, over HTTP or email, and gets parsed, normalized, identified, and grouped. Build the generic intake properly, with automatic payload detection instead of field-mapping homework, and the long tail arrives free, the homegrown script, the tool no logo wall will ever include, the on-prem system that only knows how to send email. What matters is never whether your tool is on the list. It is what the record looks like after arrival.

Full disclosure, Signal9 keeps a connector catalog, with logos and a page per vendor. We keep it because buyers look for their tool by name, and the pages show exactly how to point each one at us. That is the honest function of every integrations wall, navigation, not capability. Under most of our logos sits the same universal webhook, and we would rather tell you that than have you discover it and wonder what else the wall was dressing up.

What we will not do is tell you the count is a reason to buy. The reason to buy is what happens in the thirty seconds after your payload arrives, and that is testable this afternoon with your own alert, no logo required.

Signal9's bet is on the thirty seconds after arrival, one intake built for purpose, parsing and identification that improve with use, and depth spent where depth pays, in Teams, Slack, and ticket destinations that stay in sync. The catalog exists so you can find your tool by name. The product is what happens to its payload.

Do integration counts matter when choosing an alerting platform? For alert intake, mostly no, the bulk of any large count is branded webhooks, the same generic intake wearing different logos. Counts matter where integrations are bidirectional and stateful, chat collaboration, ticket sync, identity. For intake, ignore the wall and test with your tool's real payload instead.

What is the difference between a webhook and an integration? Direction and state. A branded webhook pushes data in, one way, and could be replaced by a generic webhook without losing anything. A real integration exchanges data both ways and keeps state in sync, so removing it breaks a workflow. Most entries on a large integrations wall are the first kind counted like the second.

How many integrations does Signal9 have? Honestly, a catalog of documented vendors, and under most of them one universal webhook with automatic payload detection, plus email ingest for tools that only send mail. The deep ones are where depth matters, Microsoft Teams and Slack collaboration, and ticket destinations with two-way closure sync. If your tool can POST JSON or send an email, you can point it at Signal9, listed or not.