Notifications

Notifications serve two purposes on AgenFleet: delivering cron job output and receiving platform alerts (agent down, budget exceeded, delivery failure). Both use the same connected channels.

---

Connecting channels

Go to Settings → Notifications to manage your connected channels.

---

Telegram

Telegram is the recommended channel for most users — it’s fast, supports rich Markdown formatting, and works on mobile.

1. Open the Telegram connection page

   Go to Settings → Notifications → Connect Telegram.

2. Start the bot

   Click the link to open the AgenFleet Telegram bot, then send /start. This registers your account.

3. Confirm the connection

   Return to the portal — your Telegram account should show as connected within a few seconds.

4. Test it

   Click Send Test Message. You should receive a test message from the bot in Telegram.

Sending to a group or channel:

To deliver cron output to a Telegram group instead of your personal DM, add the AgenFleet bot to the group and grant it message permissions. Then select the group as the delivery target when configuring the cron job.

Note

Telegram messages have a 4,096-character limit. Longer agent output is automatically split into multiple consecutive messages.

---

Slack

1. Open the Slack connection page

   Go to Settings → Notifications → Connect Slack.

2. Authorize the app

   Click Add to Slack. You’ll be redirected to Slack’s OAuth flow — select your workspace and approve the permissions.

3. Choose a default channel

   Select the channel where notifications will be posted by default. This can be overridden per cron job.

4. Test it

   Click Send Test Message to verify the connection.

Channel vs. DM delivery:

When configuring a cron job’s delivery target, you can choose between:

• A public or private channel (e.g., #agent-briefings)
• A direct message to a specific team member

The Slack app must be invited to any private channel before it can post there.

---

Email

Email delivery requires no OAuth flow — just enter the recipient address when configuring a cron job’s delivery.

Email format:

• Subject: [AgenFleet] {Job Name} — {Date}
• Body: Agent output as plain text
• From: notifications@agenfleet.ai

Tip

Add notifications@agenfleet.ai to your contacts or allowlist to prevent briefings from landing in spam.

Multiple recipients: Enter a comma-separated list of email addresses in the delivery configuration to send to multiple people simultaneously.

---

Webhook

Webhooks deliver cron job output as a JSON POST to any URL you control. Use this to trigger n8n workflows, feed data into dashboards, or integrate with your own systems.

Payload format:

{
  "event": "cron.completed",
  "jobId": "daily-market-briefing",
  "agentId": "nova-research",
  "agentName": "Nova",
  "runAt": "2026-03-17T08:00:12Z",
  "output": "## Market Briefing — March 17...",
  "tokensUsed": 2104,
  "status": "success"
}

Configuring a webhook:

1. Go to Settings → Notifications → Add Webhook
2. Enter the destination URL
3. Test the connection — AgenFleet will send a test POST to verify reachability

Note

Webhook signature verification (HMAC-SHA256) is on the engineering roadmap. Until it ships, restrict your webhook endpoint to the AgenFleet IP range or require a shared secret as a query parameter that you validate on your end.

---

Alert notifications

Beyond cron job delivery, AgenFleet uses your connected channels to send operational alerts:

Alert	Trigger	Severity
Agent offline	Heartbeat missed >5 min	High
Budget threshold reached	Agent hits alertThreshold	Medium
Budget exhausted	Daily or monthly limit hit	High
Cron delivery failed	Two consecutive delivery failures	Medium
Agent degraded	Elevated latency or repeated errors	Low

Alerts are sent to your default notification channel — the first connected channel listed in Settings → Notifications. To route alerts to a specific channel (separate from cron delivery), configure the Alert Channel setting separately.

---

Managing multiple channels

You can connect multiple channels simultaneously. When configuring each cron job, you choose which channel(s) to deliver to. This lets you:

• Send executive briefings to email
• Send operational alerts to a team Slack channel
• Send personal monitoring to Telegram
• Feed raw output to a webhook for downstream processing

There is no limit on the number of connected channels.

---

Disconnecting a channel

Go to Settings → Notifications → click Disconnect next to the channel. Any cron jobs still configured to deliver to that channel will fail on the next run and generate an alert. Update those jobs to use a different delivery target before disconnecting.