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

v0.11.0

Published

n8n community nodes for Oido Studio — call Oido agents and trigger workflows from Oido events.

Readme

n8n-nodes-oido

n8n community nodes for Oido Studio. Call Oido agents from inside your workflows, trigger workflows from Oido events, and let agents trigger your workflows.

Nodes

  • Oido — actions:
    • Run Agent — run an Oido agent with a dynamic input and use its answer downstream (waits for the result, or fire-and-forget). Usable as a tool by n8n's AI Agent node.
    • Respond to Agent — return a shaped response (items, custom JSON, text; status code, headers) to the agent that dispatched the workflow. Requires an Oido Trigger (Agent Dispatch) upstream.
    • Embed Text — turn text into an embedding vector with the Oido embedding model (POST /v1/embeddings).
    • Rerank Documents — rank an array of documents by relevance to a query; returns documents with scores (POST /v1/rerank).
    • Extract Text (OCR) — run OCR on a binary image/PDF (max 10MB) and get the text back; nothing is stored (POST /v1/ocr/extract).
    • Search Documents — semantic search over documents previously ingested via Oido OCR (GET /v1/ocr/search).
    • Ingest Document — upload an image/PDF into the Oido document store; async OCR + semantic indexing (POST /v1/ocr/ingest).
    • Get Document — fetch an ingested document and its processing status; poll after Ingest Document (GET /v1/ocr/documents/:id).
    • Search Wiki — semantic search over the org wiki, with optional rerank (GET /v1/wiki/search).
    • Get Wiki Page — fetch a wiki page by slug (GET /v1/wiki/:slug). The auto-maintained slug index is the org's knowledge entrypoint: page counts, hub pages, synthesis links and an overview.
    • Ingest to Wiki — feed text or a URL into the wiki knowledge pipeline; returns an async job_id (POST /v1/wiki/ingest).
  • Oido Trigger — triggers:
    • Oido Event — start the workflow when an Oido event fires: agent run finished (optionally filtered to one agent) or channel message received (optionally filtered to one channel).
    • Agent Dispatch — let Oido agents start this workflow with their trigger_workflow tool (the agent must be bound to the workflow in Studio → n8n). Choose how to respond: immediately, with the last node's output, or via a Respond to Agent node.

Install

n8n → Settings → Community Nodes → Installn8n-nodes-oido.

Requires n8n community packages enabled (N8N_COMMUNITY_PACKAGES_ENABLED=true).

Credential — Oido API

  • Base URL: http://oido:5577 when n8n runs in the same Docker network as Oido; otherwise your public API URL.
  • API Key: create one in Oido Studio → Settings → API Keys (starts with oido_sk_).

Develop

npm install
npm run build      # → dist/
npm publish        # community package (keyword: n8n-community-node-package)