Alerts

Get notified when your flows fail or succeed. Alerts can be delivered via email, webhook, or Slack.

How It Works

When a flow execution completes, the alert system checks for active subscriptions matching the event type. Notifications are sent asynchronously (they don't block flow execution).

Channels

Channel	Target	Format
Email	Any email address	Subject line with flow name + plain text body with error details
Webhook	Any HTTPS URL	JSON POST with event type, flow details, error message, execution ID
Slack	Slack incoming webhook URL	Formatted Slack message with status emoji, flow name, and error details

Event Types

flow.failed — sent when a flow execution fails (any step error or timeout)
flow.succeeded — sent when a flow execution completes successfully

Managing Alerts

Navigate to Settings → Alerts in the admin panel to create, toggle, or remove alert subscriptions. Each subscription specifies a channel, target, and which event types to listen for.

API

# List alert subscriptions
GET /connect/v1/alerts
Authorization: Bearer <jwt>

# Create an alert subscription
POST /connect/v1/alerts
{
  "channel": "email",
  "target": "ops@example.com",
  "eventTypes": ["flow.failed"]
}

# Update (toggle active state)
PATCH /connect/v1/alerts/:id
{ "isActive": false }

# Delete
DELETE /connect/v1/alerts/:id

Permissions

alerts.view — view alert subscriptions (Admin, Manager, Viewer)
alerts.write — create and manage alert subscriptions (Admin, Manager)

Webhook Payload

When using the webhook channel, the following JSON payload is POST'd to your target URL:

{
  "event": "flow.failed",
  "timestamp": "2026-04-16T12:00:00.000Z",
  "flowId": "abc-123",
  "flowName": "Sync leads to CRM",
  "error": "Action connection not found",
  "executionId": "exec-456"
}

Tip: Set up a flow.failed alert to a Slack channel during initial setup. This catches misconfigured flows before they affect your data pipeline.