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 connections, for example to post an order to an external API.
- Database connections, to insert or update records in a SQL database.
- Filesystem connections, to write files to local storage, FTP, or cloud storage.
- SOAP connections, for legacy systems.
How the Outgoing Picks Up Tasks
When the outgoing runs, it looks for tasks with the statusNew. 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 is set on the route. If sending fails, the status becomes Failed. See Tasks for the full status lifecycle.
Transformers on the Outgoing
You can add transformers 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.Filters on the Outgoing
Adding a 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 theSkipped 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.