> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alumio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Outgoing configurations

> Outgoing configurations send data from Alumio to a destination system.

An **outgoing configuration** is the second step of a [route](/documentation/integrations/routes). It picks up [tasks](/documentation/integrations/tasks) created by the incoming and sends their data to a destination system.

## **What an Outgoing Can Do**

An outgoing configuration can send data to the same kinds of systems as an incoming. The most common ones are:

* [HTTP / API](/references/http-client) connections, for example to post an order to an external API.
* [Database](/references/database-connection) connections, to insert or update records in a SQL database.
* [Filesystem](/references/filesystem) connections, to write files to local storage, FTP, or cloud storage.
* [SOAP](/references/soap-client) connections, for legacy systems.

## **How the Outgoing Picks Up Tasks**

When the outgoing runs, it looks for tasks with the status `New`. For each task, it runs the outgoing transformers and then sends the data to the destination system.

After sending, the task status moves to `Finished`, or to `Waiting` when [Enable waiting status](/documentation/integrations/routes#route-options) is set on the route. If sending fails, the status becomes `Failed`. See [Tasks](/documentation/integrations/tasks) for the full status lifecycle.

## **Transformers on the Outgoing**

You can add [transformers](/references/transformer) to an outgoing configuration. They run on the task data right before it is sent, and are typically used for final formatting or for serializing the data into the structure the destination system expects.

Detailed documentation on individual transformers will be published separately. For the available transformers, see the [Transformers reference](/references/transformer).

## **Filters on the Outgoing**

Adding a [filter](/references/filter) to the outgoing transformers does not prevent the task from being created, since the task already exists at this point. Instead, the task is moved to the `Skipped` status and the data is not sent to the destination system.

This is useful when a task should be acknowledged in Alumio but not actually delivered, for example to skip orders below a certain amount.

## **Reusing an Outgoing**

The same outgoing configuration can be used in multiple [routes](/documentation/integrations/routes). This makes it easy to share a destination, such as a single ERP endpoint, across different integration flows.