Key Terms and Concepts

In this topic, we share the key terms and concepts that you will meet throughout the automation documentation. We recommend you get familiar with them before moving further.

Automation Flow

To build automation, you need to create an automation flow. Automation flow is a task execution algorithm. It consists of a trigger that is followed by the chain of automation components, such as actions and conditions that allow you to build a complex multi-step execution logic, handle errors, and more.


Every automation flow starts with a trigger. Trigger defines when to run the automation. There are several types of triggers that allow you to start the automation manually, on schedule, or based on a specific event. To learn more about triggers, visit the Triggers topic.


Components are the building blocks of the automation flow. They are used to execute actions, set conditions, create branches, handle errors, and navigate the automation flow execution. To learn more about components, visit the Components topic.


Actions either get the data or send it to the data source. By chaining actions and mixing them with the other automation components, you choose what happens after the trigger sends a signal to start the automation. Actions are connection-specific, so different data sources may contain a different list of available actions. To learn more about actions, visit the Actions topic.


Automation accesses data in data sources through connections. Before building an automation flow, make sure to establish a connection to each data source involved. Skyvia offers a wide selection of pre-built connectors to provide access to all your favorite apps and data storages. To learn more about connections, visit the Connections section.


Components inside the automation flow operate with data. Scope defines which data can be accessed by a component at a specific point of the automation flow. To learn more about scope, visit the Scope chapter.


The component’s output is the data returned by the component that can be later access by other components. To learn more about output, visit the Component’s Output chapter.