Interested? Reach out to or the Chat in the bottom right and we will get you this application imported to your site.


When you are in production it is often the case that you are taking action. If a line goes down, a defect is found, there is an audit finding, or you are responding to an opportunity - you need to take action. All of these actions are directly tied to your production performance. This content is made to be "plugged in" to the Tulip apps you are already running. Do you have an operator terminal that has a "request help" button? What does it do? This app is the answer to that question. It helps you manage the events that occur everyday and it allows you to assign them to your team for action.

General Process Overview

Using the "Events Component" app from within one of your existing apps creates an event. This event may be a "Quality Event", "Safety Event", or any event of your choosing. Once created, it becomes available in the "Events Manager" application. From this application, you can view all of your open events, change their status, write comments, and assign them to your team.

Getting Started - Application Overview

Below is a video that walks through the application in more detail:


These applications make use of Tulip Table APIs, which will need to be set up before the app will function. You will also want to define the statuses available in the dropdown selector (in the "Events Manager" app). Once those are set up you will be able to begin using the app and managing your events.

Setting up the Tulip Table API

First, create a bot using the Tulip Table API by clicking on settings in the top right

Then Create a Bot

Grant the Bot all Scopes

This will generate credentials for you to set up your API connector. It is a good idea to save these somewhere. Leave this window open while you open up a new window.

In your other window, navigate to your connectors and select the new HTTP connector called "Table API" and edit the connection settings

Choose "Cloud Connector Host" and enter in your tulip instance as the host. Then click edit headers.

Choose Basic Auth and enter in your API Key (from the previous window) as the Username and your Secret as your Password.

Your table API is now set up!

Tweaking the app

The "Events Component" app is built for Quality Events, originally. If you want to change the event type then just look at some of the triggers to ensure that you are creating the correct event type and loading the right drop downs.

"Load Lists" will load the drop downs. Define these as you'd like to. For example, in the default setting, the app is labeling these as "Quality Events". You may want to change these to "Safety Events" depending on what app is creating the event.

Similarly, the "add new" buttons each call on whatever you decide you want the drop down category to be. Here is what the "add new" button trigger does. Notice that it is declaring itself as a "Quality Event L1". It matches the drop downs that you are loading on step enter.

When you are loading the step, there is also a "Define event type" trigger. This value will be stored in the events table to help you sort through all of the different events that are created throughout your facility.

The final step to this application is to plug it into one of your existing apps (or build your app directly onto the "Events component" app). Watch the video above to see how copying and pasting the app into another app is accomplished. Once you do that, you'll want to check that all of the transitions are in tact. For example, when you click on the "Add new" button, does it go to the the "Add new" step? Compare the transitions to the imported app if you have any questions about which buttons go where.

That's it! Reach out with any questions.

Did this answer your question?