---
title: "Automations editor"
slug: "automations-editor"
updated: 2025-12-02T16:56:49Z
published: 2025-12-02T16:56:49Z
canonical: "support.tulip.co/automations-editor"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Automations editor

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

## Navigation

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](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Editor%20Annotated.png)

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](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Create%20Event.png)

### Initiate an automation - event types

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 Updated** Requires a selection a specific machine activity field.

- On any machine
- On specific machine type
- On specific machine

**Machine Attribute Changed** Requires a selection a specific machine attribute.

- On any machine
- On specific machine type
- On specific machine

**Table Row Added** Requires a selection a specific table.

**Table Row Updated** Requires a selection a specific table.

- On any field in table or a specific field

**Table Row Deleted** Requires a selection a specific table.

**On a schedule or timer** Allows you to select specific times at the following intervals:

- Hours
- Days
- Weeks

**Insight detected (note: deprecated for new users as of r317)**

Table Record

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

Machine Activity/Attribute Changed

For Machine Activity/Attribute changes, any machine-based information(i.e. state) called in the automation will be based on **the time of automation execution not when the automation event kick-off occured**.

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](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Event%20Details1.png)

#### Event filtering

When configuring an automation event for table record updates, use event filtering to specify which fields from the selected table need to be updated in order for the automation to run.

![event-filtering](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/event-filtering.png)

There are three different logic blocks you can use:

- Event Blocks - Initiates the automation logic to run ![Automations Event Block](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Event%20Block.png)
- Action Blocks - Manipulates data or alerts users, this includes reading/writing to tables, running connector functions, and more ![Automations Action Block](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Action%20Block.png)
- Decision Blocks - Conditional logic that always has 2 branches stemming from it–”yes” and “no” ![Automations Decision Block](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Decision%20Block.png)

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

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](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Create%20New%20Logic%20Block.png)

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:

#### Action blocks

![Automations Action Config Ex](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Action%20Config%20Ex.png)

#### Decision blocks

![Automations Decision Config Ex](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Decision%20Config%20Ex.png)

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](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Rearranging%20Logic%20Blocks.gif)

### Publish

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](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Logic%20Block%20Error.png)

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](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Publish%20Modal.png)

### Test

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](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/r280%20Test%20Automation%20Modal.png)

### View/edit

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](/r230/docs/how-to-use-automations-versions). You can also add, remove, or duplicate blocks and modify their configuration.

## Further reading

- [Automations overview](/r230/docs/getting-started-with-automations)
- [How to Use Automations Run History](/r230/docs/how-to-use-automations-run-history)
- [How to Use Automations Versions](/r230/docs/how-to-use-automations-versions)

**Automations Editor**

Visual editor for managing and creating **automations** within the Tulip platform.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Glossary/Automations%20Editor.png)

**Automation**

**Workflow** that performs tasks in the background, without an interface. Automations run logic every time an **event** occurs.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Glossary/Automations1.gif)

**Workflow**

General term to describe a series of logic in Tulip including **apps** or **automations**.

**Logic Editor**

Visual editor for managing and creating logic for **Automations**.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Glossary/Automations%20Logic%20Editor.gif)

**Logic Block**

*Event*, *action*, or *decision* in an **Automation**.

**Table Record Field**

**Table Record Fields**are single columns within a **Tulip Table.**

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Table%20Record%20Field(1).gif)

**Run**

Occurs each time an event is invoked in an **automation**.

**Action Block**

Type of **logic block** that manipulates data or alerts users.

**Decision Block**

Type of **logic block** that holds conditional logic. This logic block always has 2 branches coming out of it labeled “yes” and “no”.