> 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/managed-file-transfer/webhooks/outbound-webhooks.md).

# Outbound Webhooks

Outbound webhooks enable Couchdrop to send files and data into external applications and integration platforms as part of a workflow.

## Introduction

Outbound webhook support is currently available through Couchdrop's [iPaaS integrations](/integrations/ipaas-platforms.md), including Make, Celigo, Boomi, and Zapier.

{% hint style="info" %}
If you require a custom outbound webhook rather than an iPaaS integration, contact [Couchdrop Sales](mailto:sales@couchdrop.io) to request access.
{% endhint %}

## Using outbound webhooks

To send data from Couchdrop using an outbound webhook, connect Couchdrop to a supported iPaaS platform and configure the webhook or downstream workflow within that platform.

Supported integrations include:

* Make
* Celigo
* Boomi
* Zapier

These integrations can be used to pass data from Couchdrop into other applications and workflow systems.

## Frequently asked questions

<details>

<summary>Does Couchdrop support custom outbound webhooks?</summary>

Custom outbound webhooks are not generally available at this time. Contact [Couchdrop Sales if you need access](https://www.couchdrop.io/contact).

</details>

<details>

<summary>Which platforms can I use for outbound webhooks?</summary>

Outbound webhooks are supported through Couchdrop's iPaaS integrations, including Make, Celigo, Boomi, and Zapier.

</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/managed-file-transfer/webhooks/outbound-webhooks.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.