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

integration-mock

v0.1.1

Published

Mock the APIs an n8n workflow calls: vendor packs from OpenAPI, recorded traffic, snapshot and replay, fault injection

Readme

integration-mock

CI npm License: MIT

Build and test n8n workflows without calling the real APIs. integration-mock runs on your machine and answers as Slack, Stripe, HubSpot and other services would, so a test run sends no real messages, uses no quota and needs no API key. Anything it has no answer for fails with a clear error instead of empty data.

integration-mock starting, serving a mocked API, answering an unknown route with an error, and showing the request log

Installation

Requires Node.js 20 or newer.

Run it without installing:

npx integration-mock --help

Add it to a project:

npm install --save-dev integration-mock

Build from source:

git clone https://github.com/LudwigGerdes/integration-mock.git
cd integration-mock
pnpm install && pnpm build

Getting started

Start the mock, turn on the Slack pack, and post a message to it:

npx integration-mock start
npx integration-mock packs enable slack
curl -X POST http://127.0.0.1:8080/slack/api/chat.postMessage

Expected output:

proxy started on :8080 (admin :8081)
enabled: slack
{"channel":"C1H9RESGL","message":{"attachments":[{"fallback":"This is an attachment's fallback","id":1,"text":"This is an attachment"}],"bot_id":"B19LU7CSY","subtype":"bot_message","text":"Here's a message for you","ts":"1503435956.000247","type":"message","username":"ecto1"},"ok":true,"ts":"1503435956.000247"}

No message was sent anywhere. See what was called, then stop the mock:

npx integration-mock log
npx integration-mock stop

Expected output:

2026-09-21T07:32:48.556Z	POST	slack	/api/chat.postMessage	200	slack:POST:/api/chat.postMessage#0
stopped

In n8n, set an HTTP Request node's URL to http://127.0.0.1:8080/slack/api/chat.postMessage to use the mock from a workflow.

Usage

See which services can be mocked, and turn some on:

integration-mock packs list
integration-mock packs enable slack hubspot

Get the base URL to point a workflow at:

integration-mock url slack

Make the next call fail, to test an error branch or retry settings:

integration-mock faults set slack --status 503 --once

Mock an API that has no pack yet:

integration-mock packs init acme --domain api.acme.com

Expected output:

created ./.integration-mock/packs/acme
next: edit routes/main.json, then `integration-mock packs validate acme`

This creates:

.integration-mock/
└── packs/
    └── acme/
        ├── pack.json
        └── routes/
            └── main.json

Mock nodes whose URL you cannot change, such as the Slack node, by running n8n and the mock together in Docker:

integration-mock up

Run a workflow once for real, then keep testing against that recorded run:

integration-mock snapshot latest --workflow <id>

Documentation

Full documentation is at workflowtools.dev/integration-mock:

License

MIT © Ludwig Gerdes

The packs are generated from the services' published OpenAPI descriptions; NOTICE lists each source. Not affiliated with n8n GmbH or with any of the services mocked.