Webhooks

HTTP callbacks fired by Tree to external services when events occur.

Webhooks are HTTP callbacks Tree fires to a configured external URL when events occur in a workspace. They let other services react to Tree changes without polling. Webhooks are a Paid feature available on Paid and Team tiers.

What events fire webhooks

Webhooks can be configured to fire on:

  • Node state changes: locked to available, available to in-progress, in-progress to complete
  • Node creation, edit, or deletion
  • Edge creation, redirection, or deletion
  • Assignment changes (Team feature, see Assignments)
  • Comments (Team feature, see Comments)
  • Custom triggers via Automation rules

Each webhook subscription specifies which events fire it. Multiple webhooks can subscribe to the same event.

What a webhook payload contains

When a webhook fires, Tree sends an HTTP POST request to the configured URL with a JSON payload containing:

  • The event type that triggered the webhook
  • The affected node, edge, or project with current state
  • The previous state if applicable
  • The user who triggered the event (if any)
  • A timestamp

Receivers can use the payload to update external dashboards, trigger CI pipelines, sync with other tools, or run any other downstream logic.

Setup and security

Webhooks require:

  • A target URL that accepts POST requests
  • An optional signing secret for verifying the payload came from Tree
  • Per-project enablement to specify which projects fire the webhook

Tree retries failed webhook deliveries with exponential backoff and stops after a configurable number of attempts.

Tier availability

Webhooks are a Paid feature, available on Paid and Team. Free does not include webhooks.

LAST UPDATED · 2026-05-12