Email Notifications

Simply register an email address to receive email notifications when incidents occur or recover.

No external API key is required. Prepare an email address that can receive both the verification email and notifications from [email protected].

1. In the dashboard, open Settings > Integrations, then select Configure for Email
2. Enter a recognizable Name and the destination under To (email address)
3. Select Add
4. Open the link in the verification email within 24 hours

Unverified Email channels are not selected for normal notifications. If the verification email does not arrive, use the resend action in the Email configuration list.

Notification emails are sent from the following address:

Manako <[email protected]>

• Subject: [Manako] {Monitor Name} is DOWN
• Body: Monitor name, incident ID, monitored URL

• Subject: [Manako] {Monitor Name} is back UP
• Body: Monitor name, incident ID

Maintenance start and end events also produce email. The start message includes the affected monitors and scheduled end time.

• The verification email or notification does not arrive: Check spam filtering and allow-list settings. If the channel is marked Unverified, resend the verification email.
• A test arrives but normal notifications do not: When a monitor has channel links, only linked channels that are active and verified are used. If links exist but all are disabled, Manako does not fall back to team-wide channels.
• Notifications stop during rapid state changes: After more than three state changes for the same monitor within 10 minutes, the flap guard suppresses subsequent notifications.
• Notifications appear duplicated: incident.created and incident.resolved are separate events. A retry is skipped when a sent record already exists for the same incident, channel, and event type, and a database UNIQUE constraint also prevents duplicate records. Failed or pending records are eligible for retry.

Test sends a real test email and has a 60-second cooldown after success. A failure on one channel does not stop the remaining channels, but the queue retries when every selected channel fails.

The flap guard and incident-level sent check apply to incident notifications. Maintenance notifications bypass both controls and go to active, verified team channels.