> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/integrations/ipaas-platforms/celigo.md).

# Celigo

Learn about Couchdrop's native Celigo integration.

## Overview

Celigo is an Enterprise Integration Platform as a Service (iPaaS) used to connect applications and automate data between systems.

Couchdrop can act as the secure file transfer layer for Celigo. While Celigo handles application integration and downstream processing, Couchdrop manages how files enter the workflow through SFTP, FTP, and other supported transfer methods.

Couchdrop can also apply file transfer security and governance controls, including [Transfer Shield](/security-and-governance/transfer-shield-dlp.md), before files are passed into Celigo.

## How Celigo works with Couchdrop

Celigo is configured in Couchdrop as an outbound connection.

The connection links a Couchdrop folder to a Celigo flow using a webhook listener. Files uploaded to the folder are sent to the webhook URL, where Celigo receives them and triggers the configured flow.

## How to connect Celigo

{% hint style="warning" %}

#### Before you start

To connect Celigo to Couchdrop, you will need:

* Administrator access to Couchdrop
* A Celigo flow with a **Webhook listener**
* The **Public URL** generated for the webhook
* A **Username** and **Password** configured using **Basic** authentication
* The **Content Type** accepted by the webhook
  {% endhint %}

{% stepper %}
{% step %}

### Create a webhook listener in Celigo

In Celigo, create a flow and add a **Source** using **Webhook**.

Name the webhook and continue to its configuration.

Under **Secure the Listener**, select **Basic** and configure a **Username** and **Password**. Couchdrop will use these credentials when sending files to Celigo.

Generate the **Public URL** using the plus button beside the URL field, then save your configuration.

Keep the **Public URL**, **Username**, and **Password** available for the Couchdrop connection.
{% endstep %}

{% step %}

### Create the Celigo connection in Couchdrop

In Couchdrop, add a new outbound connection and select **Celigo**.

Configure the connection with:

* **Name** — A name used to identify the Celigo connection.
* **Folder name** — The Couchdrop folder that will send files to Celigo.
* **Webhook URL** — The **Public URL** generated by Celigo.
* **Content Type** — The content type expected by the Celigo webhook (application/json, application/xml, or application/x-www-form-urlencoded).
* **Username** — The username configured for Basic authentication.
* **Password** — The corresponding password.

Save the connection.
{% endstep %}

{% step %}

### Send files to Celigo

Upload a file to the Couchdrop folder created for the Celigo connection.

Couchdrop will send the file to the configured webhook URL, allowing the Celigo flow to receive and process it.
{% endstep %}
{% endstepper %}

## Frequently asked questions

<details>

<summary>Why use Couchdrop with Celigo?</summary>

Couchdrop provides the managed file transfer layer around Celigo. External partners and systems can deliver files using supported transfer methods such as SFTP and FTP, while Celigo remains focused on application integration and downstream processing.

</details>

<details>

<summary>Can Couchdrop apply controls before files reach Celigo?</summary>

Yes. Couchdrop can apply security and governance controls such as Transfer Shield before files continue into the Celigo workflow.

</details>

<details>

<summary>Does Celigo need to be exposed directly to external partners?</summary>

No. Partners can transfer files through Couchdrop rather than connecting directly to Celigo. Couchdrop then sends the files to the configured Celigo webhook.

</details>

<details>

<summary>What happens if the content type does not match?</summary>

The **Content Type** configured in Couchdrop needs to be accepted by the Celigo webhook listener. If the request uses an unsupported or unexpected content type, Celigo may reject or incorrectly interpret the request.

</details>

<details>

<summary>Are there file size limits?</summary>

Celigo applies size limits to webhook processing. Current Celigo webhook functionality supports paging records into pages of up to 5 MB, and newer webhook configurations can accept larger requests in specific configurations. Check the limits for your Celigo webhook configuration before sending larger files.

</details>

## Common Issues&#x20;

<details>

<summary>File size limit of 5MB</summary>

Celigo has a file size limit of 5MB. This means files larger than 5MB will be rejected and will not be processed.

</details>

<details>

<summary>Invalid content type</summary>

Make sure the **Content Type** in Couchdrop matches what your Celigo webhook listener is configured to accept

</details>