Resources · n8n integration

AMQP Sender n8n integrationAutomate AMQP Sender with n8n.

Your workflows can talk to a message broker, not only to an HTTP API. The AMQP Sender n8n integration pairs one publishing node, carrying 1 operation, with the AMQP Trigger that listens on a queue or a topic. It suits teams already running an AMQP 1.0 broker such as ActiveMQ.

Try the AMQP Sender integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the AMQP Sender n8n integration actually do?

The AMQP Sender n8n integration connects a workflow to a message broker that speaks AMQP 1.0, the open protocol behind queuing and routing systems like ActiveMQ. Two nodes ship with n8n for it. The AMQP Sender publishes a raw message to a queue or a topic, once per item. The AMQP Trigger starts a workflow when a message lands on the queue or topic it listens to. Both run on the same credential, called AMQP connection.

Start with the send side. A workflow collects readings from a machine, formats them, and hands each row to the AMQP Sender, which publishes one message per item on a topic. That is the shape of template 608, which generates factory sensor data and queues it in AMQP. The consumers on the other end never talk to n8n, they read the topic.

Second shape, n8n as the producer of a live feed. Template 762 chains a node that fetches the position of the ISS with an AMQP Sender that pushes those coordinates to an ActiveMQ topic. Same pattern for a price, a stock level, or a status you already pull somewhere in a workflow.

Third shape, the mirror image. The AMQP Trigger listens on a queue and each message becomes an item you can route. From there the usual destinations take over: a row in Postgres, a document in MongoDB, a line in Google Sheets for the people who read the numbers, or a message in Slack when something needs a human.

One point deserves a pause, because it changes how you plan a project. The AMQP credential opens a connection to your broker. It is not an HTTP API, and that is a real difference: with an HTTP based app, anything the node leaves out sends you to a generic request node. Here there is nothing generic to fall back on. The AMQP Sender and the AMQP Trigger are the surface, and what they expose is what a workflow can do.

Two more things before you build. The broker is yours to run: n8n expects an AMQP 1.0 compatible one, and ActiveMQ is the example its documentation names. And n8n publishes no delivery mechanism for the AMQP Trigger, so build on the rule that does hold, the workflow must be active for the trigger to listen. If you are weighing platforms for this kind of plumbing, the n8n review covers the self-hosting question in detail.

Connect

How do you connect n8n to your AMQP broker?

  1. 01

    Get an AMQP 1.0 broker running

    This is the prerequisite the n8n documentation states plainly: install an AMQP 1.0 compatible message broker. ActiveMQ is the example it points to, and the AMQP Products list covers the other options. Both nodes talk to that broker, so nothing works until it is up and reachable from the machine running n8n. On n8n Cloud, that means reachable from the internet.

  2. 02

    Create the AMQP credential

    In n8n, open the Credentials menu and pick AMQP connection, the only authentication method these nodes accept. Four values are asked for. Hostname is the address of your message broker. Port is the port number the connection should use. User is the name of the user to establish the connection as, and Password is that user's password. On ActiveMQ, the documented default for both is admin.

  3. 03

    Set the transport and reuse the credential

    Transport Type is optional and accepts tcp or tls, nothing else. Fill it when your broker expects an explicit transport, leave it empty otherwise. A credential is created once and reused everywhere: open the AMQP Sender or the AMQP Trigger, pick it from the dropdown, and both nodes are authenticated. Save it before you leave the form.

Triggers

What starts a workflow on the listening side?

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

What you see in n8n

Configuration notes

01Set up the AMQP TriggerThe AMQP Trigger subscribes to a queue or a topic on your broker and starts the workflow when a message arrives on it. The node runs on version 1 and takes the same AMQP credential as the sender. n8n documents no delivery mechanism for it, so the rule to build on is the operational one: the workflow has to be active for the trigger to listen.

The AMQP Trigger subscribes to a queue or a topic on your broker and starts the workflow when a message arrives on it. The node runs on version 1 and takes the same AMQP credential as the sender. n8n documents no delivery mechanism for it, so the rule to build on is the operational one: the workflow has to be active for the trigger to listen.

Key parameters

  • Queue / Topic: the name of the queue or topic to listen to, written the way your broker names it.
  • Clientname: leave it empty for non-durable topic subscriptions or queues.
  • Subscription: same rule, empty for non-durable topic subscriptions or queues.
  • Container ID: passed to the RHEA backend as its container_id.
When to use it
whenever another system already publishes to your broker and you want n8n to act on those messages instead of asking that system to call n8n.
02Shape the incoming messageA message arriving from a broker is not a tidy JSON item yet. Three options on the trigger decide what the next node receives, and getting them right saves a pile of parsing steps later on.

A message arriving from a broker is not a tidy JSON item yet. Three options on the trigger decide what the next node receives, and getting them right saves a pile of parsing steps later on.

Key parameters

  • JSON Parse Body: parses the body into an object, so your following nodes read fields instead of a string.
  • Only Body: returns only the body property, dropping the rest of the message envelope.
  • Convert Body To String: converts the JSON body content from a byte array to a string, which the documentation flags as needed for Azure Service Bus.
Use cases
a queue of order events feeds a table. Turn on JSON Parse Body and Only Body, and the item lands with named fields ready to map onto columns, with no function node in between.
03Tune throughput and reconnectionThe remaining options govern how much the trigger takes at a time and what happens when the link to the broker drops. They matter on a busy queue, and they are worth setting before you put a workflow into production.

The remaining options govern how much the trigger takes at a time and what happens when the link to the broker drops. They matter on a busy queue, and they are worth setting before you put a workflow into production.

Key parameters

  • Messages per Cicle: the number of messages to pull from the bus for every cicle.
  • Sleep Time: milliseconds to sleep after every cicle.
  • Parallel Processing: processes messages in parallel rather than one after another.
  • Reconnect: reconnects automatically if the connection drops, with Reconnect Limit capping the number of attempts.
When to use it
on a queue that fills faster than the workflow drains it, raise the batch and keep Reconnect on so a broker restart does not leave the trigger silent.
Actions

What the AMQP Sender node does

The AMQP Sender node exposes one operation. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Sends a raw-message via AMQP 1.0, executed once per item

execute

What you see in n8n

Notes & use cases

The single operation takes the current item and publishes it as a raw message on your broker, once per item.

Key parameters

  • Queue / Topic: the destination on the broker, written as your provider expects it, for example topic://sourcename.something.
  • Headers: header parameters as a flat JSON object, sent as application_properties in the message meta info.
  • Send Property: the only property to send; empty, and the whole item goes out.
  • Data as Object: sends the data as an object.
Use cases
point Queue / Topic at your destination, for example topic://sourcename.something, and leave Send Property empty so the whole item goes out as the message. That is exactly how template 608 turns each row of sensor data into one message on the topic.
Need help

Need help automating AMQP Sender with n8n?

A person reads every message.

FAQ

AMQP Sender and n8n, answered

01Is the AMQP Sender n8n integration free?
Yes on the n8n side. Both the AMQP Sender and the AMQP Trigger ship with n8n, so there is nothing to install and nothing extra to pay for the nodes themselves. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow behaves the same either way. What sits outside that answer is the broker: AMQP needs an AMQP 1.0 compatible message broker, and whatever that costs you to run or subscribe to is a separate matter from n8n.
02What credentials does the AMQP Sender node need?
One credential type, called AMQP connection, shared by the sender and the trigger. It asks for a Hostname, the address of your message broker, a Port, the port number the connection should use, a User, the name of the user to establish the connection as, and that user's Password. ActiveMQ documents admin as the default for both User and Password. Transport Type is optional and accepts tcp or tls. You create the credential once in the Credentials menu and pick it from the dropdown in every workflow that needs it, rather than retyping the broker details node by node.
03What are the limits of the AMQP nodes in n8n?
The catalogue is deliberately narrow. The AMQP Sender carries 1 operation, on a single synthetic resource, and the AMQP Trigger listens without a list of events to choose from. The bigger point is structural: the credential opens a connection to your broker rather than an HTTP API, so the usual escape hatch does not apply here. With an HTTP based app you would reach for a generic request node, and there is no equivalent for a broker connection. The two AMQP nodes are the surface you work with, and running the AMQP 1.0 broker stays your responsibility.
04Does the AMQP Trigger react in real time?
Nothing in n8n's catalogue lets you claim that. The AMQP Trigger declares no delivery mechanism: not a webhook, which is a URL an outside system calls, and not polling, which is a check made on a schedule. Any promise about timing would be invented. What is documented is plain enough to work with. The node listens to AMQP 1.0 messages on the queue or topic named in Queue / Topic, the workflow has to be active for it to listen, and two options describe the pace: Messages per Cicle sets how many messages are pulled from the bus for every cicle, and Sleep Time sets the milliseconds slept after every cicle.
05n8n or Make for an AMQP broker?
It comes down to four criteria, and neither tool wins them all. Hosting first: n8n runs on your own servers with Docker or npm, or on n8n Cloud, while Make is hosted only. Data control follows from that, since a self-hosted n8n keeps messages inside your network, which matters when the queue carries production data. Cost model next: Make bills per operation, so a busy queue changes the arithmetic. Visual logic last, and that one is a matter of habit more than capability. Try both on a small workflow before committing a broker to either.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations