Skip to main content
Sink commands deliver your step’s results to an output destination. You add a sink command inside a step’s Blueprint, usually as the last command of the last step, and it runs as part of the command chain like any other command.

Available Commands

RabbitMQ Sink

Publish to a RabbitMQ exchange (ID 1200)

Kafka Sink

Publish to a Kafka topic (ID 1201)

S3 Sink

Upload to an S3 bucket (ID 1202)

Managed Bucket Sink

Write to the Bringits-managed bucket (ID 1203)

MongoDB Sink

Write to a MongoDB collection (ID 1204)

How Delivery Works

  • RabbitMQ, Kafka, S3 and MongoDB sinks hand the job result to the Stream sink service, which delivers it to the destination configured for your organization. Connection credentials are part of that sink configuration, not of the command.
  • Managed Bucket Sink writes directly to the managed bucket; it needs no destination configuration.
  • Sinking does not replace the normal flow: the step’s result still goes through orchestration, so child steps, deduplication and miss tolerance keep working.
A sink command delivers what the step produced. Use Parse commands before the sink to shape the payload, and dataSegmentToSend (Kafka, S3, MongoDB) to choose between the full job result ("fullData") and its data field ("data").

Blueprint Format

Every command in a Blueprint is an object with id, type and params. For sinks, type is "SINK":

Best Practices

  • Place at the end of the workflow: use a sink as the final command of the step whose results you want delivered.
  • Test first: run the step from the test panel and check the destination before activating the project.
  • Shape before sending: keep sink params minimal and do the transformation in Parse commands.

Troubleshooting

  • Nothing arrives: check that a sink configuration exists for your organization and the sink type, and that the destination (exchange, topic, bucket, collection) exists.
  • Wrong payload: check dataSegmentToSend and the Parse commands before the sink.
  • RabbitMQ routing: verify exchangeType and routingKey match your consumer bindings.