Nodes

Nodes are the building blocks of a Spaceflow. Each node represents a flow step — an action, a decision, an integration, or a logic control. To build a flow, you drag nodes onto the construction canvas and connect them in sequence, defining the path the process should follow.

To see available nodes, open the Nodes tab on the Spaceflow editing screen.

How nodes work

Data input and output

Each node has two main functions related to data management:

• Input — the data the node receives from the previous node in the flow. For example, an approval node can receive the fields filled in a form from the previous step.
• Output — the data the node generates after processing the input, making it available for the following nodes. For example, a form node generates as output the filled values (name, date, notes), which can be used in an approval, an email delivery, or a document generation.

This input-output chain allows information to flow throughout the entire process, being reused and transformed at each step.

Nodes that generate tasks

Some nodes, when executed, automatically generate a task that appears on the workspace's Tasks screen. This happens when the node requires a human action — such as filling a form, approving a request, or executing a manual operation.

Other nodes are executed fully automatically, without generating a task — such as email delivery, automatic CRUD operations, or conditionals.

When a node generates a task, the flow only advances to the next node after the task is completed.

Node types

Available nodes are organized into six categories:

Triggers

Nodes that start the flow. Every Spaceflow begins with a trigger node that defines when and how the flow will be fired.

• Start— defines the flow's execution trigger. Available trigger types are:
  • Manual — the flow is started manually by a user.
  • Item actions — the flow is fired automatically when an item in a chosen category is created, updated, or deleted.
  • Timer — the flow is executed automatically at scheduled intervals.
  • Webhook — the flow is fired by an external call via webhook.

Actions

Nodes that execute tasks in the workflow. Some generate tasks for human action, others execute automatic operations.

• Form — triggers a form whose responses guide the flow's next steps. Generates a task for the assignee to fill in.
• Approval — requests that an assignee approve or reject before the flow continues. Generates an approval task.
• Task — creates a manual task with a deadline and assignee. The flow waits for the task to be completed before advancing.
• Email — sends automatic emails for notices, confirmations, or notifications. Executed automatically, without generating a task.
• CRUD Operations — creates, edits, or deletes records in any workspace category. Can be configured as a manual action (generates a task) or automatic (direct execution).

I.A.

Nodes that use artificial intelligence to enhance the capabilities of the flow. They operate with the AI agents available in ENSPACE, configured through a prompt field.

• AI Extractor — allows extracting structured information with a search across the entire Workspace. (Coming soon)
• AI Agent — allows using a customized artificial intelligence agent to make decisions and execute tasks autonomously within the flow, expanding the automation capabilities of Spaceflow. (Coming soon)
• AI Generator — generates text responses based on a prompt defined by you. It is possible to combine fixed instructions with dynamic variables from previous nodes, allowing the AI to produce personalized content for each flow execution.
• AI Router — analyzes the content that reaches the node and automatically decides which path the flow should follow.

Logic and Control

Nodes that control the flow's path, logic, and termination. They are executed automatically, without generating tasks.

• Conditionals — directs the flow by a single rule based on statuses, responses, or field values. Ideal for simple "if this, then that" decisions.
• Routes — directs the flow through multiple paths, combining several conditions in each route. Ideal for complex decisions with multiple simultaneous criteria (for example: if the contract value is greater than $100,000 and the area is civil, route to the supervisor; if it's civil but less than $100,000, route to the analyst).
• Merge — joins multiple paths into a single flow. If all inputs are configured as mandatory, the node waits for all paths to arrive before continuing. Otherwise, the flow proceeds as soon as any path arrives.
• End — marks the flow's termination. After this step, no further actions will be executed.
• Loop — repeats actions until a condition is met. (Coming soon)
• Iterator — loops through items and executes actions for each one. (Coming soon)
• Aggregator — collects and combines data from multiple steps. (Coming soon)

Documentation

Nodes for creating and managing documents from flow data.

• Documentation — generates PDF, DOCX, or spreadsheets from flow data. (Coming soon)

Integrations

Nodes that connect the flow to external systems and services.

• HTTP Request — integrates via APIs to connect external systems and data to the flow.