Email (IMAP) Monitoring

JAMS Incident Management can watch a mailbox over IMAP and fire a flow whenever a matching email lands. It's the right trigger when the system you care about already emails you β€” a monitoring tool, a backup job, a vendor's status notifications, a shared support inbox β€” and you want those emails turned into calls, SMS, push, or Teams pages with retries and escalation.

Plan availability: Email (IMAP) monitoring works on every plan, including Free. The alert channels it can trigger are plan-dependent (Voice starts on Starter; WhatsApp, email, push, Teams and Slack are on every plan). See Plans & Billing.

If you can already POST to a webhook, prefer that β€” it's faster and cleaner (see Getting started). Reach for email monitoring when the source can only email you.

How it works at a glance

  1. You give JAMS Incident Management read access to a mailbox (an email connection).
  2. A flow watches that mailbox on an interval and matches incoming mail against your criteria.
  3. A match fires the flow's recipients and escalation policy, exactly like any other trigger. Optionally, it can also take an action, such as submitting a JAMS Scheduler job.
  4. JAMS Incident Management deduplicates by message ID so the same email never pages twice.

Create the connection before, or during, the flow β€” your choice

There are two ways to set up the mailbox JAMS Incident Management reads from. They produce the same thing β€” a reusable, saved email connection β€” so pick based on how you work.

Option A β€” Create it ahead of time at Email Connections.

Build the connection as a standalone object first, then select it when you build flows. This is the better choice when several flows will monitor the same mailbox (for example, one flow for CRITICAL subjects and another for WARNING subjects on the same support inbox). One connection feeds many flows β€” you enter the credentials once.

Heads up: the Email Connections page is admin-only. If you don't see it, you don't have the admin role on this tenant.

Option B β€” Create it inline while building the flow.

In the flow builder, on the email-trigger step, click βž• Create New next to the connection picker. Fill in the same details, test, and save. The connection is saved and auto-selected for this flow β€” and it's available to pick from the dropdown in every future flow, just like one created in Option A.

Inline creation is available to anyone who can build flows, not just admins. So if you don't have access to the admin-only Email Connections page, you can still create the connection you need from inside the flow builder.

Which to use: if you'll monitor one mailbox from multiple flows, create a reusable connection up front (Option A) so the credentials live in one place. For a one-off flow, inline (Option B) is quicker β€” and the result is still reusable later.

Set up the connection

Whichever path you take, the fields are the same.

FieldWhat to enter
Connection NameA label you'll recognize later, e.g. Support Inbox Monitor.
Email ProviderMicrosoft 365 / Outlook, Google / Gmail, Yahoo Mail, or Other (Custom).
Email AddressThe mailbox to read.
App PasswordThe mailbox password β€” but see the app-password note below.
IMAP Host / PortAuto-filled for the known providers (993 is the standard secure IMAP port). For Other (Custom), enter your server's host and port.

App passwords (read this for Gmail, Yahoo, and MFA-protected Microsoft 365)

If the mailbox has multi-factor authentication / 2-step verification enabled, your normal password will not work over IMAP. You need an app password instead β€” a separate, single-purpose password your provider generates for older protocols like IMAP.

  • Gmail: an app password is required β€” Google does not allow IMAP with your normal password.
  • Yahoo: required when 2FA is on.
  • Microsoft 365 / Outlook: required when MFA is on.
  • Custom: use an app password if your provider has MFA/2FA enabled.

Generate the app password in your email provider's security settings and paste that into the App Password field β€” not your account login password.

Test before you save

Click πŸ”Œ Test Connection (the πŸ” Test Connection button in the inline flow-builder version). JAMS Incident Management opens a real IMAP session with the credentials you entered and reports success or the exact failure.

Why this matters: the Save button stays disabled until a test succeeds. A green test is the difference between "the flow is armed" and "the flow silently never sees a single email." Always get the green check before moving on.

If the test fails, the most common cause is using the account password instead of an app password β€” see above.

Per-flow conditions

The connection only grants access to the mailbox. Each flow then adds its own conditions, so different flows can react to different mail from the same inbox:

  • Conditions on the Subject, From, To / Cc or Body: contains, equals, starts with and more, combined with AND or OR. For example, Subject contains FAILED AND From equals alerts@example.com.
  • Values from the email. Pull out details such as a server or job name and use them in the alert, e.g. "{{JobName}} failed on {{Server}}".
  • Check this mailbox at least every… β€” from every minute up to hourly. Every 5 minutes is a good default; use 1 minute for time-critical alerts.

All of this is explained, with examples, in Email: Conditions & Values from the Email. An email flow can also do something when a matching email arrives, such as submit a JAMS Scheduler job or run a script. See Email: Taking Action Automatically.

Several flows on one mailbox

You can point as many flows as you like at the same mailbox. For example, one flow for CRITICAL alerts and another for anything from your backup system, both reading the same support inbox.

  • The mailbox is checked once for all of its flows, as often as the fastest of them asks. If one flow says every minute and another says every 15, the mailbox is checked every minute, and both flows look at every new email straight away.
  • Every flow sees every new email. If an email matches two flows, both fire.
  • "New" means arrived since the last check, not "unread". An email someone opened in Outlook before the check is still picked up.
  • The very first check of a mailbox looks at unread email from the last 24 hours. After that it carries on from where it left off, even after a restart.
  • Email older than 24 hours never raises an alert, even after an outage.

Read / unread: on an IMAP mailbox, emails that a flow acts on are marked as read. Other mail is left alone. Read status no longer decides what's checked, so this never hides an email from another flow. A Microsoft 365 connection never changes read status.

If a mailbox stops working, you'll know

A mailbox can stop working without anyone touching JAMS Incident Management: a password or app password is changed or revoked, Microsoft 365 needs someone to sign in again, or the mail server is down. When that happens:

  • The flow page and Email Connections show it. A red line names the mailbox, when it started failing and why, in plain words (e.g. "The mailbox rejected the sign-in. If its password or app password was changed or revoked, update the email connection."). A green line shows when it was last checked successfully.
  • Your tenant's admins are emailed once it has failed a few times in a row for at least 10 minutes. One email per outage, naming the mailbox, the reason and the flows affected. A single blip doesn't email anyone.
  • When it works again, admins get an all-clear email. Unread emails from the last 24 hours that arrived during the outage are picked up then, so they aren't lost.

Last checked on a flow now means the mailbox was actually read.

Deduplication β€” the same email never pages twice

Every email carries a unique Message-ID. JAMS Incident Management records the Message-ID of each email a flow acts on and never raises a second alert for it on that flow. So if the matching email sits in the inbox for an hour, it fires once, not sixty times. (For the rare email that arrives with no Message-ID, JAMS Incident Management builds a stable fingerprint from the message so dedup still holds.)

You don't configure this β€” it's always on.

After the trigger fires

Once an email matches, the flow behaves like any other: it pages your recipients on their chosen channels and escalates if nobody acknowledges. Set who gets paged, in what order, and how long each step waits in your escalation policy.

Troubleshooting quick hits

SymptomLikely causeFix
Test Connection failsUsing the account password instead of an app passwordGenerate an app password in your provider's security settings and use that.
Test fails for a custom serverWrong host/port, or IMAP not enabled on the mailboxConfirm the IMAP host/port with your mail admin; ensure IMAP access is turned on.
Flow never fires on a real emailA condition doesn't match that email (often an AND that should be an OR)Paste the email into Test with a sample email on the flow. It shows which condition failed. See Email: Conditions & Values from the Email.
Email arrived but no pageThe flow is inactive, its conditions don't match, or the mailbox isn't being checkedConfirm the flow is active, test the email against its conditions, and check the mailbox's status line on the flow.
A red "Not working" line on the flow or Email ConnectionsThe mailbox can't be checked; the line says whyUsually an expired or changed password / app password: update the connection. For Microsoft 365, reconnect it.
"Not being checked"Nothing has tried to check the mailbox recentlySave the flow to restart its monitoring. If it persists, contact support.
Can't find the Email Connections pageIt's admin-onlyCreate the connection inline in the flow builder instead, or ask an admin.