Recurring nodes

Nodes that auto-spawn copies of themselves on a configurable schedule.

A recurring node is a node that automatically spawns copies of itself on a configurable schedule. Recurring nodes are useful for work that happens on a repeating cadence: weekly reviews, monthly reports, quarterly planning. Recurring nodes are a Paid feature available on Paid and Team tiers.

How recurring nodes work

When a node is configured as recurring:

  • A schedule is set (daily, weekly, monthly, quarterly, or custom interval)
  • The original node becomes the template for future copies
  • At each scheduled interval, Tree creates a new copy of the node with the same structure, description, and metadata
  • Each copy has its own state and can be completed independently

The original recurring node continues to live in the project as the template. The copies are new nodes, each with their own lifecycle.

What gets copied

When a recurring node spawns a copy, the copy includes:

  • Title and description
  • Custom field values (with optional date-based variations)
  • Tags and labels
  • Assignments (on Team tiers, see Assignments)
  • Dependencies on other nodes if the template had them

The copy does not inherit:

  • Status: each copy starts fresh
  • Comments and activity history
  • Completion or progress from prior copies

Configuration options

Recurring nodes can be configured with:

  • Skip intervals: spawn every other week, every third month, etc.
  • End dates: stop spawning after a specific date
  • Maximum copies: stop spawning after N copies have been created
  • Conditional spawning: only spawn if certain criteria are met (Paid feature, requires Automation rules)

Tier availability

Recurring nodes are a Paid feature, available on Paid and Team. Free does not include recurring nodes.

LAST UPDATED · 2026-05-12