The Workflow Editor
Overview
The Workflow Editor is the core interface for building automated security workflows in Blink. It allows you to create custom workflows by combining Blink actions with actions from third-party integrations —enabling you to automate routine tasks, respond to incidents, and standardize security processes across your organization.
The Workflow Editor lets you go from idea to automation in seconds. With a visual, no-code interface and low-code flexibility when needed, you can quickly build and customize workflows to match your exact security needs. Drag and drop actions, configure triggers, and define logic—all without writing code. And when you do want to go deeper, the Builder Copilot is there to help generate and build workflows so your team can automate faster, smarter, and with confidence.
The Workflow Editor’s Interface
The following image illustrates the Workflow Editor’s Interface and it’s components
Note: This image is provided as an example of the Workflow Editor interface. The appearance of your own workflow may vary depending on how you configure your triggers, steps, and actions.
These components are as described in the following table:
| Component | Description | |
|---|---|---|
| 1 | Action Panel | This panel on the left lists all available integrations and their respective actions. You can search or scroll to explore actions and drag them into your workflow steps. |
| 2 | Builder Copilot | The ‘Builder Copilot’ icon opens Builder Copilot. By entering a prompt, the Copilot will assist in reconstructing the entire workflow to align as closely as possible with the provided instructions. |
| 3 | Test Parameters and Test Run Button | Use the “Test Parameters” button to provide inputs when testing on-demand workflows and event-based workflows. Click “Test Run” to execute the workflow in test mode, ideal for validating logic before publishing. |
| 4 | The Editor Tab and the The Run Log Tab | Switch between the ‘Editor’ for designing your workflow and the ‘Run Log’ to view past executions, inspect inputs/outputs, and troubleshoot errors. |
| 5 | ’All changes saved’ indicator and the Publish and Activate Button | The “All changes saved” indicator confirms that your workflow is being autosaved and provides access to the version history. The “Publish & Activate” button is used to publish and activate your workflow the first time. Subsequent publishes will update the version without reactivating the workflow. |
| 6 | Trigger Configuration | Triggers define the conditions under which a workflow is initiated. In this section, you can configure the trigger type selected for the workflow. In the example shown, an Event-Based Trigger is used, which activates the workflow in response to a specific event—such as a Splunk query result. |
| 7 | Steps and Actions | Steps are the building blocks of a Workflow and are arranged in a logical order to complete a workflow. Actions are added to step and performs a defined task based on integration capabilities. |
| 8 | Inline Action Panel | The ‘Inline Action Panel’ appears when adding a new step. It provides quick access to available actions, categorized by integrations, and allows for fast step configuration. |
| 9 | Outputs | Outputs refer to the final results or data generated by a workflow after it runs. These outputs can be used in various ways—for example, passed into subflows, displayed in the Self-Service Portal, or reviewed in the execution run logs for debugging purposes. |
| 10 | Toolbar | This toolbar on the right lets you zoom in/out of the canvas and quickly navigate through complex workflows. It includes reset, zoom controls, and undo/redo buttons. |
| 11 | Blink Support Chat Bot | Located in the bottom-right corner, the chat bot connects you with Blink’s support team. Use it to get help, report bugs, or ask product-related questions. |
Adding Actions to Steps
In the editor, you can add actions to a step in of the two ways.
Drag and Drop
To create a step using drag and drop, select an action from the Action panel on the left and drag it onto the canvas.
Inline Adding
Alternatively, click the icon in the center of the canvas to add a step inline. You can choose from flow control actions, subflo or use the search bar to find a specific action across all integrations.
To learn more about how steps work in the Workflow Editor—including their logic, configuration, and behavior—refer to the Steps documentation.
Workflow Editor Settings
In the top-right corner of the Workflow Editor, you can access the setting by clicking on the menu and choosing from the following
- Edit Yaml- Open the
YAMLview of your workflow and make any desired changes. - Download YAML- Download your workflow in YAML format.
- Settings - This opens the Workflow Overview page. Manage workflow-level settings such as its name, description, tags, or visibility settings.
- Version History- View and manage the workflow’s version history. You can compare changes, see timestamps, and restore previous versions if needed.
Autosave Workflow Draft
When you edit your workflow in the workflow editor, your changes are automatically saved by the system. To view the timestamp of your most recent updates, hover over the All Changes Saved link in the top-right corner. Clicking this link will open the version history of your workflow, where you can review previous versions or restore them if needed.
If the workflow fails to save—such as in the case of a lost internet connection—the autosave indicator will display as Not Saved. Hovering over this indicator will provide additional details, if available.
NOTE
To avoid conflicts or potential loss of work, please be aware that concurrent editing is restricted. If a user is currently working in the editor, others will be unable to edit the same workflow to ensure a seamless process.
Published Workflows Vs Unpublished Workflows
When managing workflows, it is essential to differentiate between published and unpublished workflow versions. Unpublished workflows represent draft versions with changes that haven not been published yet, while published workflows are finalized and ready for execution. You can identify the status of a workflow in multiple places: the workflow list, the workflow overview page, or the workflow editor.
To learn more about how to control the availability of a published workflow, check out the documentation here.
You can distinguish between a published and an unpublished workflow by looking at the:
Interactive Tutorial Guides
You can also refer to the following tutorial guides for a more in-depth understanding of how to the Workflow Editor and Workflow Run Logs works
Related Articles
Was this page helpful?