gaiia Nodes

Overview

gaiia Nodes are pre-built workflow nodes that turn common platform actions into simple, form-based steps inside the Workflow Builder. Instead of writing GraphQL queries, you can use clearly named nodes like Get Account or Create Work Order to interact with gaiia data.

gaiia Nodes are designed to handle the most common workflow actions and work alongside existing GraphQL nodes rather than replacing them.

In this article, we’ll be covering what gaiia Nodes are and how they’re used in the Workflow Builder.

Understanding what gaiia Nodes are

Previously, building workflows that interacted with gaiia data required writing things like GraphQL queries and handling responses manually. gaiia Nodes remove that complexity by abstracting the most common API operations into reusable nodes.

Each gaiia Node represents a single platform action, such as retrieving an account or creating a work order. Inputs for these nodes can be configured using plain text values, TypeScript, or State Inputs. When a node runs, it returns structured output that can be used in later steps of the workflow.

This approach reduces the amount of custom API logic required in a workflow and makes workflows easier to build and maintain.

Exploring the available node categories

gaiia Nodes appear directly in the Workflow Builder’s node library alongside existing nodes. They’re grouped by functional area and labeled by action, making them easy to browse and understand.

• Accounts – Retrieve account data, notes, billing subscriptions, and assigned inventory.
• Tickets – Create and update tickets, add comments, and retrieve ticket metadata.
• Inventory – Assign inventory items to accounts.
• Workforce – Create and update work orders, manage technician assignments, and retrieve work types.

Adding gaiia Nodes to a workflow

Once you’re in the Workflow Builder, you can add gaiia Nodes the same way you add any other node.

1. Open the node library in the Workflow Builder.
2. Browse to the gaiia API section and select the category you need.
3. Click the + beneath an existing node in the graph to add a gaiia Node.
4. Select the specific action, such as Get Account or Create Internal Ticket.

Configuring node inputs and outputs

Each gaiia Node exposes a set of required and optional inputs, depending on the action it performs.

• State-based inputs: Reference values already stored in the workflow state, such as state.objectId.
• Plain text inputs: Enter static values like ticket descriptions or note content.
• TypeScript expressions: Build dynamic values for more advanced scenarios.

After a node runs, its output is stored in the workflow state and can be accessed using the standard pattern:

state.steps['node-slug'].output

Walking through a basic example of a workflow

Step 1: Start with a trigger

Create a new workflow with a Manual trigger on an Account.

Step 2: Add a “Get Account” node

1. Open the node library.
2. Find Get Account under gaiia API > Accounts.
3. Configure the input by selecting the State input in the field dropdown, and add objectId.
   

Step 3: Use the account data

The account data is now available in state.steps['get-account'].output.response.account with fields like:

• accountId
• readableId
• primaryContact (firstName, lastName, email, phone)
• physicalAddress (locality, region, postalCode)
• customFields

Step 4: Create a note on the account

1. Add a Create Note node.
2. Configure required inputs:
   • content: Write plain text or use TypeScript for dynamic content
   • linkedEntityId: steps.get-account.output.account.id
   • linkedEntityType: Select from dropdown (e.g., “ACCOUNT”)

Step 5: Test your workflow

Run the workflow and verify the note appears on the account in gaiia.

Reviewing permissions and requirements

To use gaiia Nodes, users must meet the following requirements:

• Access to the Workflow Builder. 
• Appropriate module permissions for the actions being performed, such as ticket or work order creation.

No additional configuration is required to enable gaiia Nodes once access is granted.