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-dev/n8n-nodes-wmata-incidents

v1.0.1

Published

Rail, bus, and elevator disruptions/outages.

Vulnerabilities

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

Links

Git

Maintainers

kelvinzerokelvinzero

Keywords

n8nn8n-community-noden8n-noden8n-community-node-packageopenapiswaggerapiautomationworkflowwmata-incidents

Readme

@n8n-dev/n8n-nodes-wmata-incidents

wmata-incidents Banner

npm version License: MIT

Stop writing wmata-incidents API integrations by hand.

Every time you connect n8n to wmata-incidents, you waste hours mapping endpoints, defining parameters, and debugging schemas. You copy-paste from docs, fix edge cases, and pray nothing breaks.

What if connecting n8n to wmata-incidents took 5 minutes, not half a day?

This node gives you 1+ resources out of the box: Default: with full CRUD operations, typed parameters, and zero manual configuration.

What You Get

  • Zero boilerplate: Resources, operations, and fields are pre-configured and ready to use
  • Full CRUD: Create, read, update, and delete support where the API allows it
  • Typed parameters: No more guessing field types
  • Built-in auth: API key authentication, ready to go
  • Declarative: Native n8n performance, no custom execute() overhead

Install

npm install @n8n-dev/n8n-nodes-wmata-incidents

Or in n8n:

  1. Settings → Community Nodes → Install
  2. Search: @n8n-dev/n8n-nodes-wmata-incidents
  3. Click Install

Quick Start

  1. Install the node (above)
  2. Add credentials: wmata-incidents API → paste your API key
  3. Drag the wmata-incidents node into your workflow
  4. Pick a resource → pick an operation → done.

That's it. No configuration files. No code. It just works.

Resources

| Resource | Operations | |----------|------------| | Default | Get xml rail incidents, Get json rail incidents |

Why This Node?

Without this node:

  • Hours of manual API integration
  • Copy-pasting from wmata-incidents docs
  • Debugging auth, pagination, error handling
  • Maintaining your own client code

With this node:

  • Install → configure → use. 5 minutes.
  • Auto-generated from the official wmata-incidents OpenAPI spec
  • Always up to date when the API changes
  • Native n8n performance

Auto-Generated

This node was auto-generated from the official wmata-incidents OpenAPI specification using @n8n-dev/n8n-openapi-node-ultimate, then validated against the live API so you get accurate types and real parameters, not guesswork.

When the wmata-incidents API updates, this node updates too.

Support This Project

If this node saved you hours of work, consider supporting continued development, new APIs, better error handling, and faster updates.

Keep It Moving.

License

MIT © kelvinzer0