Resources · Make integration

RabbitMQ Make integrationAutomate RabbitMQ with Make.

Need other apps to drop messages into RabbitMQ without a single line of glue code? The RabbitMQ Make integration gives you 2 action modules, one for exchanges and one for queues. This guide shows ops and dev teams how to connect a server and ship a first scenario.

Try the RabbitMQ integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the RabbitMQ Make integration do for you?

It lets a Make scenario (the automation you build, a chain of bricks called modules) drop messages into your RabbitMQ server. RabbitMQ is a message broker, a kind of post office between your programs: a queue is a mailbox where messages wait until one program collects them, and an exchange is a sorting desk that copies a message into every queue linked to it. Make only posts; nothing here reads messages.

Hand work to your back end. A signed contract lands in your CRM, and Send To Queue drops a job straight into the queue your billing worker already listens to. Your developers keep their consumer code; Make just feeds it.

Broadcast one business event. When an order ships, Send To Exchange publishes a single message and RabbitMQ routes it to every queue bound to that exchange: stock, email, analytics. One module in Make, several listeners on your side.

Bridge no-code tools and engineering. A form, a spreadsheet row or a support ticket can become a message without anyone writing an integration. The marketing team builds the scenario, the dev team owns the consumer.

What Make does not do here: there is no trigger, so Make cannot react when a message arrives in a queue, and there is no generic API call module either. The same broker also has an n8n node, described on the RabbitMQ n8n integration page; if you are weighing the two tools, read n8n vs Make. New to the editor? The Make training starts from zero.

Connect

How do you connect your RabbitMQ server to Make?

  1. 01

    Open the port first

    Make reaches your broker from its own IP addresses, so your server must accept incoming TCP connections on port 5672 from them. Sort this out with whoever runs the firewall before touching Make, or the connection will simply time out.

  2. 02

    Add a module and create the connection

    In your scenario, add a RabbitMQ module and click Create a connection. A connection is your server account linked to Make once, then reused by both modules. Give it a clear Connection name, such as the environment it points to.

  3. 03

    Fill in the server details and save

    Type your server address in Hostname and its port in Port, then a user in Username and Password. Click Save. If Make asks you to authenticate and confirm access, accept, and the connection turns usable.

First scenario

Your first scenario with RabbitMQ in Make

GoalWhen the scenario runs, Make sends a job to a RabbitMQ queue, then publishes a notice to an exchange.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. RabbitMQ has no trigger, so this first brick will be an action that runs on a schedule.

  2. 02

    Add Send To Queue

    Search for RabbitMQ, pick Send To Queue and select the connection you just made. Fill the module fields; once the connection works, Make can help you with what it reads from your server.

  3. 03

    Chain Send To Exchange

    Click the + on the right of the first module and add Send To Exchange. Map the same job details into it, then choose the exchange that should fan it out.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles (the items passed from one module to the next) each module handled. Check in your RabbitMQ dashboard that both messages arrived.

  5. 05

    Schedule and switch it on

    Open Scheduling on the first module. A new scenario runs every 15 minutes by default. Keep that or adjust it, then flip the scenario on. Later, you can swap the schedule for a trigger from another app.

Modules

What the RabbitMQ app can do in Make

RabbitMQ gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

RabbitMQ1

Send To Exchange

Action

In Make“Send a single message to an exchange.”

This module publishes one message to an exchange, and RabbitMQ then decides which bound queues receive a copy. One bundle in, one message out.

When to use it
several services need to hear about the same business event, and you would rather keep routing rules inside RabbitMQ than duplicate modules in Make.
Watch out
if no queue is bound to the exchange, the message has nowhere to go, so check the bindings before blaming Make.
RabbitMQ2

Send To Queue

Action

In Make“Send a single message to a queue.”

Here the message skips the exchange logic you manage and lands in one named queue, ready for the consumer that reads it. The simplest way to hand a task from a no-code tool to a program your developers wrote.

When to use it
exactly one service should process the job, like a PDF generator waiting for new invoices.
Watch out
an operation (one execution of a module on one bundle) is counted for every message, and a typo in the queue name sends your work to the wrong place.
Need help

Need help automating RabbitMQ with Make?

A person reads every message.

FAQ

RabbitMQ and Make: common questions

01Is the RabbitMQ Make integration free?
Yes, RabbitMQ is a standard app, so it works on the Free plan like the other 3,000+ standard apps. The Free plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute, allow unlimited active scenarios and 40 minutes of execution. Usage is counted in operations each month, and every message sent is one operation.
02What do you need to connect RabbitMQ to Make?
You need a configured RabbitMQ server that accepts incoming TCP connections on port 5672 from Make's IP addresses, because Make opens the connection from its side. Then you enter a hostname, a port, a username and a password in the connection window and click Save. A dedicated user is cleaner than the default one: create it in the dashboard under Admin, with the access level chosen in Tags. Give the connection a name that says which server it points to.
03Can a RabbitMQ scenario in Make react in real time?
No, not on the RabbitMQ side, because the app has no trigger at all. Make cannot watch a queue and start when a message shows up. Your scenario starts in one of two ways: on a schedule, every 15 minutes by default on a new scenario, or through a trigger from another app placed first, such as a new form entry or a CRM update. RabbitMQ modules then come after it to send the message. If you need to consume messages, that part stays with your own code.
04What if the RabbitMQ module you need is missing?
The app only has two actions, Send To Exchange and Send To Queue, and no Make an API Call module to fill gaps. So reading messages, creating queues or managing bindings are out of reach from this app. The practical route is to keep that work in RabbitMQ itself or in the service that consumes the queue, and let Make handle the sending side. If the scenario still does not fit, the team can look at your setup with you through the help form below.
05Should you use Make or n8n for RabbitMQ?
It depends on what your team already runs. Both tools can talk to RabbitMQ: Make through the two sending modules described here, n8n through its own node, which has its own page on this site. Nothing in the documentation ranks one above the other for this broker, so the fair criteria are practical ones. Which tool do your other scenarios live in, which modules do you actually need, and who will maintain the flow once it is live? Start there before you pick.
Same platform

Other docs you might need on this stack.

Browse all integrations