What is a workflow?
A workflow (also called a "flow") is an automated sequence of actions triggered by specific events. Workflows enable you to connect different services and automate business processes visually.
Key Concepts
Workflow Components:
Triggers: Events that start a workflow. These are provided by your connected Integrations (e.g., "New ticket created" from Zendesk).
Actions: Tasks performed during the workflow, also provided by Integrations (e.g., "Post draft", "Tag ticket").
Logic Nodes: Platform-native nodes for control flow and decision-making (Conditions, LLM processing).
Connections: Visual links between nodes that define the execution path.
Example Workflow:
Workflow Execution
Workflows execute asynchronously when triggered:
An event occurs (trigger fires)
The workflow starts executing
Nodes execute in the defined sequence
Each node's output becomes available to subsequent nodes
The workflow completes with a success or failure state
Execution data is tracked and displayed in the Dashboard
Workflow Initiation
How a workflow starts running is entirely dictated by the Triggers provided by your installed Integrations.
The platform is designed to be agnostic: it simply listens for signals from integrations to begin execution. Depending on which integrations you use, your workflows can be initiated in several ways:
Reactive (Event-Based): Most common in ticketing systems. Integration triggers fire based on external events like a "New Ticket Created" or "Email Received."
Scheduled: Provided by integrations like Core Utilities. These triggers use cron expressions to start workflows at specific times (e.g., "Every morning at 8:00 AM").
On-Demand (Manual/API): Some integrations project manual trigger endpoints, allowing you to start a workflow via a webhook or a specific URL call with parameters.
By installing different integrations, you expand the ways your system can react and automate.
Last updated
Was this helpful?