> 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/workato.md).

# Workato

Learn about Couchdrop's native Workato integration.

## Introduction to Workato with Couchdrop

Workato is a leading iPaaS (Integration Platform as a Service) solution for SMB and enterprise customers. iPaaS platforms like Workato enable no-code integrations between internal systems - for example, connecting Salesforce with Zendesk.

Couchdrop is a Managed File Transfer (MFT) and SFTP platform designed to simplify secure B2B file transfers. It acts as a secure file transfer gateway for Workato, allowing Workato customers to receive files via SFTP, FTP, and other MFT protocols, and then pass them into Workato for internal processing.

<figure><img src="https://391958821-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpokYqd27yrOUxIBhyvbF%2Fuploads%2FBVAn2PKXZEqVB1V4ryU0%2Fworkato-logo-1.png?alt=media&amp;token=8199085c-a75a-491d-b479-ccf1c3d6ee29" alt=""><figcaption></figcaption></figure>

## How Workato works with Couchdrop

Workato is configured in Couchdrop as an outbound connection. You link a Couchdrop folder to a Workato recipe via a webhook trigger. Any file uploaded into that folder is securely delivered to Workato, which then runs the recipe you have defined.

## Requirements

* **Admin access in Couchdrop**
* A Workato recipe with a **Webhook trigger**
* The following details from Workato:
  * **Webhook URL** generated from the trigger
  * **Authentication method** (if required for your webhook)

{% hint style="warning" %}
Workato has a **file size limit of 5 MB** for webhook payloads
{% endhint %}

## Configuration Steps

**Set Up the Recipe in Workato**

* Create a new recipe
* Select **Webhook** as the trigger
* Copy the **Webhook URL** generated for the recipe
* If authentication is enabled for the webhook, take note of the **username/password or token**

**Configure the Connection in Couchdrop**

* Add a new outbound connection
* Select **Workato** and provide:
  * A name for the integration
  * A folder name (creates a Couchdrop folder that sends files to Workato)
  * The **Webhook URL** (and credentials if required) from Workato
* Save the configuration

Any files uploaded into the Couchdrop folder will now be sent automatically to your Workato recipe.

## Common Issues

<details>

<summary>Files larger than <strong>5 MB</strong> will be rejected by Workato</summary>

Workato cannot process files that are larger than 5MB.&#x20;

</details>

<details>

<summary>Invalid authentication method</summary>

Ensure the **authentication method** in Couchdrop matches the webhook configuration in Workato.

</details>

*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.couchdrop.io/integrations/ipaas-platforms/workato.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
