Context

The Context node provides the event context as pipeline input. When used as a source node (no incoming edges), it returns the parent context with form element values merged in. When used as a pass-through (has incoming edges), it returns the input data.

Configuration

This node has no configuration options.

Input

When used as a source (no incoming connections): Returns the parent context. When used as a pass-through (has incoming connections): Returns the incoming data unchanged.

Output

As a source node

Returns the event context, which includes:

• Row data: The data context from the triggering element (e.g., the current row in a repeater).
• Form element values: Values from form inputs within the same form container, merged at the top level.

{
  "id": 42,
  "title": "Existing Item",
  "name_input": "John Doe",
  "email_input": "john@example.com",
  "message_input": "Hello world"
}

In this example, id and title come from the row context, while name_input, email_input, and message_input come from form elements.

Form element merging

If the context contains an _elements key (form element values), those values are merged to the top level and _elements is removed. This makes form values accessible directly: { {row.name_input}} instead of { {row._elements.name_input}}.

Example Use Cases

Form submission pipeline

The Context node is typically the first node in a form submission action pipeline:

Context --> Validate --> Sanitize --> Save Row --> Output

The Context provides all form field values as a flat object.

Action with row context

When a button inside a repeater triggers an action, Context provides the current row data:

Context --> Set Field (completed = '1') --> Update Row --> Output

The Context includes the full row (with id), so Update Row knows which record to modify.

Access both row data and form values

In an edit form that modifies an existing record:

Context --> Validate --> Sanitize --> Update Row --> Output

The Context merges the existing row's id with the form's input values, giving Update Row both the ID and the new values.

TIP

The Context node is similar to Parent Data, but adds form element value merging. Use Context for action pipelines (form submissions, button clicks) and Parent Data for data source pipelines (loading data for display).