---
title: "Connect to software"
slug: "connect-to-software"
updated: 2024-09-27T18:53:37Z
published: 2024-09-27T18:53:37Z
canonical: "support.tulip.co/connect-to-software"
---

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

# Connect to software

The future of industrial software is shifting toward a landscape of interconnected tools, where multiple systems work together seamlessly. Tulip plays a key role in this ecosystem by addressing core manufacturing use cases while also integrating natively with other business systems to enable bidirectional data exchange.

Tulip uses Connectors as its primary interface for interacting with external software systems. Additionally, Tulip provides an API for remote data ingestion, extraction, and product configuration.

## [Connectors](/r230/docs/connectors-1)

Tulip’s **Connectors** offer a no-code interface for interacting with customer business systems. These systems can be accessed securely without being exposed to the cloud by deploying an [On-Prem Connector Host](/r230/docs/introduction-to-tulip-connector-hosts).

Each Connector handles authentication and configuration to connect with business systems, and also includes user-defined Connector Functions that represent discrete pieces of business logic. Connector functions can accept Inputs, return Outputs, and be integrated into apps or Automations for enhanced flexibility.

### Types of Connectors:

1. **[HTTP Connectors](/r230/docs/http-connectors)** Facilitate data transactions over RESTful API interfaces. Common integrations include systems like PLMs, WMSs, ERPs, and MESs.
2. **[SQL Connectors](/r230/docs/sql-connectors)** Enable queries on SQL databases for data retrieval and updates.
3. **[MQTT Connectors](/r230/docs/mqtt-connectors)** Send complex JSON payloads to customer-hosted MQTT namespaces, supporting IoT and real-time data exchange.

## [Tulip APIs](/r230/docs/api-documentation)

Tulip's **APIs** allow programmatic access to key components, including Tulip Tables, Stations, and Events, among others. These APIs enable seamless data interaction and workflow automation across systems.

## [Automations](/r230/docs/automations)

With **Automations**, users can configure Workflows that move data within Tulip or integrate with external systems. Automations enhance operational efficiency by enabling both data-driven actions and real-time responses.

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

**Output**

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

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

**JSON**

**JSON (JavaScript Object Notation)** is a light-weight, text-based data format that is used to store and transfer data.

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

**Station**

**Stations** are a digital representation of a physical place or device in your facility. Stations are 1:1 with **Interfaces (display devices)** running Tulip Player, but Stations can also be assigned **Edge Devices,** Tulip Vision Camera Configurations, Machines, and more.

**Events**

**Events** are **Triggers** fired by Custom **Widgets.** Users can configure as many Events as they want, and events can carry a payload of data to be used in a **Trigger.**

**Workflow**

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