Outputs
Modules that ship records out — HTTP endpoints, SOAP services, databases.
Every pipeline has exactly one output. It receives the records that made it through the filter chain and writes them somewhere external — an API, a SOAP service, a database table, your data warehouse.
httpRequest
POST/PUT/PATCH/… records. requestMode: batch (one request) or single (one per record). Auth, retries, success conditions.
soapRequest
Send SOAP 1.1/1.2 requests in batch or single mode. MTOM, WS-Security, retries, success conditions.
database
Insert/upsert into PostgreSQL, MySQL, or SQLite. Optional transaction wrapping, prepared parameters.
Batch vs single
HTTP and SOAP outputs accept two request modes:
batch— one request carries every record. Cheaper, fewer round trips, and the natural shape for bulk import endpoints. Default.single— one request per record. Required when the destination only accepts one record at a time, or when the URL is templated per record (/api/customers/{{record.id}}).
Database outputs always operate per-record (one query per row), but
can wrap a whole batch in a transaction with transaction: true.