Agent webhooks

floo watches for failed deploys and repeating runtime errors. When one fires, it bundles the context and POSTs a JSON event to a webhook URL you configure: an agent, an on-call bot, or an incident pipeline. floo detects and routes; remediation stays with the downstream agent or human. The dashboard calls this feature Error routing, the API path uses reparo, and floo events lists the events that fired. They are the same feature.

Turn it on

Error routing is off until you point it at a URL. Configure it per app on the dashboard under App → Alerts → Error routing, or with PUT /v1/apps/{app_id}/reparo/config over the HTTP API:

Setting	What it does	Default
Mode	`Webhook` routes detected events to your URL; `Off` disables detection	`Off`
Webhook URL	Where floo POSTs the enriched event. Must be `https://`	none
Signing secret	When set, floo signs each request so you can verify it came from floo	none
Error threshold	Repeats of the same runtime error before an event fires	`5`
Cooldown	Minutes before the same signature can fire again	`15`

There is no CLI command for this configuration. floo events list is the read-only view of what has already fired.

What triggers an event

runtime errors, repeated error conditions surfaced in logs crossing the configured threshold
failed deploys, a deploy that never goes live, rolled back, or exited non-zero

Events are grouped per app. Repeats of the same error roll up into one event, not one per log line.

What’s in the payload

floo sends a POST with a JSON body and these headers:

Header	Value
`Content-Type`	`application/json`
`X-Floo-Event`	`reparo.error_detected`
`X-Floo-App`	The app name
`X-Floo-Signature`	`sha256=` and the hex HMAC-SHA256 of the raw body, keyed with your signing secret. Sent only when a secret is set.

{
  "event": "reparo.error_detected",
  "event_id": "5c1f0a52-8f3e-4b8e-9d0a-2b7c6a1e9f10",
  "timestamp": "2026-10-27T18:04:11.532Z",
  "app": {
    "id": "fb6e7446-2d02-4307-b05e-b00120620da5",
    "name": "my-app",
    "url": "https://my-app.getfloo.app"
  },
  "error": {
    "message": "TypeError: Cannot read properties of undefined (reading 'id')",
    "fingerprint": "a41c9e0d7b",
    "stack_trace": "TypeError: Cannot read properties of undefined ..."
  },
  "suggestion": null,
  "context": {
    "recent_deploy": {
      "id": "0b7e3d1c-...",
      "environment": "prod",
      "status": "live",
      "commit_sha": "abc1234...",
      "repo": "acme/my-app",
      "github_ref": "refs/tags/v1.4.0",
      "triggered_by": "github_release",
      "created_at": "2026-10-27T17:58:02Z",
      "url": "https://my-app.getfloo.app"
    },
    "recent_logs": [
      {
        "timestamp": "2026-10-27T18:03:58.120Z",
        "severity": "ERROR",
        "service": "web",
        "message": "TypeError: Cannot read properties of undefined (reading 'id')"
      }
    ],
    "services": [{ "name": "web", "type": "web", "status": "running" }],
    "managed_resources": [{ "name": "db", "type": "postgres" }],
    "github": { "repo": "acme/my-app", "branch": "main", "installation_id": 12345678 },
    "dashboard_url": "https://app.getfloo.com/apps/fb6e7446-...",
    "logs_url": "https://app.getfloo.com/apps/fb6e7446-.../logs"
  },
  "reparo": {
    "event_url": "https://app.getfloo.com/apps/fb6e7446-.../reparo/events/5c1f0a52-..."
  }
}

recent_deploy is the deploy whose code produced the error: the failed deploy for a failed-deploy event, or, for a runtime error, the deploy that was live in the environment that logged it when the event fired. It is null when that environment no longer exists or has nothing live. recent_logs holds up to 20 of the error’s newest log lines, oldest first, from that environment (every environment when recent_deploy is null) and the 5 minutes before the event. Secrets are redacted before floo stores a line. A failed-deploy event has none; its message is the last line of the build log. managed_resources lists the app’s Postgres, Redis, and Storage by name and type, never connection details. suggestion is a short fix hint when floo recognizes the error, otherwise null. github is null when the app has no connected repo.

Verify the signature

Compute the HMAC over the raw request body, before any JSON parsing, and compare in constant time.

import crypto from "node:crypto";

export function isFromFloo(rawBody, signatureHeader, secret) {
  const expected =
    "sha256=" + crypto.createHmac("sha256", secret).update(rawBody).digest("hex");
  const a = Buffer.from(expected);
  const b = Buffer.from(signatureHeader ?? "");
  return a.length === b.length && crypto.timingSafeEqual(a, b);
}

import hashlib
import hmac


def is_from_floo(raw_body: bytes, signature_header: str | None, secret: str) -> bool:
    expected = "sha256=" + hmac.new(secret.encode(), raw_body, hashlib.sha256).hexdigest()
    return hmac.compare_digest(expected, signature_header or "")

Respond with any 2xx status to acknowledge the event.

Event lifecycle

Each event’s status shows whether your webhook received it:

triggered: detected and queued for delivery
in_progress: delivery in flight or being retried
succeeded: the webhook responded 2xx
failed: delivery failed permanently after retries
skipped: matched but suppressed (cooldown or rate limit)

List events from the CLI:

floo events list --app my-app
floo events list --app my-app --status triggered

What it does not do

floo does not generate or merge code fixes. Your agent or on-call workflow owns the fix.

Recommended loop

Watch deploy and runtime health.
Let floo create the event and POST it to your webhook.
Your agent or workflow reads the payload, inspects logs and releases, and decides.
Roll back with floo deploys rollback or ship a fix.

Logs and debugging

Runtime logs and deploy history for inspecting the incident further.

Releases and rollbacks

Recover quickly when the right move is shifting traffic back.

Get started

Build with your stack

Deploy from your agent

Configure your app

Ship and release

Data

Domains and networking

App users and access

Operate

Team and billing

For agents

Agent webhooks

Turn it on

What triggers an event

What’s in the payload

Verify the signature

Event lifecycle

What it does not do

Recommended loop

Logs and debugging

Releases and rollbacks

​Turn it on

​What triggers an event

​What’s in the payload

​Verify the signature

​Event lifecycle

​What it does not do

​Recommended loop

Logs and debugging

Releases and rollbacks

Turn it on

What triggers an event

What’s in the payload

Verify the signature

Event lifecycle

What it does not do

Recommended loop