npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-msg-buffer

v1.0.0

Published

A community n8n node for message buffering

Readme

n8n-nodes-msg-buffer

This is an n8n community node. It lets you use a timed message buffer in your n8n workflows.

The timed message buffer collects incoming messages over a sliding time window — the window resets with each new message — and emits them all at once when no new messages arrive within the configured interval.

Installation Operations Credentials Compatibility Usage Resources


Installation

Follow the installation guide in the n8n community nodes documentation.


Operations

  • Buffer messages — Accumulate incoming data under a shared session key. Each new message resets the time window.
  • Emit buffered messages — Once no new messages arrive within the configured interval, release all collected messages together through the Ready output.

Credentials

This node requires a Redis credential to store buffer state across executions.

Without a valid Redis credential, the node will not function.


Compatibility

  • Last tested on: n8n 1.100.0
  • Minimum version: Not determined — use 1.100.0 or later to be safe.

Usage

The node has five parameters:

| Parameter | Type | Description | | -------------------- | ---------- | ----------------------------------------------------------------------------------- | | Session Key | String | Unique identifier to group messages into the same buffer (e.g. conversation-123). | | Content | String | The data you want to accumulate (e.g. the message text). | | Wait Amount | Number | How long to wait after the last message before emitting (e.g. 5). | | Wait Unit | Dropdown | Unit for the delay: seconds, minutes, hours, or days. | | Redis Credential | Credential | The Redis connection to use for storing buffer state. |

Outputs

  • Ready — Fires once after the wait interval expires with no new incoming messages. Returns an object with all buffered content:
{
	"data": [
		"Hi!",
		"How are you?",
		"What's up?"
	]
}
  • Discarded — Fires on every execution that arrives while a window is already running. Returns an empty object {} and does nothing else.

When should you use this node?

This node is useful whenever you receive a burst of related messages in a short period and want to process them together instead of one by one.

Example: Chat Message Buffering

Screenshot of example workflow

With n8n-nodes-msg-buffer:

  1. The first message opens a 5-second window and is added to the buffer.
  2. The next four messages arrive during that window, each resetting it, and are routed to Discarded — they are buffered silently, no action is taken yet.
  3. After 5 seconds of inactivity from the last message, the node fires the Ready output with all five messages:
{
	"data": [
		"Hi!",
		"How are you?",
		"What's up?",
		"Let's meet.",
		"Bye!"
	]
}

Your workflow then processes them as a single, complete message — one AI call, one coherent reply.


Resources