Actions

Actions are the core building blocks of ServFlow workflows. They perform discrete operations such as fetching data from a database, calling external APIs, running AI agents, or transforming values. Every workflow consists of an entry point, one or more actions, and a response. You can configure actions in two ways:

Dashboard UI — Visual drag-and-drop interface for building workflows
YAML Configuration — Code-based configuration files for version control and advanced setups

For detailed documentation on each action type, see the Actions reference pages.

Actions in the Dashboard UI

The ServFlow dashboard provides a visual interface for adding and configuring actions in your workflows.

Adding an Action Node

To add an action to your workflow:

Click the + button below an existing node in the workflow canvas
Select Actions from the node type options
Browse the list of available actions in the sidebar

Browsing Available Actions

When you click to add an action, a sidebar panel displays all available action types. Each action shows its name and a brief description of what it does.

Available actions list in the ServFlow dashboard sidebar

Configuring an Action

Selecting an action opens the configuration panel on the left side of the screen. Each action type has specific fields to configure.

Action configuration panel showing AI Agent settings

The configuration panel displays:

Action type — The selected action (e.g., AI Agent)
Configuration fields — Type-specific settings such as identifiers, prompts, or connection details
Save Action — Button to save your configuration

Use {{ .Variable }} syntax in input fields to reference dynamic content from previous actions or request parameters.

Connecting Actions

Actions have output handles that let you define the flow:

Next — Where to route on successful completion
Fail — Where to route when an error occurs
Tools — Additional outputs for specific action types (e.g., AI Agent tools)

Drag connections from these handles to other actions, conditionals, or response nodes to build your workflow logic.

Using Action Results

When an action completes, its result is stored and can be referenced by subsequent nodes. Use the {{ .Variable }} syntax in any input field to access these values. For example, if an action with ID get_user returns user data, you can access the email field in a later action with {{ .get_user.email }}.

Actions in YAML Configuration

For code-based workflows, actions are defined in YAML configuration files. This approach is ideal for version control, complex workflows, and programmatic configuration.

Action Structure

Every action follows this structure:

actions:
  action_id:
    type: action_type
    config:
      # type-specific configuration
    next: action.next_step
    fail: response.error

The action_id is a unique identifier you choose for the action. You’ll use this ID to reference the action’s results in other parts of your workflow.

Common Fields

Field	Type	Required	Description
`type`	string	Yes	The action type identifier (e.g., `fetch`, `http`, `agent`)
`config`	object	No	Type-specific configuration options
`next`	string	No	Step to execute on success
`fail`	string	No	Step to execute on failure

Chaining Actions

Use the next and fail fields to define your workflow’s execution path:

next — Routes to another step when the action succeeds
fail — Routes to an error handler when the action fails

The routing syntax follows the pattern type.identifier:

action.other_action — Route to another action
conditional.check_value — Route to a conditional branch
response.success — Route to a response

Accessing Action Results

Action results are stored under the action’s ID and can be accessed using template syntax:

# Access the full result from action 'fetch_user'
value: "{{ .fetch_user }}"

# Access a nested field
value: "{{ .fetch_user.email }}"

# Use in expressions
expression: "{{ gt (len .fetch_user) 0 }}"

Here’s an example of chaining actions where the second action uses data from the first:

actions:
  get_user:
    type: fetch
    config:
      integrationID: my_database
      table: users
      filters:
        - field: id
          operator: eq
          value: "{{ param \"user_id\" }}"
      single: true
    next: action.send_welcome

  send_welcome:
    type: email
    config:
      recipientEmail: "{{ .get_user.email }}"
      subject: "Welcome!"
      content: "Hello {{ .get_user.name }}, welcome to our platform."
    next: response.success

Available Actions

ServFlow provides a comprehensive set of actions organized by category. Click through to the detailed reference pages for full configuration options and examples.

Data Operations

Action	Description
`fetch`	Retrieves data from a database table
`store`	Stores a new record in a database table
`update`	Updates existing records
`delete`	Deletes records from a database table
`mongoquery`	Executes native MongoDB queries

Vector Operations

Action	Description
`storevector`	Stores vector embeddings
`fetchvectors`	Queries vectors for similarity search

HTTP & External APIs

Action	Description
`http`	Makes HTTP requests to external APIs

Authentication & Security

Action	Description
`authenticate`	Validates JWT tokens and fetches user data
`jwt`	Encodes or decodes JWT tokens
`hash`	Hashes values using bcrypt

Transformation & Logic

Action	Description
`javascript`	Executes custom JavaScript code
`static`	Returns a static or computed value

AI & Agents

Action	Description
`agent`	Interacts with AI models

Flow Control

Action	Description
`parallel`	Executes multiple actions simultaneously

Communication

Action	Description
`email`	Sends email messages via SMTP

System

Action	Description
`command`	Executes shell commands

Memory

Action	Description
`memory_store`	Stores data in temporary memory
`memory_fetch`	Retrieves data from temporary memory

Binance Trading

Action	Description
`binance/getprice`	Gets cryptocurrency price data
`binance/accountbalance`	Queries Binance account balances
`binance/spotorder`	Places spot trading orders
`binance/futuresorder`	Places futures orders
`binance/pricedifference`	Calculates price changes
`binance/tradeinfo`	Gets order and position info

Next Steps

Actions Overview

Explore the complete actions reference documentation.

Quickstart

See actions in practice by building your first API.

Configuration Reference

Explore all ServFlow configuration options.

Secrets Management

Securely store credentials used by your actions.

Getting Started

Concepts

References

Actions

Actions in the Dashboard UI

Adding an Action Node

Browsing Available Actions

Configuring an Action

Connecting Actions

Using Action Results

Actions in YAML Configuration

Action Structure

Common Fields

Chaining Actions

Accessing Action Results

Available Actions

Data Operations

Vector Operations

HTTP & External APIs

Authentication & Security

Transformation & Logic

AI & Agents

Flow Control

Communication

System

Memory

Binance Trading

Next Steps

Actions Overview

Quickstart

Configuration Reference

Secrets Management

Getting Started

Concepts

Actions

References

​Actions in the Dashboard UI

​Adding an Action Node

​Browsing Available Actions

​Configuring an Action

​Connecting Actions

​Using Action Results

​Actions in YAML Configuration

​Action Structure

​Common Fields

​Chaining Actions

​Accessing Action Results

​Available Actions

​Data Operations

​Vector Operations

​HTTP & External APIs

​Authentication & Security

​Transformation & Logic

​AI & Agents

​Flow Control

​Communication

​System

​Memory

​Binance Trading

​Next Steps

Actions Overview

Quickstart

Configuration Reference

Secrets Management

Actions in the Dashboard UI

Adding an Action Node

Browsing Available Actions

Configuring an Action

Connecting Actions

Using Action Results

Actions in YAML Configuration

Action Structure

Common Fields

Chaining Actions

Accessing Action Results

Available Actions

Data Operations

Vector Operations

HTTP & External APIs

Authentication & Security

Transformation & Logic

AI & Agents

Flow Control

Communication

System

Memory

Binance Trading

Next Steps