Skip to content
Glacis Help Center home
InboxAsk a human

Workflows

Workflows are currently only configurable by the Glacis team. In case you need access or need to understand workflows, please reach out to the Glacis team.

A workflow in Glacis is an automated process — "when something happens, do something about it." Workflows are how you automate repetitive supply chain tasks like processing incoming emails, creating orders, sending confirmations, and routing documents.

How workflows work

Every workflow follows the same pattern:

  1. A trigger starts it — an event happens (email arrives, order is created, document is uploaded)

  2. One or more actions run in sequence — extract data, create records, send emails, make decisions

  3. The result is stored — orders created, tasks assigned, emails sent

You build workflows visually in the editor — a canvas where steps appear as connected boxes. The sidebar label is Automation (under your team name).

Key concepts

Trigger: The event that starts the workflow. Every workflow has exactly one. Common triggers: Email Received, Order Created, Manual Trigger.

Action: A step that does something — sends an email, creates an order, runs AI analysis, or makes a decision.

Connection: The link between steps. Connections are created automatically when you add steps using the + button. You never need to draw lines manually.

Template variables: How steps pass data to each other. When configuring a step, you reference output from previous steps using {{STEP_KEY.field_name}}.

Publishing: A workflow must be published to run automatically. Unpublished workflows can be tested but won't respond to real triggers.

Workflow vs SOP

A workflow is a single automated process — one trigger, a chain of actions, done in seconds or minutes.

An SOP (Standard Operating Procedure) is a multi-step business procedure that may span days or weeks. SOPs contain multiple steps, each potentially linked to its own workflow. Use workflows for individual automations; use SOPs for end-to-end business processes.

For details on specific node types, see Triggers, AI Nodes, and Action Nodes.


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