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

# Boomi

Learn about Couchdrop's native Boomi integration.

## Overview

Boomi is an 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 Boomi. While Boomi 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, before files are passed into Boomi.

## How Boomi works with Couchdrop

Boomi is configured in Couchdrop as an outbound connection.

The connection links a Couchdrop folder to a Boomi process using its web service endpoint. Files uploaded to the folder are sent to Boomi, where the deployed process receives and processes them.

Boomi processes exposed through its API can use a **Web Services Server connector** to receive these requests.

## How to connect Boomi

{% hint style="warning" %}

#### Before you start

To connect Boomi to Couchdrop, you will need:

* Administrator access to Couchdrop
* A Boomi process with a **Web Services Server connector** deployed to an environment
* The **Environment API URL** for the Boomi environment
* The **Endpoint (Simple URL Path)** for the deployed process
* A **Username** and **Token** from **Shared Web Server > User Management**

Boomi public runtime clouds have a **5 MB maximum web service request input size when using Low Latency mode**.
{% endhint %}

{% stepper %}
{% step %}

### Configure and deploy your Boomi process

In Boomi, create or configure the process that will receive files from Couchdrop using a **Web Services Server connector**.

Deploy the process to the Boomi environment that Couchdrop will send files to.

Copy the following details from your Boomi environment:

* **Environment API URL**
* **Endpoint (Simple URL Path)**
* **Username**
* **Token**

You will use these values when creating the connection in Couchdrop.
{% endstep %}

{% step %}

### Create the Boomi connection in Couchdrop

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

Configure the connection with:

* **Name** — A name used to identify the Boomi connection in Couchdrop.
* **Folder name** — The Couchdrop folder that will send uploaded files to Boomi.
* **Environment API URL** — The API URL for your deployed Boomi environment.
* **Endpoint** — The Simple URL Path for the Boomi process.
* **Username** — The username configured for the Boomi web service.
* **Token** — The corresponding authentication token.

Save the connection.
{% endstep %}

{% step %}

### Send files to Boomi

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

Couchdrop will send the file to the configured Boomi endpoint, allowing the deployed Boomi process to receive and process it.
{% endstep %}
{% endstepper %}

## Frequently asked questions

<details>

<summary>How does Couchdrop send files to Boomi?</summary>

Couchdrop sends files to a deployed Boomi process through its configured web service endpoint.

</details>

<details>

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

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

</details>

<details>

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

No. External partners can transfer files through Couchdrop, while Couchdrop handles the file transfer boundary and sends files onward to the configured Boomi process.

</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/boomi.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.