Automations - New Automation Editor

  • Updated

The + New Automation Editor is the workspace where users create and design automations in Process Studio: Automation. It functions as a visual workflow builder, allowing you to break down a manual process into clear, step-by-step actions. 

Each automation begins with a starting rule, followed by a sequence of downstream steps that define what should happen next. The final step in the chain represents the end of the automation.

The editor gives users a powerful way to analyze and automate processes in detail. Every step is represented by a node, and nodes are organized into categories that group available functions within each application. By selecting a category, an app, and then a specific action, users can build highly customizable workflows tailored to their operational needs.

The Automations Editor also provides tools for managing the entire lifecycle of an automation. Users can rename the automation, review its status, manage warnings, organize the layout, create variables, configure settings, and control versions. Additional options like screenshots, tags, and version history make it easier to maintain, audit, and improve automations over time.

On the canvas, users can drag, drop, delete, and reorganize nodes to design processes in the way that best fits their logic — making this editor both flexible and intuitive for process analysis.
 

Access the + New Automation Editor

To open the editor from the Automations List:

1. Click + New Automation.
2. Enter the automation name.
3. (Optional) Add a description.
4. Click Create.
The Automations Editor will open automatically.

Once created, you can return to the editor at any time:

1. Go to the Automations List tab.
2. Click the Name of an existing automation.

9 STEPS

1. The first step is to open Neostella: Control Center and click + New Automation

2. To access the + New Automation Editor, you have a couple of options depending on what you want to do.

If you’re creating a new automation, click + NEW AUTOMATION button.

3. Enter the automation name.

4. Add a Description.

5. When you click CREATE, the Automations Editor opens automatically so you can start building the workflow.

6. This is the Automations Editor.

7. If you’re returning to an existing automation, go to the Automations List tab and click the automation name.

8. The Automations Editor opens with that automation loaded, allowing you to review or continue editing it.

9. That's it. You're done.

https://www.iorad.com/player/2667435/Automations---Access-the---New-Automation-Editor?iframeHash=watchsteps-1&lang=en



Next step


Automation Editor Dashboard

The editor contains two main sections: the Editor Toolbar and the Editor Canvas.

Editor Toolbar:

1. Automation name
2. Automation status
3. Warnings button
4. Auto Layout button
5. Variables button
6. Settings button
7. SAVE button

8. Save dropdown:

  • Save & Publish.
  • Save Screenshot.
  • See Version History

9. Editor Canvas
10. Starting Rule Nodes
11. Nodes
12. Nodes menu
13. + Add New node button

Automation Name

The automation name appears at the top of the toolbar and is set during creation. You can update the name anytime through the automation settings.

Automation Status

The Automation Status shows the current state of the automation:

  • Draft – The automation is being built or edited and is not yet published.
  • Published – The automation is active and running.
  • Unpublished – A previously published automation has been turned off, and there is no active version.

Warnings

The editor automatically checks your automation for errors. When an issue is found, the Warnings button lights up and displays a list of specific problems. This helps quickly locate and correct issues in the workflow. 

Auto Layout

Auto Layout centers and organizes the nodes on the canvas automatically. Click Auto Layout at any time to clean up and standardize the visual arrangement of your workflow.

Variables

Variables allows to store and reuse data throughout your workflow. They make automations more dynamic by giving you flexible values that can be referenced in multiple steps.

Settings Panel

The Settings menu opens a pop-up window with three tabs: General, Application, and Tags

Save

Click Save to commit your changes. This updates the working draft of the automation. Automations autosave, so this is an optional button.

Save Dropdown Menu

The dropdown includes three additional management tools:

  • Save and Publish: Saves the automation and activates it immediately.
  • Save Screenshot: Generates a .png image of your automation and downloads it.
  • See Version History: Opens the Version Manager, which includes:

Version Manager

The Version Manager allows you to review, preview, and restore previous states of an automation. It works as a safeguard system that preserves progress and provides full visibility into how automation has evolved over time.

When you open the Version Manager, you will see a chronological list of all stored states of the automation. These are divided into Versions and Checkpoints.

3 STEPS

1. The Version Manager helps you review, preview, and restore earlier states of an automation.

Think of it as a safeguard that protects your work and gives you full visibility into how the automation has evolved over time.

2. When you open the Version Manager, you’ll see a chronological list of saved states.

These are organized into versions and checkpoints, making it easy to understand what changed and when.

3. That's it.

https://www.iorad.com/player/2665594/Automations---Version-Manager?iframeHash=watchsteps-1&lang=en



Next step

  • Versions

Versions are full backups of the automation. They are created automatically every time the automation is activated (for example, when you publish it for the first time, you get “Version 1”).

A version represents the automation at the exact moment it was turned on, including all nodes, configurations, variables, and settings. Versions are ideal for restoring significant milestones or stable builds.

Use Versions when you want to:

  • Recover a previously published automation.
  • Roll back after making major changes.
  • Compare the current workflow against a known working state.

     
  • Checkpoints

Checkpoints are lightweight save points created manually as you work inside the editor. They function as progress markers, letting you capture intermediate saving points without activating the automation.

Checkpoints help you:

  • Save progress before testing new ideas.
  • Avoid losing work if a change breaks the automation.
  • Experiment safely with node configurations or structure.

While Versions represent major milestones, Checkpoints represent working drafts created along the way.

  • What Each Entry Displays

Both Versions and Checkpoints include:

  • Creation date and time
    Helps you identify when each state was saved.
     
  • Status
    Indicates whether that state was drafted, published, deactivated, or has warnings.
     
  • Preview and Restore options
    Allows you to load or fully recover that version or checkpoint.
     

These options make it easy to understand the automation’s history and return to the state you need.

Step Panel Overview 

Automations are built using steps, represented visually as blocks on the canvas. Each step defines what happens at that stage of the workflow — whether it's performing an action, evaluating a condition, or interacting with an external system.

Multiple step types are available, and each has its own purpose and configuration options.