Does n8n Cloud Support RabbitMQ for Persistence? Are Other Queue Options Available?

Describe the problem/error/question

We are evaluating n8n Cloud for production use and need clarity on workflow queueing and persistence.

  • Does the n8n Cloud version support RabbitMQ (or any message broker) for job persistence or execution queueing?
  • If not, what queuing/persistence mechanism is used internally?
  • Are any advanced queueing options available for enterprise setups?

We’re mainly interested in how scalability and reliability are handled behind the scenes for long-running or scheduled workflows.

What is the error message (if any)?

None — this is a design/architecture-level question.

Please share your workflow

Not applicable — this is an infrastructure question.

Share the output returned by the last node

N/A

Information on your n8n setup

  • n8n version: Cloud (latest)
  • Database: Managed (not self-hosted)
  • n8n EXECUTIONS_PROCESS setting: Managed (cloud default)
  • Running n8n via: n8n Cloud
  • Operating system: Not applicable (cloud-based)

@Lokesh_Kashyap

So if using queue mode, you need redis, am not sure if they support others, but redis is the middle man in syncing with workers and main n8n, btw enterprise has ha such as multi main, but scaling wise queuemode etc.

So u can have multi workers which checks the redis queue that main posts there, note the data in redis is very small just references to workflow to run from db etc etc,

Also if using filesystem mode helps alot more than running all in RAM ie for long workflow it can eat up ram quickly causing ooms, crashes. typically it just stops the execution for that wf but not always.

And you can have few other options too. But hope that helps, btw, you can always build ontop of n8n infra, and inside a workflow use MQs incase of crashes etc, so u can send crud redis queue or rabbit kafka etc

Samuel

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.