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

v0.1.0

Published

n8n community nodes for ABM.dev — person/company enrichment actions and an instant (webhook) trigger

Readme

n8n-nodes-abmdev

n8n community nodes for ABM.dev — submit person/company enrichments, fetch results, and react to platform events in real time.

Sibling of the canonical Zapier app (integrations/zapier/) — same API surface, same auth model, same webhook-subscription contract.

Nodes

ABM.dev (action node, declarative style)

| Operation | Endpoint | Notes | |---|---|---| | Enrich Person | POST /v1/enrichments (type: person) | inputs → input.{ email, linkedin_url, first_name, last_name, company_name, domain } | | Enrich Company | POST /v1/enrichments (type: company) | inputs → input.{ company_name, domain, linkedin_url, crm_id }; the "Company website or domain" field is normalised to a bare host | | Get | GET /v1/enrichments/{id} | status, result field map, fieldAttribution | | Get Many | GET /v1/enrichments?take=N | recent jobs, newest first |

Enrichment is asynchronous: creates return { id, status: "queued" }. Chain with the trigger node (below) or poll Get.

Blank optional inputs are pruned from the request body before send (pruneEnrichmentBody preSend hook), and { data: ... } envelopes are unwrapped on receive.

ABM.dev Trigger (instant, webhook)

Subscribes via the platform's REST-hook API — the exact contract the Zapier app uses:

  • activate → POST /v1/webhooks/subscriptions { event_type, url, description } (response includes the signing secret, returned once — stored in workflow static data)
  • deactivate → DELETE /v1/webhooks/subscriptions/{id}

Event types: enrichment.completed, enrichment.approved.

Incoming deliveries are the standard envelope { id, event_type, created_at, data }. When the stored secret is available the node verifies X-Webhook-Signature (sha256= + HMAC-SHA256 of the raw body) and rejects mismatches with 401.

Credentials

ABM.dev API — one API key (sent as x-api-key on every request) plus a base URL:

  • https://api.abm.dev (default; public gateway — paths are /v1/...)
  • http://localhost:5000/api for a locally running AbmDev.Api without the gateway (paths compose to /api/v1/...)

The credential test calls GET /v1/organizations/current, which resolves the org from the key (401 if the key is bad).

Development

npm install
npm run build     # tsc + copy icons/codex json into dist/
npm run lint      # eslint-plugin-n8n-nodes-base community presets
npm test          # smoke tests over the built dist/

Load into a local n8n

# n8n discovers community packages installed under ~/.n8n/nodes
mkdir -p ~/.n8n/nodes
cd ~/.n8n/nodes && npm install /path/to/abm/integrations/n8n
npx n8n
# → ABM.dev + ABM.dev Trigger appear in the editor's node panel

To run against the dev API, set the credential's Base URL to http://localhost:5000/api and paste a dev API key.

Note: instant triggers need the n8n webhook URL to be reachable by the ABM.dev API (use N8N_EDITOR_BASE_URL/WEBHOOK_URL + a tunnel when the API is remote).