---
title: "Connector limits"
slug: "connector-limits"
updated: 2025-09-26T20:25:27Z
published: 2025-09-26T20:25:27Z
canonical: "support.tulip.co/connector-limits"
---

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

# Connector limits

*Learn best practices and limits for using connectors to efficiently scale them in production environments.*

## Limits

| Common questions |  |
| --- | --- |
| Is there a limit on number of Connectors? | No. |
| Is there a limit on number of Connector Functions on a Connector? | No. |
| What are the limits on the payload size for a request and a response? | The maximum payload size depends on the type of Connector Host used. Each connector host type has the following default size, and they can be configured: - Cloud connector host: 20 MB - On-premise connector host: 50 MB - Edge device connector host: 50 MB |
| For a SQL Connector, is there a limit on the number of records returned by a query? | The limit of number of rows returned on a SQL Connector Function is a result of the maximum payload size for the Connector Host used. |

## Timeouts

| Parameter | Description | Default Timeout |
| --- | --- | --- |
| Connector timeout | Controls how many seconds the connector host will wait before timing out a connector function (either HTTP or SQL) or connection by throwing a timeout error. | 20 seconds (configurable) |
| Connector OAuth 2.0 timeout | Controls how long the Tulip platform will wait when authenticating with OAuth 2.0 before throwing a timeout error | 30 seconds (configurable) |

## Further reading

- [Connector Hosts](/r230/docs/connector-hosts)
- [On-Premise Connector Hosts](/r230/docs/overview-of-on-premise-connector-hosts)

---

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 solved a similar topic!

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

**Connector Host**

Tulip **Connector Hosts** are designed to allow your Tulip Apps to interface with external systems such as databases, APIs, and machines. **On-Prem Connector Hosts** sit within your network and allow Tulip to interface with SQL databases and APIs that aren't accessible to the cloud.