REDIS n8n INTEGRATION: AUTOMATE REDIS WITH N8N

The Set action is your go-to operation for storing data in Redis. It allows you to create or update a key-value pair in your database—the fundamental building block of Redis operations. Whether you're caching an API response, storing user session data, or saving workflow state, this action handles it all.

Key parameters to configure:

• Credential to connect with: Required dropdown to select your Redis account connection
• Key: Required text field where you define the unique identifier for your data. Choose descriptive names like user:123:profile or cache:api:weather
• Value: Required text field for the actual data you want to store
• Key Type: Dropdown set to "Automatic" by default, determining how Redis interprets your data type
• Expire: Optional toggle that, when enabled, lets you set an automatic expiration time for the key

Typical use cases:

• Cache API responses to avoid rate limits and speed up subsequent requests
• Store temporary workflow data that needs to persist between node executions
• Save user preferences or session information for quick retrieval
• Implement feature flags that can be updated in real-time

Use the Set action whenever you need fast, reliable key-value storage in your automations.

The Push action adds elements to a Redis list, making it perfect for building queues, maintaining ordered collections, or tracking sequential events. Redis lists are incredibly versatile—they can function as stacks, queues, or simple ordered arrays depending on how you push and pop data.

Key parameters to configure:

• Credential to connect with: Required dropdown for selecting your Redis connection
• List: Required text field where you specify the name of the Redis list (e.g., tasks:pending or events:user:456)
• Data: Required text field for the value you want to add to the list
• Tail: Optional toggle that determines where to insert the data. When disabled (default), data is pushed to the head (left side) of the list like LPUSH. When enabled, data goes to the tail (right side) like RPUSH

Typical use cases:

• Build a task queue where new jobs are added and workers process them in order
• Maintain an activity log by pushing each user action to a list
• Create a notification buffer that stores messages until they're consumed
• Implement a simple message broker between different parts of your automation

Choose head (LPUSH) for stack-like behavior (last-in-first-out) or tail (RPUSH) for queue behavior (first-in-first-out).

The Publish action sends messages to a Redis channel, enabling real-time communication between different systems subscribed to that channel. This is Redis's pub/sub (publish/subscribe) functionality—ideal for broadcasting events, triggering external processes, or implementing real-time notifications.

Key parameters to configure:

• Credential to connect with: Required dropdown to select your Redis account
• Channel: Required text field where you specify the channel name to publish to (e.g., notifications:sales or events:order-created)
• Data: Required multi-line text field for the message content you want to broadcast

Typical use cases:

• Send real-time notifications to a dashboard when a new order comes in
• Trigger external microservices that are subscribed to specific event channels
• Broadcast system alerts across multiple applications simultaneously
• Implement a webhook-like system where multiple consumers react to the same event

The Publish action is fire-and-forget: your message is sent to all current subscribers, but isn't stored. If no subscribers are listening, the message is lost—so ensure your consumers are running before publishing critical data.

The Pop action removes and retrieves an element from a Redis list. It's the counterpart to Push—while Push adds items, Pop takes them out. This action is essential for processing queues, consuming task lists, or implementing any workflow where items need to be handled one at a time.

Key parameters to configure:

• Credential to connect with: Required dropdown for your Redis connection
• List: Required text field specifying which Redis list to pop from
• Tail: Optional toggle determining which end to pop from. When disabled (default), pops from the head (left side) like LPOP. When enabled, pops from the tail (right side) like RPOP
• Name: Optional text field (defaults to propertyName) that defines where the popped value is stored in the output
• Options: Additional configuration options available via "Add option" button

Typical use cases:

• Process a queue of pending tasks by popping each task and handling it
• Implement a worker pattern where multiple n8n workflows consume from the same list
• Remove and process the oldest (or newest) item from a collection
• Build reliable job processing by combining Pop with error handling

Combine Push with Tail enabled and Pop with Tail disabled (or vice versa) to create a proper FIFO queue.

The List Length action returns the number of elements in a Redis list. It's a simple but crucial operation for monitoring queue sizes, implementing conditional logic based on list contents, or triggering alerts when queues grow too large.

Key parameters to configure:

• Credential to connect with: Required dropdown to select your Redis account credentials
• List: Required text field where you specify the key of the Redis list you want to measure

Typical use cases:

• Monitor your task queue and trigger alerts when it exceeds a threshold
• Implement backpressure logic: stop adding items if the list is too long
• Create dashboard metrics showing pending tasks or unprocessed events
• Conditional workflow branching based on whether a list is empty or not

This action is lightweight and fast—perfect for health checks or decision points in your automation flows.

The Keys action retrieves key names from your Redis database based on a pattern. It's incredibly useful for discovering what data exists, performing bulk operations, or auditing your Redis contents. With the option to fetch values alongside keys, it becomes a powerful data export tool.

Key parameters to configure:

• Credential to connect with: Required dropdown for selecting your Redis connection
• Key Pattern: Optional text field where you can specify a pattern to filter keys. Use wildcards like user:* to match all user keys, or cache:api:* for all API cache entries. Leave empty to retrieve all keys
• Get Values: Optional toggle that, when enabled, fetches both the key names AND their associated values—transforming this from a discovery tool into a data export action

Typical use cases:

• Audit your Redis database to see what keys exist matching a certain pattern
• Export all cached data for backup or migration purposes
• Build cleanup workflows that find and delete old or unused keys
• Generate reports on data stored in Redis

⚠️ Caution: Running Keys on a large production Redis database without a pattern can be slow and block other operations. Always use specific patterns when possible.

The Info action retrieves comprehensive information and statistics about your Redis server. It returns data about memory usage, connected clients, persistence status, replication, and much more. Think of it as a health check for your Redis instance.

Key parameters to configure:

• Credential to connect with: Required dropdown to select your Redis account credentials
• Operation: Set to "Info" to execute this server information query

Typical use cases:

• Monitor Redis memory usage and trigger alerts before you run out of space
• Track connected clients to identify potential connection leaks
• Verify persistence (RDB/AOF) status for backup monitoring
• Build a Redis health dashboard within your n8n workflows
• Debugging connection issues by checking server responsiveness

The Info action is perfect for scheduled health checks—run it every few minutes and pipe the results to your monitoring system or Discord channel.

The Increment action atomically increases the integer value of a key by one. This is Redis's INCR command—atomic means it's safe for concurrent access, making it perfect for counters, rate limiters, or any scenario where multiple processes might update the same value simultaneously.

Key parameters to configure:

• Credential to connect with: Required dropdown to select your Redis connection
• Key: Required text field specifying which key to increment. If the key doesn't exist, Redis creates it with value 0 before incrementing
• Expire: Optional toggle that, when enabled, allows you to set an expiration time for the key after incrementing

Typical use cases:

• Track page views, API calls, or any countable event in real-time
• Implement rate limiting by incrementing a counter per user/IP and checking against a threshold
• Generate sequential IDs for records or transactions
• Count occurrences of specific events for analytics purposes
• Build a simple hit counter that resets daily using Expire

The Increment action returns the new value after incrementing, so you can immediately use it in subsequent workflow logic.

The Get action retrieves the value associated with a specific key from Redis. It's the read operation that complements Set—together they form the basic CRUD operations for key-value storage. Fast and simple, Get is what you'll use most often to access your cached or stored data.

Key parameters to configure:

• Credential to connect with: Required dropdown to select your Redis account
• Key: Required text field where you enter the exact key you want to retrieve
• Name: Optional text field (defaults to propertyName) defining where the retrieved value appears in the output
• Key Type: Optional dropdown set to "Automatic" by default, specifying how Redis interprets the key's data type
• Options: Additional configuration options available for customization

Typical use cases:

• Retrieve cached API responses to avoid redundant external calls
• Fetch user session data or preferences stored earlier in the workflow
• Access configuration values stored in Redis
• Check if a specific piece of data exists (returns null if key doesn't exist)

Pro tip: Combine Get with an IF node to implement "cache or fetch" logic—check Redis first, and only call the external API if the cache misses.

The Delete action removes a key and its associated value from Redis. It's the cleanup operation you need for invalidating caches, removing obsolete data, or implementing data expiration logic manually when the built-in Expire isn't suitable.

Key parameters to configure:

• Credential to connect with: Required dropdown to select your Redis account credentials
• Key: Required text field specifying which key to delete. Accepts fixed strings or expressions for dynamic key deletion

Typical use cases:

• Invalidate cache entries when the underlying data changes
• Clean up temporary data after a workflow completes
• Implement manual expiration logic for complex scenarios
• Remove user data as part of a data deletion workflow (GDPR compliance)
• Clear rate limit counters to reset access

The Delete action is idempotent—deleting a key that doesn't exist simply returns success, so you don't need to check existence beforehand. For GDPR-compliant data management workflows, combine this with your HubSpot CRM integration.