Redis n8n integrationAutomate Redis with n8n.
The Redis n8n integration turns an in-memory store into an ordinary workflow step. The node groups 10 operations under a single Redis resource, from reading a key to draining a list. The Redis Trigger subscribes to the channels you name. Built for teams that keep state between runs.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Redis n8n integration actually do?
The Redis n8n integration links a workflow to a Redis server through one credential, a login saved once in n8n, then exposes 10 operations: set and get a key, delete it, increment a counter, list keys by pattern, measure a list, push and pop list items, publish on a channel and read instance information. A second node, the Redis Trigger, subscribes to channels, so a message published in Redis can start a workflow of its own.
Three patterns cover most of what gets built here. Deduplication comes first: a run writes a marker with default.set, and every later run checks it with default.get before doing the work twice, so the same order never produces two alerts in Slack.
Queues come second. One workflow appends jobs with default.push, a scheduled workflow takes them one by one with default.pop, and default.llen says how far behind the list has fallen. A slow downstream API is never handed everything at once.
Coordination comes third. default.publish sends a message on a channel, the Redis Trigger in a second workflow subscribes to that channel, and the second workflow starts when the message arrives. Two automations stay separate without either one calling the other.
The boundaries are worth knowing before you plan around them. The node stops at 10 operations, all under one Redis resource, and a command outside that list is not exposed. The trigger has no event list to pick from either: you name channels, and that is the whole configuration. On Get and Set, a Key Type left on Automatic asks the server for the type before the data, which is slower than naming String or Hash yourself.
Redis keeps its values in memory, which makes it a natural home for counters, short-lived markers and queues, and a poor stand-in for the durable tables you keep in Postgres or MySQL. Plenty of workflows use both: the relational store holds the record, Redis holds the state between executions. If the platform itself is still an open question, the n8n review walks through the trade-offs, and the n8n training covers building these flows step by step.
How do you connect Redis to n8n?
- 01
Create the Database connection credential
Redis has one credential type in n8n, Database connection, and the node carries no authentication selector, so there is nothing to choose. Open Credentials, create a Redis credential, then enter the Password of a user account on your Redis server and the Host name of that server. Host defaults to
localhost, so change it whenever Redis runs somewhere else. - 02
Point the credential at the right port and database
Port defaults to
6379, and the number has to match thetcp_portvalue listed when you run theINFOcommand on the server. Database Number defaults to0and picks which logical database the connection opens. Both are plain numbers, and both deserve a second look before you save the credential. - 03
Turn SSL on when the connection leaves the machine
The SSL toggle decides how the connection travels. Left off, it runs over TCP only. Turned on, it runs over SSL and reveals a second option that disables TLS verification, meant for self-signed certificates. A credential saved once here is then offered in the dropdown of every Redis node you add later.
What starts a workflow from Redis ?
Redis Trigger is the node that starts a workflow when something happens in Redis. Activate the workflow and every event it receives becomes one execution.
What you see in n8n
Configuration notes
01Subscribe to a Redis channel
The Redis Trigger listens on the server its credential points at. The workflow starts whenever a channel the node subscribes to receives a new message, and that message becomes the first item of the execution. Use it when something already broadcasts on Redis, or when another n8n workflow publishes with the Publish operation.
Key parameters
- Channels: required, the channels to subscribe to. Several channel names go in the same field, separated by commas, and the wildcard character
*is supported when you want a whole family of names.
02Set the trigger options
Two options decide what the workflow actually receives. Left alone, the trigger hands over the message as it arrived, which is fine when the publisher sends plain text. When the other side publishes JSON, these two are what save a Code node further down the canvas.
Key parameters
- JSON Parse Body: n8n tries to parse the message into an object, so its fields become addressable in expressions, the way
{{ $json.orderId }}reads an order id straight from the payload. - Only Message: the trigger returns only the message property rather than the item wrapped around it.
What can the Redis node do?
The Redis node exposes 10 operations. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Delete a key from Redis
deleteWhat you see in n8n
Notes & use cases
Removes the key you name and leaves everything else in the database alone. This is the step that ends a stored state rather than reading or changing it.
Key parameters
- Key: name of the key to delete from Redis, usually built from the item in hand, as in
{{ $json.id }}.
Get the value of a key from Redis
getWhat you see in n8n
Notes & use cases
Reads one key and writes what comes back into the item, under a property you choose. The workflow then carries the stored value next to the data it already had.
Key parameters
- Name: the property to write the received data to. Dot-notation is supported, so
data.person[0].namenests the value where you want it. - Key: name of the key to get from Redis.
- Key Type: Automatic requests the type before the data and is slower for it; pick Hash, List, Sets or String when you already know.
- Dot Notation: sitting in Options, switch it off to write a flat property name instead of nesting.
Atomically increment a key by 1. Creates the key if it does not exist.
incrWhat you see in n8n
Notes & use cases
Adds 1 to the counter held under the key, atomically, and creates the key when it is missing. Two executions running at the same moment cannot land on the same number.
Key parameters
- Key: name of the key to increment.
- Expire: switch it on to set a timeout on the key.
- TTL: number of seconds before the key expires.
Return generic information about the Redis instance
infoWhat you see in n8n
Notes & use cases
Returns generic information about the Redis instance the credential points at, without touching a single key. No required parameter to fill in, so the node runs the operation the moment the workflow reaches it.
Key parameters
- Value Is JSON: the single optional setting here, which tells the node whether the value it handles is JSON or key value pairs.
Return all keys matching a pattern
keysWhat you see in n8n
Notes & use cases
Brings back every key whose name matches the pattern you give. One switch turns the same operation into a small export, values included.
Key parameters
- Key Pattern: the key pattern for the keys to return.
- Get Values: on, the node also returns the value stored under each matching key.
Return the length of a list
llenWhat you see in n8n
Notes & use cases
Gives the number of items sitting in a list, and stops there. The count arrives as data in the item, so an IF node can branch on it without any extra step.
Key parameters
- List: name of the list in Redis.
Pop data from a redis list
popWhat you see in n8n
Notes & use cases
Takes one item off a list and hands it to the workflow. The item leaves the list, so the following execution picks up the next one instead of the same one.
Key parameters
- List: name of the list in Redis.
- Tail: on, the item comes off the end of the list rather than the front.
- Name: optional property to write the received data to, dot-notation included.
- Dot Notation: in Options, off writes the property name as it stands.
Publish message to redis channel
publishWhat you see in n8n
Notes & use cases
Sends a message on a channel. Everything subscribed to that channel receives it, including a Redis Trigger sitting in another n8n workflow.
Key parameters
- Channel: channel name, the same one the subscriber listens on.
- Data: the data to publish.
Push data to a redis list
pushWhat you see in n8n
Notes & use cases
Adds data to a list, which is how a queue gets filled for a later run to empty.
Key parameters
- List: name of the list in Redis.
- Data: the data to push.
- Tail: on, the data goes to the end of the list, which changes the order a Pop will see.
Set the value of a key in redis
setWhat you see in n8n
Notes & use cases
Writes the value you provide under the key you name. Four optional settings decide what gets stored and how long it survives.
Key parameters
- Key: name of the key to set in Redis.
- Value: the value to write in Redis.
- Key Type: Automatic tries to work out the type from the data; Hash, List, Sets and String state it outright.
- Expire and TTL: switch on Expire to set a timeout, then give TTL the number of seconds before the key expires.
Need help automating Redis with n8n?
A person reads every message.
