Back to JAMS IMES
NHelp Center

Integrations Overview

An integration is a connection between JAMS IMES and an external system you already use. Some integrations send signals INTO JAMS IMES (so your alerts know when something fails); others let JAMS IMES 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.
JAMS SchedulerReceive job-failure alerts from JAMS. Also allows acknowledging the alert by saying "release" or "cancel" on the voice call.Integrations → JAMS.

Outbound — what JAMS IMES uses to deliver

JAMS IMES always sends voice, SMS, and email. The infrastructure behind those is dual-provider with automatic failover (Twilio + Azure Communication Services), but it's invisible to users — you don't configure providers per-flow.

What you DO configure: per-tenant email transports if you want emails from your domain rather than JAMS IMES'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 IMES's default sender (alerts@jamssoftware.com). Fine for most teams.

Authentication — SSO

Single Sign-On (SSO) lets your team log in via your existing identity provider instead of password. JAMS IMES 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 IMES 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 run JAMS Scheduler → JAMS integration. Bidirectional — you can release/cancel jobs from voice ack.

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 connections create their own managed flow on save (one connection = one flow, by design — the flow's recipients/channels define how JAMS 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