Skip to content
Docs

Notifications and alerts

Get notified by email, Slack, or Microsoft Teams when jobs fail, find no files, or complete — and choose exactly what triggers an alert.

Last updated July 17, 2026

#How alerts work

Alerts are configured under Settings → Alerts. When a job run meets a condition you care about, FileAgent sends a notification to your configured channels, so problems find you instead of waiting in a log. Channels by plan: email on Pro and above; Slack and Microsoft Teams on Business Premium and Enterprise.

#Email alerts

Configure your mail (SMTP) settings and recipient addresses, then choose which events send mail. Use a team distribution list rather than one person so coverage survives vacations. Send a test from the alert settings to confirm delivery, and check spam filters once.

#Slack and Microsoft Teams

Slack and Teams alerts are delivered via incoming webhook URLs:

  • Slack — create an incoming webhook for the target channel (Slack app settings → Incoming Webhooks), then paste the URL into FileAgent's alert settings.
  • Teams — add an incoming webhook to the target channel, then paste the URL into FileAgent.
Treat webhook URLs like passwords — anyone with the URL can post to your channel. Available on Business Premium and Enterprise.

#What to alert on

You choose which run outcomes send a notification:

  • Failure or partial failure — the must-have for production. Covers full failures and runs where some files didn't make it.
  • No files found — useful when a job should always have work; a “no files” result then signals that an upstream producer stopped delivering.
  • Success — positive confirmation for business-critical deliveries where stakeholders want to see that the file arrived.
Alert on failure everywhere; add “no files” where silence would be a problem; reserve success for the handful of jobs someone is actually waiting on. Alert fatigue is real — if everything pings, nothing does.