Action Nodes
Action nodes are the steps in a workflow that do something — create an order, send an email, make a decision, or call another workflow. This page covers the non-AI action nodes available in Glacis. For AI nodes, see AI Nodes. For triggers, see Triggers.
Decision Point
Splits your workflow into two paths based on a condition.
When to use it: When the next step depends on a value — e.g., "Is this a purchase order?" or "Is the order amount over $10,000?"
How it works:
Add a Decision Point step to your workflow.
Define a condition using data from previous steps (e.g.,
{{AI_CLASS.output.category}} == "purchase_order").The workflow splits into a Yes path and a No path.
Add steps to each path by clicking + on the Yes or No branch.
Decision Points are how you build routing logic. A common pattern: classify an email with AI → Decision Point to check the category → different actions for each type.
Send Email
Sends an email from your team's Glacis email address.
When to use it: Sending confirmations, notifications, follow-ups, or any outbound communication as part of a workflow.
Configuration:
Field | Description |
|---|---|
To | Recipient email address(es) — can use template variables |
Subject | Email subject line |
Body | Email content — supports template variables for personalization |
Attachments | Optionally attach documents from previous steps |
Example: Send an order confirmation after creating an order:
To: {{TRG_EMAIL.From}} Subject: Order {{CRT_ORDER.order_number}} Confirmed Body: Hi, we've received your order {{CRT_ORDER.order_number}} and it's being processed...
Create Order
Creates a new order in Glacis using data from previous steps.
When to use it: Automatically creating orders from extracted email/document data.
Configuration: Map data from previous steps to order fields — order type, order number, supplier, items, dates, etc. Uses template variables like {{AI_EXTR.output.order_number}}.
The field mapping for Create Order can be complex if your extracted data has many fields. Your Glacis admin can help configure this step for your specific data structure.
Update Order
Updates an existing order with new data.
When to use it: Modifying orders based on incoming information — price changes, quantity updates, delivery date changes.
Key option: Create-or-Update mode — if the order doesn't exist, create it; if it does, update it. This is useful when you're not sure if an incoming PO is new or a revision of an existing one.
Create Task
Creates a task and assigns it to a user or team.
When to use it: Flagging items for human review, creating follow-up tasks, assigning approvals.
Configuration:
Field | Description |
|---|---|
Title | Task name — can use template variables |
Description | What needs to be done |
Assignee | Who should handle the task |
Priority | Critical, High, Medium, or Low |
Deadline | When the task is due |
Create Shipment
Creates a shipment record linked to an order.
When to use it: Automatically creating shipment records when orders are confirmed or when shipping details are received.
Action Groups
An action group is a set of steps that run together as a unit. Action groups help organize complex workflows by grouping related steps.
When to use it: When several steps always run together and you want to manage them as a unit — for example, "create order + send confirmation + create task" as a single group.
Action groups are an advanced feature. For most workflows, sequential steps with Decision Points are sufficient.
Need help?
If you have questions or run into issues, we're here to help:
Chat with us — use the support widget in the bottom-right corner of Glacis
Email — reach us at support@glacis.com
Related docs — Creating Workflows | AI Nodes | Triggers