Webhooks

Outbound webhooks — where AgenFleet pushes events to your systems in real time — are on the active engineering roadmap. This page documents the planned event model and the alternatives available today.

Planned webhook events

When outbound webhooks ship, they will cover the following event types:

Event	When it fires
`cron.completed`	A cron job finished executing
`cron.delivered`	Cron output was successfully delivered to a notification channel
`cron.failed`	Cron delivery failed after all retries
`agent.status_changed`	An agent transitions between online / degraded / offline
`agent.budget_alert`	An agent reaches its `alertThreshold`
`agent.budget_exhausted`	An agent’s daily or monthly budget is depleted

Planned payload format

All webhook payloads will share a common envelope:

{
  "id": "evt-uuid-...",
  "event": "cron.completed",
  "timestamp": "2026-03-17T08:00:44Z",
  "data": { ... }
}

All requests will be signed with an HMAC-SHA256 signature for verification, and will include a timestamp header for replay attack protection. Always verify signatures and reject requests where the timestamp is more than 5 minutes old.

Current alternatives

For cron job output delivery: Configure delivery targets directly on each cron job — Telegram, Slack, email, or a raw URL POST from the cron system.

For agent status monitoring: Poll GET /api/agents on a schedule. The status field on each agent reflects its current health.

For cost and activity data: Use the Cost & Metrics API to retrieve usage, cost breakdowns, and activity log data on demand or on a polling schedule.

For n8n users: You can trigger n8n workflows directly from cron job delivery targets today using the webhook URL as the delivery destination.

Stay updated

Webhook availability will be announced via the changelog and in the portal. If outbound webhooks are a blocker for your integration, contact support@agenfleet.ai to discuss your use case and timeline.