> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aisera-platform/what-can-my-bot-do/ai-automation-optimize-flow/ai-workflow-studio/workflow-reference-guides/workflow-nodes.md).

# Workflow Nodes

[Workflows](https://aisera.com/blog/ai-workflow-orchestration-guide/) are often triggered by Intents. In other words, when a user makes a request to your application or bot, the first thing the software determines is what the user wants to know or do. The bot does this by recognizing the exact request or by asking follow-up questions until it determines the intention (Intent) of the user. 

Your bot will often have many possible Intents, and each Intent will start a workflow that will end with the Fulfillment (answer) for the original request.

See [**Configuring Intents**](/aisera-platform/crafting-the-conversation/configuring-icm-intents-and-fulfillment.md) for instructions about how to create Intents for your application or bot.

## The Workflow Node Palette

This guide explains why the Workflow Editor’s **node palette**—the left-side list of nodes—can show fewer node types for some workflows. In most cases, this is expected behavior. The editor shows only the node types that are supported for the workflow’s current use.

Use this page if you think that expected node types are missing from the left-side palette. Some of the nodes may show conditionally, based on the type of node you are adding.

## Default Node View <a href="#what-users-normally-see" id="what-users-normally-see"></a>

For a standard editable workflow, the node palette contains the following groups and node types.

| Group            | Available node types                                                     |
| ---------------- | ------------------------------------------------------------------------ |
| Actions          | Action, MCP Tool, Create Ticket, Ask Approval, Table Query, Notification |
| User Interaction | User Input, Input Form, Message                                          |
| Operations       | Decision, Goto, Subflow, Parallel, Prompt, Callback, Set Variable        |
| Advanced         | HTTP Request, JavaScript                                                 |

The **Create Ticket** node is available only when the workflow is associated with an application (aka. Bot).

### The workflow is used by an active Parallel node <a href="#the-workflow-is-used-by-an-active-parallel-node" id="the-workflow-is-used-by-an-active-parallel-node"></a>

When a workflow is used as a child branch of a **Parallel** node in an active parent workflow, the editor limits the palette to node types that are supported in that parallel branch. This might make the palette look smaller.

This protects the workflow from being configured with interactions or operations that are not supported while parallel work is running.

The following nodes are not available to add in this situation.

| Group or node type | Not available                       |
| ------------------ | ----------------------------------- |
| User Interaction   | User Input, Input Form, Message     |
| Operations         | Subflow, Parallel, Prompt, Callback |
| Actions            | Ask Approval                        |

The remaining available nodes are:

| Group      | Available node types                                                                        |
| ---------- | ------------------------------------------------------------------------------------------- |
| Actions    | Action, MCP Tool, Create Ticket (when the workflow is App level), Table Query, Notification |
| Operations | Decision, Goto, Set Variable                                                                |
| Advanced   | HTTP Request, JavaScript                                                                    |

**Important:** This restriction applies when at least one active parent workflow uses the workflow in a Parallel node. It can apply even if the workflow is also used elsewhere.

### The workflow is a Knowledge Flow <a href="#the-workflow-is-a-knowledge-flow" id="the-workflow-is-a-knowledge-flow"></a>

Knowledge Flows do not show the **Actions** group. Their palette starts with User Interaction, Operations, and Advanced nodes.

If a Knowledge Flow is also used by an active Parallel node, the palette is reduced to the following nodes:

* Decision
* Goto
* Set Variable
* HTTP Request
* JavaScript

This is the smallest expected editable palette.

### The workflow has no associated application <a href="#the-workflow-has-no-associated-application" id="the-workflow-has-no-associated-application"></a>

If the workflow is not associated with an application, the **Create Ticket** node is not shown. Other applicable nodes remain available.

### The workflow cannot be edited <a href="#the-workflow-cannot-be-edited" id="the-workflow-cannot-be-edited"></a>

If the workflow is read-only, imported, or its current version is not editable, the editor hides the entire node palette rather than showing a smaller list.

## Guidance for workflow authors <a href="#guidance-for-workflow-authors" id="guidance-for-workflow-authors"></a>

1. Check whether the workflow is configured as a branch of a Parallel node in an active parent workflow.
2. If it is, design the branch using only the nodes shown in the palette. The omitted nodes are intentionally unavailable for that execution context.
3. If the workflow needs a user interaction, approval, nested workflow, callback, prompt, or another Parallel node, move that work outside the Parallel branch or redesign the parent workflow so this workflow is not used as a parallel child.
4. Check the workflow type and application association when the Actions group or Create Ticket node is missing.
5. If the entire palette is missing, confirm that the workflow is opened in an editable version and that the user has edit permission.

## Guidance for product managers and operations teams <a href="#guidance-for-product-managers-and-operations-teams" id="guidance-for-product-managers-and-operations-teams"></a>

* A reduced palette is an expected compatibility safeguard, not a loading failure or a role-based partial permission issue.
* The restriction is driven by how the workflow is used by active workflows, not by the node types already present on the canvas.
* An active parallel-parent relationship is sufficient to restrict the palette; the workflow does not need to be opened from that parent workflow for the restriction to apply.
* When investigating a report, identify the workflow’s type, application association, editability, and active parent workflows that reference it through a Parallel node.

## Support triage checklist <a href="#support-triage-checklist" id="support-triage-checklist"></a>

Collect the following before escalating:

Workflow name and ID.Workflow type: standard workflow or Knowledge Flow\.Whether the workflow has an associated application.Whether the whole palette is hidden or only selected nodes are absent.The name and status of every parent workflow that uses this workflow\.Whether a parent uses the workflow in a Parallel node.The workflow version and the user’s edit permission.

With this information, support can distinguish expected node availability from an unexpected editor issue.

## Building Workflows

You can [build workflows](https://aisera.com/products/ai-workflows/) without attaching them to Intents.

To build a workflow, choose **+ New Workflow** in the AI Workflow Studio window.

<div align="left"><figure><img src="https://3281977978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBFXjH9S1CAy9f5hzg5Q%2Fuploads%2F71kx7IZrHk5yIz6pUrXw%2Fnew_workflow.png?alt=media&amp;token=294ef141-0b15-4a4e-ad82-6c5a9cdf6b7a" alt="" width="563"><figcaption></figcaption></figure></div>

Then type the name of the workflow, select the workflow **Type** and **Scope** from the drop-down menus. The **Description** field is optional.

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXedN4dsPvntC6mpIDq1C3aUdEhUYTkkFo5N1Y8LJl6dJOWIUXhyCyNtVTLFYPIVBbaWVR7atacRwZQkZmwMghC2NegZoLY8hRhQ479iW5VqOjWt7Wzq-BI7_bSAUpkZrL0v5fOj-zhlppLcSjwXdwGIDsRHuNp0WLdqdml-Xffy-R_thuwW8ss?key=D_gN9K8DxPeuol8TkTw43Q)

Create a New Workflow

The **Description** field is optional.

The nodes appear on the left side of the AI Workflow Studio blank canvas in sections that correspond to how they're designed to be used.

<div align="left"><figure><img src="https://3281977978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBFXjH9S1CAy9f5hzg5Q%2Fuploads%2Fwne4MOXvUU1m5AODWfUO%2Fblank_canvas.png?alt=media&amp;token=6be0b9ad-e7b6-4c79-9d79-392ac66a4029" alt="" width="563"><figcaption><p>Blank Canvas for New Workflow</p></figcaption></figure></div>

## Types of Nodes

Nodes are the building blocks for your workflow. The nodes are on the left side on the canvas and are grouped according to their usage. Each of the Node Types is described in one of the links below.

* [Action Nodes](#action-nodes)
* [User Interaction Nodes (Conversational Nodes)](/aisera-platform/what-can-my-bot-do/ai-automation-optimize-flow/ai-workflow-studio/workflow-reference-guides/workflow-nodes/user-interaction-conversational.md)
* [Operations Nodes](/aisera-platform/what-can-my-bot-do/ai-automation-optimize-flow/ai-workflow-studio/workflow-reference-guides/workflow-nodes/operations-nodes.md)
* [Advanced Nodes](#advanced-nodes)

Drag a node onto the AI Workflow Studio canvas and then define what the node will do. The topics above are a reference for the nodes and tools available to you in the AI Workflow Studio.&#x20;

## Save the Workflow

After you've finished building the workflow logic, click on **Save as Draft**.&#x20;

<div align="left"><figure><img src="https://3281977978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBFXjH9S1CAy9f5hzg5Q%2Fuploads%2FYwpj2SNKaQN5gbr1NlGS%2Fsave_as_draft.png?alt=media&amp;token=bc284fa7-c3d9-45dc-87c1-7fdb18ac5c4e" alt="" width="368"><figcaption></figcaption></figure></div>

This grays out the Save button and will publish the flow. For it to work as expected, this step of the flow is mandatory every time you make a change. It is possible to roll back to any published version.