iPM doesn't need to be the only place your team works — integrations let alerts, authentication, and data flow between iPM and the other tools already in use, under Administration, then Integrations.
Common integration types
- Directory / SSO (LDAP, Active Directory) — let team members log in with their existing corporate credentials instead of a separate iPM-specific password, and centralize account deactivation through the same directory used everywhere else.
- Chat notifications (Slack, Microsoft Teams, or a generic webhook) — post alerts directly into a team channel alongside, or instead of, email. This is often faster for an on-call team to notice than an inbox.
- Ticketing systems — automatically create or update a ticket in an external system when a critical alert fires, so incident tracking stays in the tool your team already uses for that purpose, without someone manually copying details across.
- Generic webhooks / API access — for anything not covered by a built-in integration, a webhook lets an alert trigger custom logic in your own tooling.
Setting one up
- Choose the integration type and provide the required connection details (a webhook URL, directory server address, or API credentials, depending on the type).
- Test the connection before relying on it — most integrations offer a way to send a sample event through.
- Scope it deliberately — route only the alert severities or host groups that are actually relevant to that integration, the same way you would with Alert Escalation, rather than forwarding everything.
Keep integrations scoped and tested
An integration that fires on every alert, regardless of severity, quickly becomes noise in whatever system it's feeding — the same alert fatigue problem covered in Alert Escalation applies just as much to a Slack channel or a ticketing queue as it does to email.