Task automations

A task automation is one studio’s configuration for one trigger type: whether it is on, its threshold, who gets the task, and optionally a flow, a tree of action nodes that runs when the trigger fires. This module serves and saves that configuration and contains the flow executor. Source: backend/apps/core-api/src/modules/task-automations/. The matching side lives in Tasks engine. The rows a flow writes are served by Inbox.

Mounting and auth

taskAutomationsRouter(ctx) is mounted in modules/index.ts at /v1/web/task-automations behind serviceAuth (HMAC service auth), webUserContext(ctx.prisma) and webLimiter. The routes file adds no requireRole or coach access guard. Any authenticated web lane caller of the studio can read and change the automations. Every query is scoped by req.auth.studioId. A missing studio on req.auth returns UNAUTHORIZED (401). Responses use the standard envelope. A Zod failure returns VALIDATION (422) with the issues in details. See API overview.

Storage

Model	Purpose
`TaskAutomation`	One row per `(studioId, type)`. Holds `enabled`, `thresholdValue`, `thresholdUnit`, `thresholdByFrequency`, `assigneeMode`, `assigneeCoachId`, `assigneeCoachIds`, `notify`, `notifyTitle`, `notifyBody`, `planIds` and the `flow` JSON
`TaskAutomationTask`	Legacy task blocks of a trigger, unique on `(automationId, ordinal)`. Holds a threshold, assignee, `name`, `notify`, `notifyBody`, `formTypes`, `formIds`
`AutomationFlowRun`	One run of a flow for one entity, unique on `(studioId, type, entityKey)`. `status` is `RUNNING`, `WAITING`, `DONE` or `FAILED`
`FlowNodeExecution`	One row per executed effect node of a run, unique on `(runId, nodeId)`, with the node’s `result` JSON

A studio with no row for a trigger gets the catalogue default from AUTOMATION_DEFAULTS.

Triggers

TASK_TRIGGER_TYPES lists 19 values. AUTOMATION_DEFAULTS holds 18 of them. FORM_FILLED_OVERDUE is in the type list but not in the catalogue, so GET never returns it and the generator never evaluates it.

Type	Default on	Default threshold	Unit
`FORM_FILLED`	no	0	hours
`FORM_SENT`	no	0	hours
`FORM_FEEDBACK_SENT`	no	0	hours
`FORM_RATING_BELOW`	no	3	score
`FORM_RESPONSE`	yes	2	hours
`INACTIVE`	yes	5	days
`NO_WORKOUT`	yes	4	days
`PLAN_EXPIRING`	no	3	days
`TECHNIQUE_VIDEO`	yes	12	hours
`NEW_CLIENT_IN_PLAN`	no	0	days
`SUBSCRIPTION_ASSIGNED`	no	0	minutes
`MILESTONE`	no	0	days
`CALORIE_UNDER`	no	20	percent
`CALORIE_OVER`	no	20	percent
`AEROBIC_UNDER`	no	20	percent
`PAUSED_DURATION`	no	7	days
`TRAINING_PLAN_STALE`	no	14	days
`NUTRITION_PLAN_STALE`	no	14	days

INACTIVE and MILESTONE default notify to true. Every other trigger defaults it to false. The rule each trigger matches on is documented in Tasks engine.

Endpoints

`GET /v1/web/task-automations`

Returns one entry per catalogue trigger, merged with the studio’s stored rows. Auth: web lane, any role. No parameters. Response: data.items is an array in catalogue order. Each item:

string

The trigger type.

string

The built-in task title from CONTENT in tasks/task-content.ts, used when a task has no name.

boolean

Stored value or the catalogue default.

number

Stored value or the catalogue default.

string

minutes, hours, days, percent or score.

string

OWNER, RESPONSIBLE, SPECIFIC or UNASSIGNED. Defaults to RESPONSIBLE.

string or null

Legacy single assignee.

string[]

Falls back to a one item list built from assigneeCoachId.

boolean

Whether the legacy task also sends the trainee a message.

string or null

Stored as given.

string or null

The trainee message text.

string[]

Product ids the trigger is limited to.

object

Days per weekly workout band, keys 3 to 7, normalised by normalizeFrequencyThresholds. Missing bands fall back to the stored thresholdValue, or to the defaults 5, 4, 3, 3, 2 when there is no row. Values are clamped to 1 to 60.

object[]

The stored TaskAutomationTask rows sorted by ordinal, returned as full rows (so they also carry id, automationId, createdAt and updatedAt). When there are none, one synthesised task at ordinal 0 built from the parent row, with formTypes set to all four form types and formIds empty.

object

The stored flow when there is one. Otherwise a flow lifted from the stored task blocks with legacyTasksToFlow, or the default flow with a single task node when the trigger has no blocks.

{
  "ok": true,
  "data": {
    "items": [
      {
        "tasks": [
          {
            "ordinal": 0,
            "thresholdValue": 5,
            "thresholdUnit": "days",
            "assigneeMode": "RESPONSIBLE",
            "assigneeCoachIds": [],
            "name": null,
            "notify": true,
            "notifyBody": null,
            "formTypes": ["INTAKE", "CHECK_IN", "ONE_TIME", "PDF_SIGNATURE"],
            "formIds": []
          }
        ],
        "flow": {
          "schemaVersion": 1,
          "trigger": {
            "time": 5,
            "unit": "days",
            "pct": 20,
            "score": 3,
            "programs": [],
            "formTypes": ["INTAKE", "CHECK_IN", "ONE_TIME", "PDF_SIGNATURE"],
            "formIds": []
          },
          "steps": [
            { "id": "nmg1abc0", "kind": "task", "assign": "none", "members": [], "name": "" }
          ]
        },
        "type": "INACTIVE",
        "defaultTitle": "לא נכנס/ה לאפליקציה",
        "enabled": true,
        "thresholdValue": 5,
        "thresholdUnit": "days",
        "assigneeMode": "RESPONSIBLE",
        "assigneeCoachId": null,
        "assigneeCoachIds": [],
        "notify": true,
        "notifyTitle": null,
        "notifyBody": null,
        "planIds": [],
        "thresholdByFrequency": { "3": 5, "4": 4, "5": 3, "6": 3, "7": 2 }
      }
    ]
  },
  "requestId": "req_123"
}

A synthesised flow gets fresh node ids on every read, because legacyTasksToFlow and defaultFlow generate ids at call time. Ids become stable once a flow is saved.

Errors: UNAUTHORIZED (401).

`PATCH /v1/web/task-automations`

Upserts the automation for one trigger type and returns the full list again. Auth: web lane, any role.

string

required

One of TASK_TRIGGER_TYPES.

boolean

Turns the trigger on or off.

integer

Non negative, coerced from a string.

string

minutes, hours, days, percent or score.

string

OWNER, RESPONSIBLE, SPECIFIC or UNASSIGNED.

string or null

Legacy single assignee. Ignored when assigneeCoachIds is sent, in which case the first id is stored.

string[]

Coach ids.

boolean

Send the trainee a message when a legacy task is created.

string or null

Stored on the row.

string or null

Message text. The token {שם פרטי} is replaced with the trainee’s first name at send time.

string[]

Product ids.

object

Record with keys 3, 4, 5, 6, 7 and integer values from 1 to 60.

object[]

1 to 5 legacy task blocks. Replaces the whole list. The fields of one block are in the table below.

object

The node tree. See Flow schema. It is parsed with flowBody and then checked by validateFlow.

Fields of one entry in tasks (automationTaskBody):

Field	Type	Default	Notes
`thresholdValue`	integer	0	Non negative
`thresholdUnit`	string	`days`	`minutes`, `hours`, `days`, `percent` or `score`
`assigneeMode`	string	`RESPONSIBLE`	`OWNER`, `RESPONSIBLE`, `SPECIFIC` or `UNASSIGNED`
`assigneeCoachIds`	string[]	empty	Coach ids
`name`	string or null		Task title, trimmed, up to 120 characters
`notify`	boolean	false	Send the trainee message
`notifyBody`	string or null		Trimmed. No length limit in the schema
`formTypes`	string[]	all four	Any of `INTAKE`, `CHECK_IN`, `ONE_TIME`, `PDF_SIGNATURE`
`formIds`	string[]	empty	Up to 500 form template ids

What the service does:

When flow is sent, flowTriggerColumns projects the flow trigger onto the legacy columns, overriding whatever the body sent for them. A percent trigger stores flow.trigger.pct, a score trigger stores flow.trigger.score, and every other trigger stores flow.trigger.time and flow.trigger.unit. planIds becomes flow.trigger.programs. The matchers read these columns.
The repository upserts the row in a transaction. On create, the catalogue threshold is the base. When tasks is sent, task 0 is mirrored onto the parent row (threshold, assignee, notify, notifyBody), the existing blocks are deleted, and the new ones are inserted with their array index as ordinal.
When tasks is sent, open tasks are brought in line per ordinal. If a block’s name changed, renameOpenTasks sets the new title on that ordinal’s OPEN and SNOOZED automatic rows. If a block’s assignee changed, resyncOpenTasks reassigns them: UNASSIGNED clears owners, SPECIFIC sets the given ids, OWNER sets every active HEAD_COACH plus the given ids, and RESPONSIBLE sets each trainee’s trainers plus the given ids.
When tasks is not sent but assigneeMode or assigneeCoachIds is, ordinal 0 rows are reassigned from the saved row.

No push, WhatsApp message or job is sent by a save. A newly enabled trigger is picked up by the next hourly sweep or the next event. Response: the same shape as GET, read after the write. Errors: VALIDATION (422) for schema failures, including these validateFlow messages:

flow has N nodes; the limit is 60
conditions nest deeper than 5 levels
node ids must be unique
a create-task action needs at least one staff member
a condition needs exactly one fallback branch
the fallback branch must be last
webhook url must be https and public

UNAUTHORIZED (401) without a studio.

`GET /v1/web/task-automations/wa-templates`

Lists the studio’s own approved WhatsApp templates from its connected SmartSend account. The builder’s WhatsApp node uses it for the studio template picker. Auth: web lane, any role. No parameters. The handler reads the SmartSend key from Studio.settings.smartsend.apiKey and calls ctx.smartsend.listTemplates. Response: when no key is stored, connected is false and templates is empty. This is a normal 200 answer. Otherwise each template row has id (the template name that the send call expects) and value (a display label).

{
  "ok": true,
  "data": {
    "connected": true,
    "templates": [{ "id": "weekly_checkin", "value": "weekly_checkin (he)" }]
  },
  "requestId": "req_123"
}

Errors: SERVICE_UNAVAILABLE (503) smartsend is not answering when the SmartSend call fails. UNAUTHORIZED (401) missing web user context.

`GET /v1/web/task-automations/wa-templates/params`

Returns the parameters of one studio template, in send order. Auth: web lane, any role.

string

required

Template name, trimmed.

string

Optional language code, trimmed.

Response:

{
  "ok": true,
  "data": {
    "params": [{ "name": "1", "label": "First name", "type": "text" }]
  },
  "requestId": "req_123"
}

Each row has name, label (falls back to name) and type when SmartSend returns one. Errors: BAD_REQUEST (400) templateName is required. BAD_REQUEST (400) smartsend is not connected when the studio has no key. SERVICE_UNAVAILABLE (503) smartsend is not answering. UNAUTHORIZED (401).

Flow schema

flow.schema.ts owns the wire shape. FLOW_SCHEMA_VERSION is 1.

{
  "schemaVersion": 1,
  "trigger": {
    "time": 2,
    "unit": "days",
    "pct": 20,
    "score": 3,
    "programs": [],
    "formTypes": ["CHECK_IN"],
    "formIds": []
  },
  "steps": [
    { "id": "n1", "kind": "task", "assign": "coach", "members": [], "name": "Call the trainee" },
    { "id": "n2", "kind": "wait", "time": 1, "unit": "days" },
    {
      "id": "n3",
      "kind": "paths",
      "branches": [
        {
          "id": "b1",
          "label": "Came back",
          "fallback": false,
          "rule": { "field": "loggedSince", "op": "eq", "value": "yes", "fieldName": "" },
          "steps": []
        },
        {
          "id": "b2",
          "label": "Everyone else",
          "fallback": true,
          "rule": { "field": "program", "op": "eq", "value": "", "fieldName": "" },
          "steps": [{ "id": "n4", "kind": "push", "msg": "We miss you {שם פרטי}" }]
        }
      ]
    }
  ]
}

Trigger

Field	Type	Default	Limits
`time`	integer	0	0 to 10000
`unit`	`minutes`, `hours`, `days`	`days`
`pct`	integer	20	1 to 500
`score`	integer	3	2 to 10
`programs`	string[]	empty	up to 100 product ids
`formTypes`	string[]	not set	`INTAKE`, `CHECK_IN`, `ONE_TIME`, `PDF_SIGNATURE`
`formIds`	string[]	not set	up to 500

flowFormScope(trigger) returns all four form types and no ids when formTypes is not an array. feedbackFormKinds(trigger) narrows that to CHECK_IN and INTAKE for the feedback trigger.

Node kinds

Every node has an id (trimmed string, 1 to 40 characters) and a kind.

Kind	Fields	Effect at run time
`task`	`assign` (`none`, `coach`, `specific`, `manager`, `all`, default `none`), `members` (up to 20 coach ids), `name` (up to 120)	Writes an `InboxItem`
`push`	`msg` (up to 1000)	Sends a push to the trainee
`wa`	`mode` (`template` or `free`), `source` (`perform` or `studio`), `template`, `studioTemplate`, `studioParams` (up to 20 `name` and `value` pairs), `msg` (up to 1000), `openChat` (default true)	Sends a WhatsApp message through SmartSend
`webhook`	`label` (up to 120), `url` (up to 2048)	Queues an HTTP POST
`content`	`contentId`	Unlocks a content item for the trainee
`wait`	`time` (1 to 10000), `unit` (`minutes`, `hours`, `days`)	Parks the run
`paths`	`branches` (2 to 7)	Chooses branches by rule

A webhook url may be empty (the node saves but does nothing). A non empty URL must be https and must not point at a private host: localhost, 127., 0., 10., 192.168., 169.254., 172.16 to 172.31, an IPv6 literal, or a .local or .internal name. assign maps to the task assignee mode through FLOW_ASSIGN_TO_MODE: none to UNASSIGNED, coach to RESPONSIBLE, specific to SPECIFIC, manager to OWNER, and all to SPECIFIC with no ids.

Branches and rules

A branch has id, label (up to 60), fallback, a rule and its own steps. A rule has field, op (gt, lt, eq), value (up to 200), fieldName (up to 120, used by formField) and an optional filter record (used by trainee).

`field`	How `evaluateRule` decides
`program`	`Client.productId` equals the value, or the trimmed `Client.planName` equals it
`coach`	The value is one of the trainee’s trainer ids (primary coach or an active assignment), or equals one of their names
`formStatus`	The trainee’s newest `FormAssignment` is `COMPLETED`, compared with the value `filled` or `notFilled`. The Hebrew literal `מולא` is also accepted as filled
`daysSinceLogin`	Days since `Client.lastCheckInAt` compared with the numeric value using `op`. Never logged in counts as infinitely many days. `eq` compares whole days
`formField`	The newest `FormResponse` answer for the field whose label equals or contains `fieldName`, read as a number and compared with `op`
`loggedSince`	Whether `lastCheckInAt` is after the run’s trigger time, compared with `yes` or `no`. The Hebrew `כן` is accepted as yes
`trainee`	One rule of the trainee board’s advanced filter (`filterRule` and `ruleConditions` from the clients module), counted against this trainee

For every field except trainee, an empty value is always true, and a non empty one is false when the run has no client. A trainee rule that does not parse, or that the filter engine turns into no conditions, is true. Otherwise it is false without a client.

Structural limits

validateFlow enforces what Zod cannot express per node:

At most MAX_FLOW_NODES = 60 nodes, counting nodes inside branches.
Conditions nest at most MAX_CONDITION_DEPTH = 5 levels.
At most MAX_BRANCHES_PER_CONDITION = 6 rule branches plus the fallback.
Node ids and branch ids are unique across the whole flow.
A task node with assign specific needs at least one member.
Each paths node has exactly one fallback branch, and it is the last branch.

Legacy conversion

legacyTasksToFlow lifts stored task blocks into a flow: blocks are sorted by delay, the first block’s delay becomes the trigger timing, the gap to each later block becomes a wait node, each block becomes a task node, and a block with notify on and a message also adds a push node. SPECIFIC with no ids becomes all. Percent and score triggers put their number on the trigger and add no waits. defaultFlow is a single unassigned task node. resolveStoredFlow returns the stored flow when it parses, else the lifted or default one.

Flow runtime

flow-runtime.ts executes flows. One AutomationFlowRun row exists per (studioId, type, entityKey), created once. An entity that ever ran a trigger’s flow never runs it again.

How a run starts

startFlowRuns(ctx, args, deps) creates one run per seed. A unique violation (P2002) counts as skipped. The run’s context stores triggeredAt, a snapshot of the flow, the seed metadata, and the client name when given. With startDelayMs above 0 the run is created WAITING with resumeAt set and a delayed job is queued. Otherwise it is created RUNNING and advanced inline, in the calling request or job.

Starter	Trigger	Entity key	Notes
Task generator sweep (`flowRunner` in `workers/task-scheduler.ts`)	Every sweep trigger that has a stored flow	The legacy `autoKey`, for example `INACTIVE:<clientId>` or `TECHNIQUE_VIDEO:<videoId>`	Hourly. Only entities with no existing legacy key are seeded
`startFormFilledFlowRuns`	`FORM_FILLED`	`FORM_FILLED:<formResponseId>`	Needs the trigger enabled and a stored flow that parses. Does not check the flow’s form scope
`startFormRatingBelowFlowRuns`	`FORM_RATING_BELOW`	`FORM_RATING_BELOW:<formResponseId>`	Checks the stored task blocks’ form scope when any exist, then needs a rating below the parent `thresholdValue`
`startFormSentFlowRuns`	`FORM_SENT`	`FORM_SENT:<assignmentId>`	Needs the trigger enabled and a stored flow. Does not check the form scope
`startFormFeedbackSentFlowRuns`	`FORM_FEEDBACK_SENT`	`FORM_FEEDBACK_SENT:<formResponseId>`	The form type must be in `feedbackFormKinds(flow.trigger)`
`startSubscriptionAssignedRuns`	`SUBSCRIPTION_ASSIGNED`	`SUBSCRIPTION_ASSIGNED:<subscriptionId>`	Works without a stored flow. Starts after the trigger delay
`startNewClientInPlanRuns`	`NEW_CLIENT_IN_PLAN`	`NEW_CLIENT_IN_PLAN:<clientId>`	Works without a stored flow. First subscription only

The four form starters return true when the flow owned the event, including the cases where the flow exists but the form was out of scope or no rating was low. The caller then skips the legacy task writer.

How a run advances

advanceRun(ctx, runId, deps) walks the run’s position, a stack of frames. A frame is a loc (the chain of branch ids from the root) and an index (the next node in that steps list).

Entry guard. Only a RUNNING run, or a WAITING run whose resumeAt has passed, proceeds. A duplicate job returns at once. If the studio has deletedAt set, the run is marked FAILED with error studio deleted.
Current flow. The flow is re-read from the TaskAutomation row on every advance, so an edit applies to the remaining steps. When the row has no parseable flow, the snapshot in the run context is used, then the caller’s fallback. With none, the run is closed as DONE with a note. Disabling the trigger does not stop runs that already started.
Deleted branch. When a frame’s branch id no longer exists, the run closes as DONE with the note flow structure changed; remaining steps skipped.
Wait. The position is saved at the next node, the run becomes WAITING with resumeAt, and a delayed job is queued on flow-run. A failed enqueue is logged and left to the sweeper.
Paths. Every non fallback branch whose rule is true runs, in builder order. The fallback runs only when none matched, and only when it has steps.
Effects. executeNode inserts the FlowNodeExecution row before running the effect. A unique violation means the node already ran, and it is skipped. This is what makes retries and resumes safe.
Failure. A node that throws marks the run FAILED with the first 500 characters of the message and keeps the position at the failed node.
Guard. More than MAX_STEPS_PER_ADVANCE = 500 loop iterations marks the run FAILED with flow walk exceeded the step limit.

Node effects

Node	Effect	Skips recorded in `result`
`task`	`createMany` with `skipDuplicates` of one `InboxItem`: `type` is the run’s type, `source` `auto`, title is the node `name` or the `CONTENT` title, detail and priority from `CONTENT`, `metadata` from the run, `autoKey` `<entityKey>:fx:<nodeId>`. Owners: `coach` uses the trainee’s trainers, `manager` uses active `HEAD_COACH` rows, `specific` uses the listed members that are still active coaches of the studio, `none` and `all` leave it unowned	None
`push`	`createTraineeNotifier(...).notify(studioId, 'TRAINER_MESSAGE', ...)` with the message as `bodyOverride` and `{שם פרטי}` replaced by the first name	`empty message`, `no client`, `client missing`
`wa`, `mode` `free`	`ctx.smartsend.sendMessage` with the studio’s own SmartSend key from `Studio.settings.smartsend.apiKey`	`no client`, `client missing`, `no phone`, `no smartsend key`, `empty message`
`wa`, `source` `studio`	`ctx.smartsend.sendTemplate` with the studio key, `studioTemplate` and the `studioParams` values	`no studio template picked`, `no smartsend key`
`wa`, `source` `perform`	`ctx.smartsend.sendTemplate` on the global sender (`SMARTSEND_OTP_API_KEY`, else `SMARTSEND_API_KEY`) with the first name as the only parameter	`unknown template`, `template pending approval`, `no global sender key`
`webhook`	Queues a direct delivery on the hook queue. See below	`no url`
`content`	Creates a `ContentItemUnlock` with `source` `automation` after checking the item belongs to the studio. An existing unlock returns `already` true	`no content picked`, `no client`, `content not in this studio`

The built-in catalogue FLOW_WA_TEMPLATES has four entries (w1 to w4) and every one has realName set to null. A wa node with source perform therefore records template pending approval and sends nothing. Studio templates and free text do send.

The webhook node enqueues a job with directUrl and event automation_flow. The delivery worker posts it without a signature. The payload:

{
  "event": "INACTIVE",
  "occurredAt": "2026-10-07T09:00:00.000Z",
  "trainee": { "name": "Dana Levi", "phone": "0501234567", "email": "dana@example.com" },
  "program": "3 months",
  "flowNode": "CRM update"
}

flowNode is the node label, or its id when the label is empty. Delivery, retries and headers are described in Automation hooks. WhatsApp sending is described in WhatsApp.

Queues and workers

workers/flow-run-worker.ts, started from server.ts:

Piece	Queue	Behaviour
`createFlowRunQueue(ctx).enqueue`	`flow-run`	Job `advance` with the run id. 3 attempts, exponential backoff from 60 seconds. Continuation job ids are `flow-<runId>-<nodeId>` with unsafe characters replaced by a hyphen, so a duplicate enqueue collapses
`startFlowRunWorker`	`flow-run`	Calls `advanceRun`. Concurrency 2. When a job exhausts its attempts and the run is still `RUNNING`, the run is marked `FAILED` with `the flow run was interrupted`
`startFlowSweepWorker`	`flow-sweep`	Repeats every hour (job id `flow-sweep-hourly`) and once on boot. Re-enqueues up to 200 `WAITING` runs whose `resumeAt` passed, oldest first, and marks `RUNNING` runs untouched for 30 minutes as `FAILED` with `stalled`

The Postgres resumeAt column is the durable record of a wait. The delayed BullMQ job is a faster path. Whichever arrives first resumes the run and the other stops at the entry guard. There is no endpoint in this module that lists or retries flow runs.

API basics

Trainees

Plans and libraries

Tracking

Imports

Forms

Tasks and automation

Communication

Studio and billing

Admin and internal services

Trainee app API

Partner and automation

Public, internal and auth

Task automations

Mounting and auth

Storage

Triggers

Endpoints

`GET /v1/web/task-automations`

`PATCH /v1/web/task-automations`

`GET /v1/web/task-automations/wa-templates`

`GET /v1/web/task-automations/wa-templates/params`

Flow schema

Trigger

Node kinds

Branches and rules

Structural limits

Legacy conversion

Flow runtime

How a run starts

How a run advances

Node effects

Queues and workers

​Mounting and auth

​Storage

​Triggers

​Endpoints

​GET /v1/web/task-automations

​PATCH /v1/web/task-automations

​GET /v1/web/task-automations/wa-templates

​GET /v1/web/task-automations/wa-templates/params

​Flow schema

​Trigger

​Node kinds

​Branches and rules

​Structural limits

​Legacy conversion

​Flow runtime

​How a run starts

​How a run advances

​Node effects

​Queues and workers

Mounting and auth

Storage

Triggers

Endpoints

`GET /v1/web/task-automations`

`PATCH /v1/web/task-automations`

`GET /v1/web/task-automations/wa-templates`

`GET /v1/web/task-automations/wa-templates/params`

Flow schema

Trigger

Node kinds

Branches and rules

Structural limits

Legacy conversion

Flow runtime

How a run starts

How a run advances

Node effects

Queues and workers