Tables and variables

Every workflow's run context resolves from its trigger and whatever earlier nodes produced (see Workflows) - but some values and data need to persist across runs, or be shared between workflows, without standing up Postgres just for a lookup table. Variables and data tables cover that gap. Both are scoped to your account - there's no team/workspace model yet, so nothing here is shared between users.

Variables

Open Variables from the sidebar to set named key/value pairs. Every variable you set is automatically resolved into every workflow's run context as {{vars.X}} - no per-workflow wiring required, it's just there. Mark a variable secret and its value is encrypted at rest and decrypted only at execution time, the same way credential values are.

Typical uses: a base URL you reference from several HTTP Request nodes, a default notification recipient, a feature flag, an API version string - anything you don't want copy-pasted across every workflow that needs it.

HTTP Request
  endpoint: {{vars.apiBase}}/v1/orders

Data tables

Open Data Tables from the sidebar to create a named table with typed columns (text, number, or boolean). The Data Table node then reads and writes rows from any workflow:

• insert - add a row from a JSON template (Handlebars-resolved against the context).
• get - look up rows, optionally filtered by a field/value match, capped at 1000 rows per query.
• update - patch rows matching a field/value filter.
• delete - remove rows matching a field/value filter.

This is the lightweight alternative to the Postgres node or one of the Data stores app nodes when what you need is a simple scratchpad - a dedupe list, a small lookup table, counters - not a full external database.

Related

• Workflows - how {{vars.X}} fits alongside trigger and node context.
• Credentials - the same encryption approach secret variables use.
• Node reference: Data & Utilities - the Data Table node's full entry.