The Workflow Editor
The Workflow Editor allows you to build and automate security workflows by adding Blink action or actions from various third-party integrations to steps. It enables users to create custom workflows that streamline security tasks, enhance efficiency, and respond to threats or incidents in a consistent and automated way. Through the workflow editor, you can easily select predefined actions, configure triggers, and set up automated responses, all without needing extensive coding knowledge.
-
Click on any Workflow in the Workflow Pack to open it in the Workflow Editor. In the editor, you will see the action panel on the left side, which contains all available integrations and their corresponding actions. You can search for a specific integration or drag and drop an action into a step. Alternatively, you can click directly on a step to select and add an action from the panel.
-
You will be directed to the workflow editor, where you can find two tabs at the top of the screen. The “Editor” tab is the default tab for editing the selected workflow and the “Run Log” tab to access the workflow’s Run Logs.
Autosave Workflow Draft
When you make edits to your workflow steps in the workflow editor, the system will save your changes automatically. To check the timestamp of your latest modifications, simply hover over the All Changes Saved link located in the top-right corner. Clicking on this link will open the workflow’s version history, allowing you to review or restore its previous versions.
If workflow fails to save, such as during a lack of internet connection, the autosave indicator will display not saved. Hovering over the indicator will provide additional details, if relevant.
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’s essential to differentiate between published and unpublished versions. Unpublished workflows represent draft versions with changes that haven’t 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.
How to Identify an Unpublished Workflow
- Workflow Page: A yellow dot appears on the left-hand side of any workflow with unpublished changes. This serves as a quick visual indicator that a newer draft version exists.
- The Workflow Overview Page: To view more details, select the workflow and click the Overview button. On the Workflow Overview page, you’ll see a notification at the bottom highlighting that unpublished changes exist. Additionally, you’ll find an option to view the latest draft of the workflow for further details.
- The Workflow Editor: Within the Workflow Editor, hover over the Published button. If there are unpublished changes, a notification will appear, stating that certain changes are not included in the published version. You can also access the Version History to review all changes made to the workflow.
Interactive Tutorial Guide:
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
Was this page helpful?