Getting Started with Automations
  • 24 Apr 2024
  • 4 Minutes to read
  • Contributors

Getting Started with Automations


Article summary

New to automations and not sure where to start? You’ve come to the right place!

Automations is a new Tulip feature that allows you to automate and expedite Workflows in your processes. This article will cover the basics of what automations are, how you build them, and the capabilities for specific use-cases.

Note on Beta

“Beta Versions” means versions of new functionality for the Tulip Products or Services and/or Updates that are not generally commercially available and which Tulip may pre-release to all or some of its customers for which customers are expected to report any bugs they encounter or any changes such customers would like to see before the general release.

User Permissions

Existing roles are authorized for the Automations Page as defined below. All roles are able to create, archive, and edit an automation from the Automations page.

  • SysAdmin
  • Account Owner
  • Workspace Owner
  • Administrator

Similar to apps, any role can view automations. If you need to change access permissions for a user, you can do so via the Account Settings page.

Automations Page Overview

Let’s take a tour of the Automations page to get familiar with the layout and information available. To get to the automations page, click the Automations tab in the top navigation bar.

At the start your page may be blank, but soon your page will be full of all the automations you need to efficiently run through your process. Let’s break down what this page looks like:

Automations Page Annotated

The automations page reveals information for each automation in your instance, organized by the date they were created. The status of the automation indicates where it’s active or inactive. Click the toggle button to change the status. Finally, the “...” button to the right of each automation allows you to duplicate or archive the automation.

NOTE

You cannot delete an automation for traceability purposes.

To view archived automations, click the “...” in the top right corner of the page and select View Archived Automations.

Archived Automation

How To Write Your First Automation

To start writing your first automation, click + Create Automation in the top right corner of the automations page.

Welcome to the Automations Editor! First, give your automation a name by clicking on Untitled Automation in the top left corner. Be sure to name it something identifiable that states the action or the process it completes.

Optimizing Automations for Your Shop Floor

In order to get the most out of automations, it’s important to know the capabilities and integrations possible with this feature so you know exactly what’s possible. Automating processes should create streamlined workflows in order to allocate time and resources towards other, more manual tasks. To accomplish this, let’s go over some use-cases of how to incorporate automations into your shop floor.

  1. Dispatch work to the right people to minimize downtime.
    Automation Use-cases Graphics

  2. Process data and update records in your system.
    Automation Use-cases Graphics 1

  3. Get ahead of requests to keep production running smoothly.
    Automation Use-cases Graphics 2

  4. Ensure procedures are followed and stay up to date with compliance.
    Automation Use-cases Graphics 3

  5. Respond to quality issues quickly and maintain accurate records.
    Automation Use-cases Graphics 4

Integrations

You can integrate Machines with automations, and soon you’ll be able to use Connector Functions as well. Link Tables so you can get a notification when a row updates. Coming soon, you’ll also be able to set alerts for Analytics (Insight Detected) and run the automation on a schedule or timer. The integrations with automations allow you to customize your experience and take full advantage of the Tulip platform.

Collecting Data

Collect data on your automations with versions and run history features. These tools give insights on the number of automation versions created and the performance of the automation itself.

Versions are iterations of an automation. Each time you edit an automation, it creates a new version and archives the former one. View the current version number from the Automations main page or the Version History page for a specific automation.
Automations - Version History

Run history is the record of events an automation has encountered. A Run refers to each time an event is invoked and an action is fired. The run history page gives details such as the version per firing, the status, the start time, and the end time.
Automations - Run History

Now that we’ve covered the basics of Automations, you can get started creating your own for your specific processes.

Further Reading


Was this article helpful?