Workflow nodes

Workflows are built by connecting different types of nodes. Each node performs a specific function in the automation.

Node Types

The Automations platform currently supports four node types. While LLM and Condition nodes are native to the platform, the variety of Triggers and Actions available to you depends entirely on the Integrations you have connected:

1. Trigger Nodes - Start workflows

2. Action Nodes - Perform operations

3. LLM Nodes - AI processing

4. Condition Nodes - Branching logic

---

1. Trigger Nodes

Purpose: Start a workflow when a specific event occurs

Characteristics:

• Every workflow must have at least one trigger

• Triggers listen for external events

• Each trigger provides a payload with event data accessible to all nodes

Available Triggers: Triggers are provided by Integrations. As new integrations are installed, the library of available triggers grows.

• Native Triggers: Core triggers like Cron come from the Core Utilities integration.

• Integration Triggers: Provided by installed apps (e.g., "New Zendesk ticket", "Email received", "Status changed").

• Extensible Architecture: Since integrations are standalone services, a trigger can be anything that can interact with a web server.

---

2. Action Nodes

Purpose: Perform tasks and operations (API calls, data processing, etc.)

Characteristics:

• Execute specific operations (create ticket, add tag, set status)

• Require arguments (inputs) that can reference previous node outputs

• Return results that can be used by subsequent nodes

Note on Rate Limits: Actions are subject to the rate limits of the connected system. High-frequency workflows may be throttled by the external API.

---

3. LLM Nodes

Purpose: Process data using Large Language Models (AI)

Characteristics:

• Send prompts to EbbotGPT or other AI models

• Support structured output (JSON schemas)

• Can use RAG (Retrieval-Augmented Generation) for context

• Support tool calling for function execution

Note on Rate Limits: When the LLM node is configured with tools, it is subject to the rate limits of the systems those tools are connected to.

---

4. Condition Nodes

A condition node leading to an action.

Purpose: Create branching logic in workflows

Characteristics:

• Evaluate conditions to determine workflow path

• Support six comparison operators: Same as, Not the same as, Less than, Less than or same as, Greater than, Greater than or same as.

• Enable if/else branching

• Referencing Node Data: Values are selected via UI dropdowns (e.g., Select "ticketing_trigger" node → "requester_email" field).