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-timeout

v0.1.0

Published

A Timeout node which allows to continue with subsequent nodes if no events have arrived in a given timespan

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

martin-probstmartin-probst

Keywords

n8n-community-node-package

Readme

n8n-nodes-timeout

This is an n8n community node. It lets you use Timeout nodes in your n8n workflows. Useful in home automation flows.

The timeout node takes incoming events from the trigger input and delays them for a given period of time. But unlike the Wait node, whenever a new event arrives within the waiting period, the timeout of the previous execution is cancelled and it will stop without emitting an event to subsequent nodes. A workflow which uses a Timeout node to detect and alert about a sensor failure

Use-cases

Timeout nodes are especially useful in home-automation if you want to observe interruptions in an event stream. Consider a sensor which reports its measurements regularly via a webhook. If the sensor stops transmitting (low battery, lost network connection) for some time, you can detect this failure and notify the user about it.

A different use-case is to turn something on (a light, a pump) for a certain duration and have it turned off automatically. While this could also be achieved with a simple Wait node (turn on -> wait -> turn off), you can get into trouble if this workflow is triggered again before an earlier execution has finished. A workflow which uses a Timout node to control auto-off of an actuator

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Compatibility
Usage
Resources
Version history

Installation

Follow the installation guide in the n8n community nodes documentation.

Operations

List the operations supported by your node.

Compatibility

State the minimum n8n version, as well as which versions you test against. You can also include any known version incompatibility issues.

Usage

Connect the flow of an event source (usually a Webhook) to the Trigger input of the Timeout node. If you need events to cancel the timeout altogether without triggering a new timeout, connect these event to the Cancel input. This could be events from an If branch or from a different source (like a second Webhook). It is totally fine to leave the Cancel input unconnected, e.g. if you only want to detect the disruption of incoming events.

If you have an event stream of similar events (e.g. multiple sensors), you can use a unique id from their payload (sensor id) in the optional scope parameter. This will trigger independent timeouts for each unique scope.

Resources