Overview of the Automations Editor
  • 14 Jun 2024
  • 4 Minutes to read
  • Contributors

Overview of the Automations Editor

Article summary

Learn to navigate the Tulip Automations Editor to build your automations just how you want.

To enter the Automations Editor, you can create a new Automation via the + Create Automation button on the Automations Page. You can also edit an existing automation by clicking on one from your list and then selecting the Edit button.

How to Use the Editor

At the top of the page, name your automation by clicking on the Untitled Automation text.

Automations Editor Annotated

Below the title is the workspace where you build and edit the automation Workflow.

To the right of the workspace is the Logic Editor, which changes based on your selection in the workspace. It will either show the run history of the automation if no selection is made, or it will show the details of the selected Logic Block.

Automations Create Event

Automations begin with an event which can be a table Field change, a machine output, or a timer occurrence. Events initiate the automation logic to Run. When you create a new automation, there are seven options for a new event:

  • Machine Activity Changed
  • Machine Attribute Changed
  • Table Row Added
  • Table Row Updated
  • Table Row Deleted
  • Insight Detected
  • On a schedule or timer
Table Record

For Table Record Added or Updated, a CSV upload to a table will not cause an automation to fire.

After selecting the type of event you want to automate for, the appropriate event block appears in the workspace and the Logic Editor allows you to configure the event or change the event type.

Automations Event Details1

There are three different logic blocks you can use:

  • Event Blocks - Initiates the automation logic to run
    Automations Event Block

  • Action Blocks - Manipulates data or alerts users, this includes reading/writing to tables, running connector functions, and more
    Automations Action Block

  • Decision Blocks - Conditional logic that always has 2 branches stemming from it–”yes” and “no”
    Automations Decision Block

Each logic block has different details and configuration needs. You don’t need to include every type of logic block in order to run a successful automation. For example, automations can run without an action firing. If an event sends an alert when temperature exceeds X and RPM is above Y, it would run every 5 minutes whether or not those conditions are satisfied.


Create new logic blocks by clicking the + button on any connecting line of the flow. From here you can:

  • Add a new action block
  • Add a new decision block
    Automations Create New Logic Block

To configure the logic for each block, click on it then edit in the logic editor pane. Here are some example configurations for logic blocks:


Automations Action Config Ex


Automations Decision Config Ex

To duplicate or delete a block, use the icons in the top right corner of the logic editor after selecting a block. Duplicating will automatically copy the logic as well.

If you want to rearrange the order of the logic blocks, you can click and drag them to different parts of the workflow.

Automations Rearranging Logic Blocks


To publish an automation, click the Publish button at the top right of the editor screen. Only valid automations can be published. The publish button is disabled if the automation:

  • Does not have at least 2 blocks (the event block plus an action or decision)
  • All blocks have been configured correctly. Blocks that have not been completely configured display a warning icon.
    Automations Logic Block Error

Once clicking the Publish button, a modal displays where you can:

  • Toggle the active status of the Automation. This is set to "Active" by default.
  • Cancel to return to the editor
  • Publish the automation
    Automations Publish Modal


Users can test their automation prior to publishing it. Like publishing, only valid automations can be tested. The test button is disabled if:

  • Does not have at least 2 blocks (the event block plus an action or decision)
  • All blocks have been configured correctly. Blocks that have not been completely configured display a warning icon.

You can select the environment (production, testing, development) that the connector should run in.
r280 Test Automation Modal


You can edit all aspects of an Automation after you publish it, including the name, the event block, and any existing action or decision blocks. Any edits you make creates a new Version. You can also add, remove, or duplicate blocks and modify their configuration.

Further Reading

Was this article helpful?