Skip to main content

Logic Nodes

Logic nodes let you add decision-making and data processing to your workflows. They sit between your trigger and action nodes to control flow and transform data.

If/Else Node​

Branches the workflow based on a condition.

Configuration:

  • Define a condition expression (e.g., event.amount_owed > 0)
  • True path — continues to the connected "if" branch
  • False path — continues to the connected "else" branch

Use case: Only generate a notice if there's an outstanding balance.

Switch Node​

Routes data to different branches based on a value. Similar to a switch statement in programming.

Configuration:

  • Select a field to evaluate (e.g., event.notice_type)
  • Define cases: "N4", "N8", "N12", etc.
  • Each case connects to a different downstream node

Use case: Route to the correct template based on the type of legal notice.

ForEach Node​

Iterates over an array in the event payload, executing downstream nodes once per item.

Configuration:

  • Select the array field to iterate (e.g., event.tenants)
  • Downstream nodes receive one item at a time

Use case: A single webhook event contains multiple tenants — generate a separate document for each.

Filter Node​

Selects items from an array that match a condition.

Configuration:

  • Select the source array
  • Define the filter expression (e.g., item.balance > 0)

Use case: From a list of tenants, only process those with unpaid rent.

Compose Node​

Constructs a new data object by picking and transforming values from upstream nodes.

Configuration:

  • Define key-value pairs
  • Values can reference upstream fields, static values, or expressions

Use case: Combine data from multiple sources into a single object that matches your template's expected columns.

{
  "tenant_full_name": "${event.first_name} ${event.last_name}",
  "formatted_amount": "$${event.amount_owed}",
  "notice_date": "2026-04-12"
}

Select Node​

Picks specific fields from the event payload, discarding everything else.

Configuration:

  • Check the fields you want to pass downstream
  • Unchecked fields are dropped

Use case: Clean up a large webhook payload before passing it to a Template Node.

Organization Info Node​

Injects your organization's metadata into the workflow data, making it available to downstream nodes.

Available fields:

  • Organization name and display name
  • Address (street, city, province, postal code)
  • Phone number
  • Email and billing email
  • Website
  • Admin contact information

Use case: Auto-fill "From" sections of legal notices with your organization's contact details, without needing to include them in every webhook payload.