Since March 2021, GroupAlarm has allowed alarms to be triggered directly via an IMAP trigger. To increase the reliability of this interface and simplify management, we have now integrated the IMAP connection into the connection manager.

Previously, credentials for IMAP mailboxes were stored directly in the respective trigger. By moving them to the connection manager, we separate the connection data from the logic, which not only increases security but also simplifies the creation of multiple flows for the same mailbox.

By integrating into the connection manager, the status of your IMAP connection is continuously monitored. Should the connection to the mail server be interrupted – for example due to an expired password or server problems – this can be converted into an alarm or notification via the ‘Connection status changed’ trigger. This ensures that critical alarm paths do not fail unnoticed.

Changes at a glance

• Centralised management: Credentials are now only created once in the connection manager and can be used by multiple triggers.
• Status monitoring: The connection status is displayed directly in the manager, which significantly speeds up troubleshooting.
• New configurations: New IMAP connections can now only be created via the connection manager.

Recommendations for existing customers

Existing IMAP triggers will continue to work for now, but do not benefit from centralised monitoring. We therefore recommend that all users migrate their configured triggers promptly:

1. Create a new connection of type ‘IMAP’ in the connection manager.
2. Enter your server details and credentials there.
3. Open your existing IMAP triggers, replace the trigger with ‘IMAP connection’ and select the newly created IMAP profile in the ‘Connection’ field.
4. Save the configuration. The manually stored credentials in the trigger will be replaced.

Create an additional flow with the ‘Connection status changed’ trigger and define what should happen if a problem occurs with the selected IMAP connection (e.g. alarm or notification).

By making this change, you increase the operational reliability of your alerting chain and keep track of the status of your interfaces at all times.