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

@orchesty/connector-wisepops

v2.0.0

Published

[![npm](https://img.shields.io/npm/v/@orchesty/connector-wisepops?color=15ba68)](https://www.npmjs.com/package/@orchesty/connector-wisepops) [![License](https://img.shields.io/badge/license-Apache--2.0-15ba68)](https://github.com/Orchesty/orchesty-nodejs-

Readme

Wisepops Connector

npm License

An Orchesty connector for Wisepops, an on-site marketing platform for growing email lists and boosting sales through targeted popups and notifications.

Application Type

Basic (Webhook)

This connector implements IWebhookApplication and authenticates using an API key sent via a custom WISEPOPS-API key="{api_key}" header. Wisepops delivers collected email events to your Orchesty webhook endpoint.

| Field | Description | |---|---| | api_key | Your Wisepops API key |

Components

This connector has no standalone Connector or Batch nodes — all integration logic is handled through the webhook subscription lifecycle built into the Application class.

| Webhook | Event | Description | |---|---|---| | Collected Emails | email | Triggered when a visitor submits their email via a Wisepops popup |

Setup

Credentials

  1. Log in to your Wisepops account.
  2. Navigate to Settings → Integrations → API and copy your API key.
  3. In Orchesty, open the Wisepops application settings, enter the API key, and complete the webhook registration flow.

Webhooks

After authorization, Orchesty registers a webhook for the email event via POST https://app.wisepops.com/api1/hooks. When Wisepops detects a form submission, it sends the event to your Orchesty webhook URL.

API Documentation

Wisepops API: https://wisepops.com/

Installation & Usage

Install the package:

npm install @orchesty/connector-wisepops @orchesty/nodejs-sdk
# or
pnpm add @orchesty/connector-wisepops @orchesty/nodejs-sdk

Register the application in your Orchesty DI container:

import { container } from '@orchesty/nodejs-sdk';
import WisepopsApplication from '@orchesty/connector-wisepops/dist/WisepopsApplication';

const app = new WisepopsApplication();
container.setApplication(app);

License

This connector is released under the Apache License 2.0. See the LICENSE file for the full license text.

Contributing

Contributions are welcome! This connector is part of the open-source Orchesty Node.js Connectors monorepo.

For guidelines on how to create or update connectors — including project setup, coding conventions, and how to write tests — please refer to the Contributing to Connectors guide.

All contributions should include:

  • Source code in src/ following the existing connector structure
  • Tests in src/**/__tests__/ with input.json, mock.json, and output.json fixtures
  • An updated CHANGELOG.md entry