Alert Configuration: Slack and Email

What Triggers Alerts

VersionForge sends alerts when events require your attention. The following events are alertable:

| Event | Default Severity | Description | |-------|-----------------|-------------| | Sync failure | Critical | A sync pipeline failed at any stage (extraction, transform, load) | | Cross-check failure | Critical | Post-load reconciliation found a variance exceeding tolerance | | Credential expiry warning | Warning | An OAuth token expires within 7 days | | Credential failure | Critical | A health check detected invalid or revoked credentials | | Connection health change | Warning/Critical | A connection transitioned to degraded or down status | | Schema drift detected | Warning | Source system schema changed (new fields, removed fields, type changes) |

You can enable or disable alerts per event type in Settings > Alerts > Event Configuration.

Configuring Slack Alerts

1. Create a Slack webhook

   In your Slack workspace, go to Apps > Incoming Webhooks (or create a new Slack app with webhook permissions). Create a webhook URL pointed at the channel where you want VersionForge alerts to appear.

2. Add the webhook to VersionForge

   Navigate to Settings > Alerts > Channels and click Add Slack Channel. Enter:

   • Channel name -- A label for this channel in VersionForge (e.g., "FP&A Alerts").
   • Webhook URL -- The Slack webhook URL you created.
   • Severity filter -- Choose which severity levels this channel receives: All, Warning + Critical, or Critical only.

3. Test the channel

   Click Send Test Alert. A test message should appear in your Slack channel within a few seconds. If it does not arrive, verify the webhook URL and channel permissions.

Slack alerts include:

• Event type and severity badge
• Connection and sync profile name
• Timestamp
• A View Details link that opens the relevant page in VersionForge

Configuring Email Alerts

VersionForge supports two email delivery methods:

Option A: Resend API

If you use Resend for transactional email:

1. Navigate to Settings > Alerts > Email Configuration.
2. Select Resend as the provider.
3. Enter your Resend API key.
4. Set the From address (must be a verified domain in Resend).

Option B: SMTP

For self-managed SMTP:

1. Navigate to Settings > Alerts > Email Configuration.
2. Select SMTP as the provider.
3. Enter: Host, Port, Username, Password, and From address.
4. Toggle TLS on if your SMTP server requires it (recommended).

Adding Recipients

After configuring the email provider, add recipients:

1. Click Add Recipient under Settings > Alerts > Email Recipients.
2. Enter the email address.
3. Set the severity filter for this recipient.
4. Click Send Test Email to verify delivery.

Alert Severity Levels

| Level | Color | Used For | |-------|-------|----------| | Critical | Red | Sync failures, credential failures, connection down | | Warning | Amber | Credential expiry approaching, connection degraded, schema drift | | Info | Blue | Connection recovered, sync completed successfully (opt-in) |

Info-level alerts are disabled by default. Enable them in Settings > Alerts > Event Configuration if you want confirmation of successful syncs.

Alert Deduplication

VersionForge prevents alert fatigue with built-in deduplication rules:

• Same event, same connection -- If the same failure occurs on consecutive health checks or sync runs, only the first occurrence triggers an alert. A reminder is sent every 24 hours while the issue persists.
• Recovery clears the counter -- When an issue resolves (connection recovers, sync succeeds), the deduplication counter resets. A new failure after recovery triggers a fresh alert.
• Digest mode -- If more than 5 alerts would fire within a 10-minute window, VersionForge batches them into a single digest message listing all events.

Managing Alert Channels

View all configured channels (Slack and email) in Settings > Alerts > Channels. From this screen you can:

• Edit a channel's severity filter or webhook URL
• Disable a channel temporarily (useful during maintenance windows)
• Delete a channel permanently
• View delivery history -- See which alerts were sent to each channel and whether delivery succeeded