Skip to main content
The RabbitMQ Sink command (Command Type: 1200) sends the job result to the sink service, which publishes it to a RabbitMQ exchange on your organization’s configured RabbitMQ.

Command Type

Command Type ID: 1200

Parameters

The published payload is the step’s job result; there is no data parameter. Shape the result with Parse commands before the sink.

How It Works

  • The command runs inside the step’s command chain and hands the result to the Stream sink service, which publishes it to RabbitMQ.
  • The step’s result still goes through orchestration, so child steps and miss tolerance keep working.
  • RabbitMQ connection details come from your organization’s sink configuration, not from the command.

Usage Examples

Publish to a Topic Exchange

Publish with Headers

Use Item State in the Routing Key

Best Practices

  • Place at End of Workflow: Use the sink as the final command of the step whose results you deliver
  • Match the Exchange Type: exchangeType must match the exchange declared in RabbitMQ
  • Use Descriptive Routing Keys: Use clear routing keys for message organization
  • Verify Consumption: Confirm messages are being consumed successfully

Troubleshooting

Messages Not Being Consumed

  1. Verify Exchange Exists: Ensure the exchange exists with the same exchangeType
  2. Check Routing Key: Verify the routing key matches your consumer bindings
  3. Check Sink Configuration: Ensure a RabbitMQ sink configuration exists for your organization
  4. Review Payload: Verify the job result shape matches consumer expectations