---
title: "Slack Connector Automation"
slug: "slack-connector-automation"
updated: 2023-11-13T18:08:06Z
published: 2023-11-13T18:08:06Z
---

> ## 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.

# Slack Connector Automation

In this example, we want to monitor a Table and get notified via Slack when a new Record is added to the table.

---

## Scenario

You are a Lean Manager at a production plant, and one of your responsibilities is to evaluate upcoming 5WHY reports. Since you don't want to check every hour manually that a new report was recorded, you need an Automation that warns you about this. The company uses Slack as the standard messaging software, so you want the automation to send updates to you in Slack.

### Use case

Rather than manually configure the Connector yourself, select the Slack [quick connector](/r230/docs/how-to-set-up-quick-connectors) or [download the Slack connector from the Tulip Library](https://tulip.co/library/connectors/slack-connector/). Once you set up the connector and create a Connector Function to send a message, create an automation that fires when a new record is created in your table.

## Configure the Automation

### Set up the Slack Connector

After importing the connector to your instance, you need to configure the connector online. This requires the following steps:

1. Integrate your Slack API by following [this article](https://support.tulip.co/docs/how-to-integrate-tulip-with-slack).
2. Configure the Slack connector using the following fields and click **Test**: ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28255%29.png)

Running on: **Cloud Connector Host** Host: **hooks.slack.com** Port: **443** TLS : **Yes**

1. **Create a connector function** using a POST method.
2. Configure a Sending message Input like so:

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

Using the POST method, copy the URL of the webhook you set up in step 1. Type in a test message and click **Run** to see if the configuration was successful.

Next, create the Automation which runs the Slack connector function you just set up.

### Create the Automation Flow

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

Replicate the above automation flow with the following steps:

1. **Create a New Automation** via the **Automations** page.
2. Select **Table Record Added** for the event block and then configure the block for the intended table (ex. 5WHY report table).
3. Create an Action Block that **Sends a Message** and select the created Slack Connector function.
4. Customize your Slack text message.

And that's it! With this couple of steps we have a 24/7 automation to alert via Slack you when a new 5WHY report is created.

## Further Reading

- [Getting Started with Automations](/r230/docs/getting-started-with-automations)
- [Overview of the Automations Editor](/r230/docs/overview-of-the-automations-editor)

Check out other [Automations solutions available in the library](/r230/docs/automations-1)!

**Tulip Tables**

**Tulip Tables** are a global location to store your production data. **Tables** are made up of **Records** (rows). A single can be accessed from multiple apps or stations at the same time. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Tulip%20Tables%20Overview%20-%20Feature%20Overview(1).gif)

**Table Record**

A **Table Record** is a reference to a row in a **Tulip Table**. Table Records can be created either from the Table UI or from with an App Trigger.

To edit a record it must be loaded into a **Table Record Placeholder.**

**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)

**Connectors**

**Connectors** enable real-time connectivity between your Tulip solution and a transactional system (e.g. an ERP). The output of a Connector Function can be used in Tulip Apps, Automations, and Functions.

- **HTTP Connectors** utilize HTTP API endpoints.
- **SQL Connectors** can enable connectivity with certain SQL databases.
- **MQTT Connectors** can connect to MQTT brokers for machine monitoring.

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

**Connector Function**

**Connector Functions** are individual operations to interact with an HTTP or SQL Datasources. Connector Functions can have inputs and outputs, and can be called from: Triggers, Functions, Automations, and AI Agents.

Once pulled, data can be used throughout your applications.

**Input**

An **input** is transmission of data from a data set to a program.

**Action Block**

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