Resources · n8n integration

RabbitMQ n8n integrationAutomate RabbitMQ with n8n.

A queue stops being a black box the moment n8n sits on both ends of it. The RabbitMQ n8n integration gives you 2 node operations, publishing a message and clearing one from a queue, plus a trigger that consumes a queue and starts one workflow run per message.

Try the RabbitMQ integration on n8nSee the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does a RabbitMQ n8n integration actually cover?

RabbitMQ is a message broker: one system drops messages into a queue, another picks them up when it is ready to work. The n8n integration puts a workflow on either side of that queue. The RabbitMQ node publishes a message to a queue or to an exchange, and it can also delete a message from a queue. The RabbitMQ Trigger plays the consumer role, turning each message that arrives on a queue into a workflow execution.

Start with the pacing problem. A workflow that collects data on a schedule often runs faster than whatever has to store or process the result. Publishing each result to a RabbitMQ topic lets the second workflow drain the queue at its own speed before writing rows into Postgres. n8n's own template library shows the shape with satellite position updates pushed to a topic (workflow 844).

Then there is routing. n8n's own template library shows client onboarding events published to RabbitMQ with a routing key, picked up by a small consumer workflow that shapes the record with a Code node and sends the alert through Gmail (template 15316). One workflow publishes, one purpose-built consumer reacts, instead of a single workflow growing branch after branch.

The third case is fan-out. A fanout exchange copies one published message to every queue bound to it, so a single "order paid" message can feed an archiving workflow that writes to MySQL and, in parallel, a workflow that prepares the customer email. You publish once. The broker handles the duplication.

Now the limits, stated plainly. The node carries 2 operations and nothing more: no queue listing, no user administration, no reading of a message outside the trigger. The credential opens an AMQP connection to the broker rather than an HTTP API, so the usual escape hatch of adding an HTTP Request node does not apply here. What the node and the trigger expose is what you get from n8n, and the rest stays on the RabbitMQ side.

That makes this a good fit for teams already running a broker and looking to put automation around it, less so for teams hoping n8n will administer RabbitMQ for them. If queues are new territory for the people who will maintain these workflows, the n8n training covers the trigger and credential mechanics that this page assumes.

Connect

How do you connect n8n to a RabbitMQ broker?

  1. 01

    Point n8n at the broker

    In n8n, open the Credentials menu and create a RabbitMQ credential. The only supported method is a user connection, so start with the address of the broker itself: Hostname takes the machine that runs RabbitMQ, and Port takes the port the connection should use. A credential is created once here and then offered in the dropdown of every RabbitMQ node and trigger you add afterwards.

  2. 02

    Fill in the login and the virtual host

    User is the account the connection logs in as, and Password its password. RabbitMQ ships with guest as the default user and guest as its password, and recommends a different user in production. Vhost is the virtual host the connection should use, a way of splitting one broker into isolated spaces; the default virtual host is /.

  3. 03

    Turn on SSL when the broker expects it

    The SSL toggle decides whether the connection is encrypted. With it on, Passwordless says whether the certificate connection uses the SASL mechanism EXTERNAL or no password at all. Turned on, it asks for the Client Certificate and the Client Key pasted as text, plus the Passphrase. CA Certificates takes the text of the CA certificates to trust.

Triggers

What does the RabbitMQ Trigger listen to?

RabbitMQ Trigger is the node that starts a workflow when something happens in RabbitMQ. Activate the workflow and every event it receives becomes one execution.

What you see in n8n

Configuration notes

01Configure the RabbitMQ TriggerThere is no event list to tick here. The trigger consumes one queue and produces one execution per message that arrives on it. Save the workflow, then activate it: an inactive workflow does not listen.

There is no event list to tick here. The trigger consumes one queue and produces one execution per message that arrives on it. Save the workflow, then activate it: an inactive workflow does not listen.

Key parameters

  • Queue / Topic: the name of the queue to read from, typed exactly as it exists on the broker, for instance orders.created.
  • Delete From Queue When: found under Options, it sets when the message is acknowledged, which decides whether it leaves the queue as soon as n8n receives it or once the run is finished.
  • Parallel Message Processing Limit: the maximum number of executions running at the same time. Use -1 for no limit.
When to use it
whenever another system already publishes to RabbitMQ and you want n8n to be the consumer, instead of exposing an n8n URL to that system. Acknowledging after the run keeps a failed execution from silently dropping the message.
02Shape the messages the trigger returnsA message arrives as raw content. The Options collection decides what n8n hands to the next node and whether the queue is created on the fly.

A message arrives as raw content. The Options collection decides what n8n hands to the next node and whether the queue is created on the fly.

Key parameters

  • JSON Parse Body: parses the body into an object, so the fields become usable as {{ $json.field }} downstream instead of one string.
  • Only Content: returns just the content property, leaving out the delivery envelope that surrounds it.
  • Content Is Binary: saves the content as binary, the setting for messages carrying a file rather than text.
  • Assert Queue, Durable, Exclusive, Auto Delete Queue: check the queue exists before reading, keep it across broker restarts, scope it to this connection, or drop it once no consumer is left.
  • Binding, Arguments, Headers: add a binding to the queue, and pass arguments or headers along with it.
When to use it
turn on JSON Parse Body and Only Content for a publisher that sends JSON, and keep Durable on for a queue that must survive a broker restart.
Actions

What can the RabbitMQ node do?

The RabbitMQ node exposes 2 operations. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Send a Message to RabbitMQ

sendMessage

What you see in n8n

Notes & use cases

Publishes a message to a queue or to an exchange.

Key parameters

  • Queue / Topic: the name of the queue to publish to.
  • Exchange and Type: publish through an exchange instead, typed direct, topic, headers or fanout depending on how the broker should spread the message.
  • Routing Key: the routing key the exchange matches against.
  • Send Input Data: sends the incoming item as JSON; turn it off and write the payload yourself in Message.
  • Alternate Exchange: under Options, an exchange that catches messages this one cannot route to any queue.
Use cases
hand each scraped record to a consumer that stores it, or publish an "invoice paid" message a billing workflow reads later.
02

Delete From Queue

deleteMessage

What you see in n8n

Notes & use cases

Removes a message from a queue instead of publishing to it, so the node works against an existing entry rather than adding one.

Key parameters

  • Queue / Topic: the queue the operation acts on.
  • Exchange and Type: name the exchange when the target is reached through one, with the same direct, topic, headers and fanout choices.
  • Routing Key: the routing key attached to the message.
  • Message: the message the operation targets, often built from the trigger with an expression such as {{ $json.content }}.
Use cases
clear an entry a workflow has already handled elsewhere, or drop a message that a validation step just rejected.
Need help

Need help automating RabbitMQ with n8n?

A person reads every message.

FAQ

RabbitMQ and n8n, answered

01Is the RabbitMQ n8n integration free?
Yes, on the n8n side. Both the RabbitMQ node and the RabbitMQ Trigger ship with n8n, so there is nothing to install and no add-on to buy, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow built in one runs identically in the other. What you do need is a RabbitMQ broker to connect to, which you host and pay for yourself according to wherever it runs. The n8n credential does not provision a broker and does not change anything about how yours is billed.
02What credentials does the RabbitMQ node need?
One credential type, called a user connection, shared by the node and the trigger. It asks for the Hostname of the broker, the Port, the User and Password the connection logs in as, and the Vhost, the virtual host the connection should use, which defaults to a single slash. RabbitMQ creates a guest account with guest as its password, and recommends a different user in production. An SSL toggle adds the encrypted variant: Passwordless, Client Certificate, Client Key, Passphrase and CA Certificates, all pasted as text. Create it once in the Credentials menu and every RabbitMQ node reuses it.
03What are the limits of the RabbitMQ node in n8n?
The node has 2 operations, sending a message and deleting one from a queue. Everything else about broker administration stays outside n8n: no listing of queues, no user management, no metrics, no purge. The trigger reads one queue at a time, so several queues means several workflows. The important part: the credential opens an AMQP connection to the broker rather than an HTTP API, so adding an HTTP Request node is not a workaround for a missing operation the way it is with most app nodes. If it is not in the node or the trigger, it does not happen from n8n.
04Does the RabbitMQ Trigger react in real time?
That is the one thing n8n does not spell out for this trigger. Its documentation describes neither how the delivery reaches n8n nor any interval, so no latency figure belongs on this page. What is documented: the trigger listens on the queue named in Queue / Topic, the workflow has to be active for that listening to happen, and each message produces one execution. Two Options settings are worth setting deliberately: Delete From Queue When, which controls at what moment the message is acknowledged, and Parallel Message Processing Limit, which caps how many executions run at once.
05n8n or Make for RabbitMQ?
It depends on where the broker lives and who owns the data path. Make is hosted by Make, with no self-hosting option, and it bills per operation, which matters when a queue can produce thousands of messages a day and each one becomes an operation. n8n can be self-hosted with Docker or npm, or used on n8n Cloud, and the same workflow works in both. A broker that sits inside a private network is often easier to reach from an n8n instance on that same network. Make brings a visual builder that many teams find quicker to read. No bad answer, just different constraints.
Same platform

Other docs you might need on this stack.

Browse all integrations