Sequence

The Sequence node

Lede. Generates a per-record number or string – the running counter for the current merge.

Group: Sequence · Available in: all text-bearing workspaces · Central node: No

Purpose

  • Number records sequentially (1, 2, 3 …).
  • Generate a per-record alphanumeric ID (A001, A002, …).
  • Produce a hashed / random per-record token for uniqueness.
  • Emit a per-record value that doesn’t come from the datasource.

Where to find it

Add Node ▸ Data ▸ Sequence

(Lives under Data because the Sequence category’s label is Data.)

How it works

The settings panel lets you pick a generation mode: counter, formatted counter, random, hash, …. On each evaluation the node returns the next value in the sequence for the current record. Wire the result downstream like any other text source.

The In socket is optional and accepts multiple connections – chained upstream values are concatenated before the sequence value. The Format socket applies a Text Formatter to the output.

Sockets

Direction Name What it does What you can connect
Input In Optional upstream text concatenated before this node’s value. Any text-producing node.
Input Format Formatter applied to the output. Text Formatter.
Output Out The generated value. Placeholder Content, Data Text In, …

Settings

Setting What it does
Mode Counter / formatted counter / random / hash / …
Start value Where the counter starts.
Step Counter increment.
Pattern Format string when applicable (e.g. A000 for zero-padded letters + digits).

Example (end-to-end)

Scenario. A serial number S-001, S-002, … per generated PDF page.

Wiring.

[Static Text: "S-"] → [Sequence: counter, start=1, pattern="000"] → [Placeholder.Content]

Empty / error behaviour

  • Never empty for counter / formatted-counter modes.
  • Random / hash modes may produce duplicates by their nature; if uniqueness matters, use the counter modes.

Limitations

  • The counter is per merge, not per document. If you split a merge run, the counter resets.
  • No persistent state across merges (use a per-record column instead for permanent identifiers).

Common pitfalls

  • The counter doesn’t reset between previews. Re-open the document or use Preview again to reset.
  • Data Text – common upstream chain partner.
  • Text Formatter – downstream cleanup.
  • Repeater – the other Sequence-category member; together they handle "this n-th record" vs. "iterate n records".

Screenshots

📷 Screenshot [NEU]: Sequence settings panel

Not found what you're looking for?

Node Reference · Last updated 3 weeks ago

Copyright ToolboxCode UG