Actions are powerful elements that bring your process nodes to life by adding business logic, data management capabilities, and integration with external systems. They define the specific activities that nodes perform within your process flow.

​
What is a node action?

Node Action

A node action defines the specific activity that a node performs within a process flow. Actions allow you to incorporate business rules, manage data, communicate with external systems, and control what gets displayed in the user interface. They are the building blocks that drive your process logic and user interactions.

Actions Documentation

Comprehensive documentation on all action types and their configurations

Business Rules

Learn how to implement business logic with rule actions

​
Action types

FlowX.AI supports several types of actions that can be added to nodes, broadly categorized into business rules and user interactions:

​
Business rules and data management

Business Rule

Add custom logic and decision-making using scripts

Save Data

Persist process data to storage

Kafka Send

Send messages to Kafka topics for event-driven scenarios

Upload File

Handle file uploads within the process flow

​
Process control and integration

Start Subprocess

Initiate a subprocess from within the current process

Append Params to Parent Process

Pass data back to a parent process from a subprocess

Start Integration Workflow

Trigger an integration workflow with external systems

Start New Project Instance

Launch a new project instance from within a process

​
User interface

Send Data to User Interface

Send data to be displayed in front-end applications

Actions can only be added to certain node types:

  • Task nodes (Service Tasks)
  • User Task nodes
  • Send Message/Receive Message Task nodes

​
Adding an action to a node

1

Access Your Process Definition

  1. Open FlowX.AI Designer and navigate to your project
  2. Go to the Processes section within your project
  3. Select your process definition from the list
  4. Click the Edit Process button to open the Process Designer
2

Select or Add a Node

  1. Either select an existing node that supports actions, or add a new one
  2. Remember that only Task nodes, User Task nodes, and Message Task nodes support actions

If you need to add a new node first, refer to the Adding a New Node documentation.

3

Add an Action

  1. With the node selected, locate the Actions section in the properties panel
  2. Click the + Add Action button
  3. From the dropdown menu, select the action type you want to add

4

Configure Action Parameters

Each action type requires specific configuration parameters:

  1. Fill in the required fields for your selected action type
  2. Configure optional parameters as needed
  3. Save your changes

Pay careful attention to parameter syntax and formatting. Incorrect configurations may cause the action to fail during process execution.

5

Set Action Execution Order (Multiple Actions)

If you have multiple actions on a single node:

  1. Use the drag handles to arrange the actions in the desired execution order
  2. Actions will execute from top to bottom in the list
  3. Consider dependencies between actions when setting the order

For complex nodes with multiple actions, consider adding comments in scripts or descriptions to document the purpose and dependencies of each action.

6

Save Your Process

Click the Save button to save your process definition with the new action.

​
Common action configurations

Different action types require different configurations, but many share these common elements:

​
Best practices

When adding actions to nodes:

  • Use meaningful action names to clearly indicate their purpose
  • Keep business rules focused on a single responsibility
  • Document complex logic with comments in your scripts
  • Consider error handling in your action configurations
  • Test actions individually before relying on them in production flows
  • Monitor performance of actions that might be resource-intensive
  • Use consistent data structure across related actions for better maintainability

​
Next steps

After adding actions to your nodes, you can:

Handling decisions in the flow

Learn how to implement conditional branching in your processes using exclusive gateways

Configure UI Components

Design the user interface elements that will interact with your actions