RABBITMQ n8n INTEGRATION: AUTOMATE RABBITMQ WITH N8N

This action is the cornerstone of any messaging workflow—it allows you to publish data directly into your RabbitMQ infrastructure from any point in your n8n automation. Whether you're queuing tasks for background processing, broadcasting events to multiple consumers, or feeding data into a microservices architecture, this action handles it elegantly.

The key parameters give you fine-grained control over message delivery:

• Credential to connect with: A required dropdown to select your pre-configured RabbitMQ account credentials, ensuring secure authentication with your broker.
• Operation: Set to "Send a Message to RabbitMQ" to publish data. This is the core function of the node.
• Mode: Choose between "Queue" for direct point-to-point messaging or "Exchange" for pub/sub patterns where messages are routed to multiple queues. Supports both fixed values and dynamic expressions.
• Queue / Topic: The text field where you specify exactly which queue or exchange receives the message. Must match an existing queue name in your RabbitMQ setup.
• Send Input Data: A toggle that, when enabled, automatically sends all data from the previous workflow node as the message payload. Perfect for passing along processed results without manual mapping.
• Options: Add custom properties like routing keys, message headers, delivery mode (persistent vs transient), and priority levels.

Use this action to: queue incoming webhook data for asynchronous processing; fan out notifications to multiple subscriber services; bridge external APIs with internal microservices; buffer high-volume data for controlled downstream consumption.

This action handles the critical task of cleaning up your queues by removing items that have been processed. It's particularly useful in workflows where a RabbitMQ Trigger node initiates the automation, and you need to explicitly acknowledge and remove the message after successful processing.

Here are the essential parameters:

• Credential to connect with: Required dropdown for selecting your RabbitMQ account credentials, just like the send action.
• Operation: Set to "Delete From Queue" to remove the specified item from its queue.
• Exchange: A required text field specifying the exchange name associated with the queue. This identifies where the original message was routed from.
• Type: Defines the exchange type. Options include "Fanout" (broadcasts to all bound queues), "Direct" (routes based on exact routing key match), "Topic" (pattern-based routing), and "Headers" (attribute-based routing).
• Routing Key: Required text field specifying the routing key used when the message was originally published. This ensures you're targeting the correct message for deletion.

Use this action to: acknowledge successfully processed messages in manual acknowledgment workflows; clean up queues after batch jobs complete; remove specific items based on conditional logic elsewhere in your workflow.

💡 TIP: When combining RabbitMQ Trigger nodes with the Delete From Queue action, make sure your workflow handles errors gracefully. Consider implementing error alert notifications to monitor failures. If processing fails, you may want to leave the message in the queue (or send it to a dead-letter exchange) rather than deleting it, ensuring no data is lost.