Skip to main content

Action Outputs

When a Pipe needs to send data to a secondary destination (e.g., raise a notification), any output (except http-server) can be used under actions.

The below example, publishes "hello dolly" to a RabbitMQ queue named some-name using actions[output].amqp and then proceeds to output.write: console:

name: postact

input:
exec:
command: echo '{"message":"hello dolly"}'
raw: true

actions:
- output:
amqp:
input-field: message
queue:
name: some-name
uri: amqp://127.0.0.1//

output:
write: console

A secondary destination output must not obstruct data flow within the Pipe, i.e., it must be non-blocking.