---
title: "Set up quick connectors"
slug: "set-up-quick-connectors"
updated: 2023-09-25T20:37:09Z
published: 2023-09-25T20:37:09Z
---

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

# Set up quick connectors

*Learn about Quick Connectors and how to set them up.*

---

Quick Connectors in Tulip add a ready-made connector to your instance so you can quickly configure it. Quick Connectors are templates from the [Tulip Library](https://tulip.co/library-search/?content-type=connectors) that are easy to access and conviently set up so all you need to do is complete the configuration details and start connecting.

## Setting Up a Quick Connector

To set up a quick connector, navigate to the **Connectors page** under the **Apps tab**.

Select **+ Create Connector** then choose from the list of available connectors and click **+ Add**.

![Quick Connectors Set Up](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Quick%20Connectors%20Set%20Up.gif)

Note that the connector appears offline. If you open the **Connection Details**, a few boxes are already filled in.

![Quick Connectors - Edit Connection Details](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Quick%20Connectors%20-%20Edit%20Connection%20Details.png)

You must configure the remaining connector details, including any necessary Headers of Certificates, in order to get it online. Read [How to Configure a Connector](/r230/docs/how-to-configure-a-connector) for a step-by-step guide on how to accomplish this.

### Setting Up a Connector Function

Quick Connectors come with at least one Connector Function to help you get started. There are many types of connector functions performing different API Calls. For a full list of available endpoints you can connect to, refer to the appropriate organization's API documentation. If you need help creating and configuring a connector function, check out our [guide](/r230/docs/how-to-create-and-configure-an-http-connector-function).

## Further Reading

- [How To Run A Connector Function in Multiple Environments](/r230/docs/how-to-run-a-connector-function-in-multiple-environments)
- [Using HTTP Connectors in Apps](/r230/docs/using-http-connectors-in-apps)
- [Troubleshooting Connectors](/r230/docs/troubleshooting-connectors)

---

Did you find what you were looking for?

You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have faced a similar question!

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

**Header**

**Headers** represent the meta-data associated with the API **request** and **response**. They are an extra source of information for each **API call** you make and should be the first source to inspect when you encounter issues with an API to help troubleshoot issues.

**Certificate**

A **certificate** is used in place of a username and password for user **authentication**.

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

**API Call**

An **API call** is a message sent to a server asking an API to provide a service or information.