Skip to main content

Key Concepts


To use the Blink platform, you need to know the key concepts and terminology.


An Automation constitutes a series of actions that solves a specific use case. It is created using Steps and Sections. See Automations for more details.

Blink Co-pilot is an innovative feature that helps users to create custom automations from the ground up, using the advanced capabilities of generative AI to enhance and streamline workflows within the Blink workflow editor.

See Blink Co-pilot for more details.


Steps and Automations run when they are initiated by one of the following triggers:

Event-based: An Automation that is triggered by an event that occurs on an external service provider.
Scheduled: An Automation that is triggered at a pre-set time and can be repeated at any frequency.
On-Demand: An Automation that is triggered when selected from the Self-service portal.

See Triggers for more details.

Global Variable

Global Variables are persistent values you can define and use throughout your entire workspace and within Automations. With Global variables, users can store centralized information and pass data between Automations. See [Global variables](/docs/blink-platform/global-variables) for more details.


A workspace enables you to create data-segregated and separate workspaces for different teams across your company, as well as, for different use cases. Every team can have one or more workspaces. This enables team members to collaborate on projects and share automated workflows and resources efficiently. All the workflows of a Workspace appear on the Automations Pack page. See Workspaces for more details.

Workflow Editor

The Workflow Editor allows you to create and edit automated workflows, where you can view the run log of the workflow. The workflows can be a draft or published version.


A Section is a series of Steps within an Automation. The purpose of a Section is to create order by grouping Steps together into meaningful groups.


Steps are the building blocks of a Blink Automation. Each Step has a single goal and Steps are arranged in a logical order to complete a workflow.The user assigns input parameters, and the Step executes an Action and displays its output.

See Steps for more details


An Action is a built-in feature on the Blink platform. It is the functional element of a Step. Actions enable you to perform operations on remote systems. Typical Actions on AWS include Create a user and Delete a user, and on Github Create pull request and Create user repo. See Actions for more details.


An Integration is a connection to an external service provider that you wish to interact with and use as part of a workflow.


A Connection can be created with a vast number of cloud infrastructures and monitoring and security tools. A Connection enables actions to run on remote systems that require authorization. It is created using a token from the target system or via the personal account of the user on that system. See Connections for more details.


A Runner executes the actions defined in the Automation. By default all actions are executed from the Blink cloud; however, the user can chose to deploy a runner that will execute all of the actions from your on-premises cloud infrastructure. See Runners for more details.


The Cases feature allows you to effectively handle security incident investigations by providing detailed information and logs in one place on a single dashboard. This, in turn, allows for quicker responses to security incidents as soon as they are detected or identified. See Cases for more details.