ContentRunner Next Message (Stage) icon

ContentRunner Next Message (Stage)

From user state and branches (welcome/main), compute state_check, current/next message per branch, next planned times, and is_last_in_branch

ContentRunner Next Message (Stage)

AI-generated

Summary

Computes per‑branch state, next and after‑next messages, and passes through selected input fields.

Inputs

  • userState — Object from ContentRunner Get State containing current_cursor_* and timestamps.
  • branchWelcome — Array of branch items (cursor_index, interval_minutes) from Campaigns By Bot for the welcome branch.
  • branchMain — Array of branch items (cursor_index, interval_minutes) from Campaigns By Bot for the main branch.
  • passThrough — Comma‑separated list of input JSON keys to forward unchanged (e.g. parsed, update).

Output shape

Array of objects, each containing a json property with computed state_check, welcome and main branch data, plus any passed‑through fields.

Missing branch data is null; passed‑through keys are copied from the incoming item; the result is always wrapped in an array.

Examples

Example 1: Propagate state and branch definitions to compute next message schedule.

Set User State, Branch Welcome, Branch Main; no Pass Through filter needed.

Example 2: Forward specific JSON keys to downstream nodes.

Configure passThrough as 'chat_id,from_language_code' to retain those values in output.

Example 3: Detect end of welcome branch and trigger final action.

Use default values; node will set is_last_in_branch true when no further welcome messages remain.

Links

Discussion