Integrations Overview

An integration is a connection between JAMS Incident Management and an external system you already use. Some integrations send signals INTO JAMS Incident Management (so your alerts know when something fails); others let JAMS Incident Management reach OUT (so callers can take action via voice or SMS). One β€” SSO β€” handles authentication, not alerts.

Each integration is configured once per tenant. After setup, all your flows can use it.

What's available today

Inbound β€” things that fire flows

IntegrationWhat it doesSetup
WebhookThe most generic trigger. Anything that can make an HTTP POST can fire a flow.None β€” every flow you make gets its own webhook URL.
Email (IMAP)Monitor a mailbox; fire when emails match a subject/body keyword.Email Connections. Microsoft Graph for O365, plus generic IMAP.
API monitorPeriodically GET an endpoint; fire when the response matches a condition.API Connections.
Azure MonitorReceive alerts from Azure Monitor alert rules.Integrations β†’ Azure Monitor.
Grafana & PrometheusReceive alerts from Grafana (self-hosted or Cloud) or Prometheus Alertmanager; stop when they resolve.Integrations β†’ Grafana & Prometheus.
JAMS SchedulerReceive job-failure alerts from JAMS Scheduler. Recipients acknowledge from a voice call (press 1 / say "confirm") or by replying to the SMS.Integrations β†’ JAMS Scheduler.
Windows servicesWatch any Windows service on any server and fire when one stops. The same Agent also reports JAMS Scheduler service health and MSMQ queue depth.Integrations -> Windows Services.

Two-way ticketing (ITSM / help desk)

These both fire flows when a ticket comes in and let JAMS Incident Management write the response back. When an on-call responder Acknowledges or Resolves (by voice, SMS, Teams/Slack button, or the /incidents page), JAMS Incident Management updates the originating ticket β€” and if the ticket is resolved on the vendor side, it stops escalating.

IntegrationWhat it doesSetup
ServiceNowEscalate ServiceNow incidents; push Acknowledge β†’ In Progress / Resolve β†’ Resolved back into the incident, with a work note.Integrations β†’ ServiceNow.
ZendeskEscalate Zendesk tickets; push Acknowledge β†’ Open / Solve β†’ Solved back into the ticket, with an internal comment.Integrations β†’ Zendesk.
FreshserviceEscalate the Freshservice tickets you choose (by priority, type or group); Acknowledge adds a private note, Resolve sets Resolved with a resolution note.Integrations β†’ Freshservice.

Jira (one-way for now) pages your on-call team when a Jira issue is created and stops when it moves to Done. Acknowledging stops the alerts in JAMS Incident Management but does not update the issue. Setup: Integrations β†’ Jira β€” see Jira.

Also works in reverse β€” open a ticket from any alert. Beyond receiving tickets, JAMS Incident Management can create a new ServiceNow incident, Zendesk ticket or Freshservice ticket in response to any other alert (a JAMS Scheduler job failure, email, API, webhook, or manual send). The on-call responder opens it straight from the call, SMS, Teams/Slack card, or the /notifications page β€” and doing so also acknowledges the alert. You turn it on per flow; see the ServiceNow, Zendesk and Freshservice guides.

Outbound β€” what JAMS Incident Management uses to deliver

JAMS Incident Management delivers on seven channels: email, SMS, voice call, push, Microsoft Teams, Slack, and WhatsApp. The infrastructure behind voice/SMS is dual-provider with automatic failover (Twilio + Azure Communication Services), but it's invisible to users β€” you don't configure providers per-flow.

Two of these are also integrations you set up once per tenant:

IntegrationWhat it doesSetup
Microsoft TeamsPost alerts to a Teams channel or DM linked responders an adaptive card with Acknowledge / Escalate buttons. Acks attribute to the named person and the card flips to "Acknowledged by …".Integrations β†’ Teams.
SlackPost alerts to a Slack channel or DM linked responders a Block Kit message with Acknowledge / Escalate buttons. Acks attribute to the named person and the message flips to "Acknowledged by …".Integrations β†’ Slack.
Push (PWA)Deliver to a teammate's installed app on their phone or desktop.Each user enables it on their own device β€” see Push Notifications.

What you DO configure for email: per-tenant email transports if you want emails from your domain rather than JAMS Incident Management's:

IntegrationWhat it doesSetup
Microsoft Graph (O365)Send notification emails through your tenant's Office 365.Email Connections β†’ Add β†’ Microsoft. OAuth into the M365 account.
SendGridSend via SendGrid using an API key.Email Connections β†’ Add β†’ SendGrid.
SMTPSend via any SMTP server.Email Connections β†’ Add β†’ SMTP.

If you skip this, emails go from JAMS Incident Management's default sender (alerts@jamssoftware.com). Fine for most teams.

Migrating in from another tool

Migrating from PagerDuty brings across people, teams, schedules, rotations, escalation policies and overrides. You get a full report first β€” what would be created, the coverage you'd actually end up with, and anything that can't be represented faithfully β€” and nothing is written until you confirm. Importing people emails nobody; you invite them individually when you're ready to cut over.

Migrating from Opsgenie brings your existing on-call schedules across β€” rotations, turn lengths, coverage hours, people and overrides β€” rather than making you rebuild them by hand. You get a full report of what would be created, including the coverage you'd actually end up with, before anything is written.

Worth starting early if it applies to you: Opsgenie closes on 5 April 2027 and any configuration left behind is deleted.

Both start with a read-only check, so you can see exactly what a migration would produce before committing to one.

Authentication β€” SSO

Single Sign-On (SSO) lets your team log in via your existing identity provider instead of password. JAMS Incident Management supports any standards-compliant OIDC provider β€” Microsoft Entra ID, Okta, Google Workspace, Auth0, OneLogin, Keycloak, etc.

Detailed walkthroughs for the most common IdPs:

When to use which trigger

A lot of first-time users ask "which integration should I use for X?" Some guidance:

  • You have a custom script / app that knows something failed β†’ Webhook. Easiest, most flexible.
  • You're already getting failure emails (from a build system, monitoring tool, vendor alert) β†’ Email (IMAP). Don't rebuild what's already working β€” just teach JAMS Incident Management to read those emails.
  • You're trying to monitor an HTTP API for uptime / specific responses β†’ API monitor.
  • You're an Azure shop and have alert rules in the portal β†’ Azure Monitor.
  • You alert from Grafana or Prometheus (including teams left without phone and SMS paging when Grafana OnCall OSS was retired) β†’ Grafana & Prometheus. See Grafana & Prometheus Alertmanager.
  • You run ServiceNow ITSM and want a human paged on P1 incidents β†’ ServiceNow. Two-way: the on-call's Acknowledge / Resolve syncs back to the incident. See ServiceNow.
  • You run Zendesk and want urgent tickets to page someone, not just sit in a queue β†’ Zendesk. Two-way: Acknowledge / Solve syncs back to the ticket. See Zendesk.
  • You run Freshservice and want urgent tickets to page someone β†’ Freshservice. Two-way: Acknowledge / Resolve syncs back to the ticket. See Freshservice.
  • You track work in Jira and want new urgent issues to page someone β†’ Jira. See Jira.
  • You run JAMS Scheduler β†’ JAMS Scheduler integration. Two-way: a failed job alerts your on-call team, who acknowledge from a voice call (press 1 / say "confirm") or an SMS reply β€” and, with the on-prem JAMS Incident Connector installed, restart / continue / cancel / retry the job right from the phone. See JAMS Scheduler.
  • You run Skybot Scheduler (5.0.48 or later) β†’ Skybot integration. Failed jobs page your on-call team, who can restart, end or hold the job from the call, text, or Teams/Slack card. See Skybot Scheduler.
  • You run GoAnywhere MFT β†’ GoAnywhere integration. Failed projects page your on-call team, who can run the project again from the call, text, or Teams/Slack card. It can also alert when a file-transfer service stops or a certificate is about to expire. See GoAnywhere MFT.
  • Your team lives in Microsoft Teams β†’ add Teams as a delivery channel so alerts land where people already are, with one-click Acknowledge / Escalate on the card. See Microsoft Teams.
  • Your team lives in Slack β†’ add Slack as a delivery channel β€” same one-click Acknowledge / Escalate, as a DM or a channel post. See Slack.

When in doubt, start with webhook. It's the most universal and you can switch to a more specific trigger later by editing the flow.

How integrations relate to flows

Each integration is not a flow β€” it's a connection that flows reference. One integration can be used by many flows. Editing the integration affects all flows that use it (which is usually what you want).

A few examples:

  • One Email Connection, many flows. Connect monitoring@example.com once; then have separate flows for "alerts containing CRITICAL", "alerts from server X", "alerts from vendor Y". All read from the same mailbox.
  • One JAMS Connection, one flow. JAMS Scheduler connections create their own managed flow on save (one connection = one flow, by design β€” the flow's recipients/channels define how JAMS Scheduler failures are routed). You can edit recipients on the flow without changing the JAMS connection.
  • One SSO config per tenant. Used by every user that logs in.

What's next

  • Microsoft Teams β€” deliver alerts to Teams with one-click Acknowledge / Escalate
  • Slack β€” deliver alerts to Slack with one-click Acknowledge / Escalate
  • JAMS Scheduler β€” alert on failed JAMS jobs
  • Skybot Scheduler β€” alert on failed Skybot jobs and fix them from the alert
  • GoAnywhere MFT β€” alert on failed GoAnywhere projects and run them again from the alert
  • Azure Monitor β€” two-way alert acknowledgement
  • Grafana & Prometheus Alertmanager β€” page your on-call team when a Grafana or Prometheus alert fires
  • ServiceNow β€” two-way ITSM incident escalation + write-back
  • Zendesk β€” two-way ticket escalation + write-back
  • Freshservice β€” two-way ticket escalation + write-back
  • Jira β€” page your on-call team when a Jira issue is created
  • SSO overview β€” let your team log in via your IdP
  • Inviting Users β€” set up the people who'll receive alerts
  • Using AI Helper β€” fastest path to a flow that uses these integrations