> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oloid-demo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Oloid Workflow: Key Concepts (TBA)

> Here are the core concepts and terminology that you would need to know to use Oloid Workflow.

## Key Concepts

* [Flows](#flows)
* [Accounts](#accounts)
* [Nodes](#nodes) : [Trigger](#trigger) [Action](#action) [System](#system)
* [Job](#job)

## Flows

Flows are automated processesbuilt by users that can span multiple applications. Each flow comprises of triggers and actions that are carried out when a trigger event is picked up.

When flows are started, they run automatically in the background to look for trigger events and carry out actions. When stopped, they cease to look for trigger events.

A Flow is represented as a tab within the editor workspace.

A Flow is a single set of connected nodes. So, a flow (tab) can contain multiple flows (sets of connected nodes).

## Accounts

For a flow to communicate with application via action and trigger nodes, it has to be authorized to interact by applications. This authorization is referred to as an account.

Accounts are not tied to a flow - a single account can be used by multiple flows.

## Nodes

A Node is the basic building block of a flow.

Nodes are triggered by either receiving a message from the previous node in a flow, or by waiting for some external event, such as an incoming HTTP request, a timer. They process that message, or event, and then may send a message to the next nodes in the flow.

A node can have at most one input port and as many output ports as it requires.

### Trigger

Triggers determine what event to listen to execute the actions described in a flow.

Trigger events can be set off in applications (Example application-ProWatch) when a certain event happens (“Door forced open” alarm is generated), when a new line is added in a file, or according to a schedule (fires at a certain time or interval).

Depending on the available API, flow can receive trigger events in real-time, or check for the occurrence of an event periodically by polling the

application.

### Action

Workflow actions are executed every time the trigger event occurs. Flows are required to have at least one action. For example, we can create a ticket in ServiceNow for the ProWatch “Door Forced Open” alarm.

### System

The System nodes are set of nodes that are the non-application specific nodes. These nodes provide utilities to manage flows. The most useful ones are inject, debug, function & switch nodes.

## Job

Each time there is a trigger event, the actions in the flow are executed. The entire flow of each trigger event through the flow is called a **job**. Jobs can be successful (when actions are executed successfully), or have errors (when an action results in an error). When an error is encountered, subsequent actions are not executed.