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

@hogsend/plugin-telegram

v0.31.1

Published

Telegram connector for Hogsend — inbound activity (messages, `/start` deep-link linking) → `IngestEvent`, plus journey-callable outbound actions (`sendMessage`, `dm`) over the Bot API.

Downloads

559

Readme

@hogsend/plugin-telegram

Telegram connector for Hogsend — inbound activity (messages, /start deep-link linking) → IngestEvent, plus journey-callable outbound actions (sendMessage, dm) over the Bot API.

  • Transport: webhook (Telegram delivers updates over HTTPS; no socket). Served at POST /v1/webhooks/telegram.
  • Identity (minimal path): the contact's canonical key is telegram:<userId> (the external key); platform metadata lives under contacts.properties.telegram. No engine schema change.
  • Linking: a one-tap https://t.me/<bot>?start=<token> deep link binds the Telegram account to an email. The token is a short, single-use, TTL'd Redis nonce (Telegram caps the start param at 64 chars, so the binding is stored server-side, not in the link).

Wire it up

import { telegramConnector, telegramActions } from "@hogsend/plugin-telegram";

const client = createHogsendClient({
  connectors: [telegramConnector],
  connectorActions: telegramActions,
});

Set TELEGRAM_BOT_TOKEN (from BotFather) and TELEGRAM_WEBHOOK_SECRET (an arbitrary secret echoed back by Telegram's setWebhook(secret_token=…) and checked by the engine route), then register the webhook:

https://api.telegram.org/bot<TOKEN>/setWebhook?url=<PUBLIC_URL>/v1/webhooks/telegram&secret_token=<TELEGRAM_WEBHOOK_SECRET>

Send from a journey

import { sendConnectorAction } from "@hogsend/engine";

await sendConnectorAction({
  connectorId: "telegram",
  action: "sendMessage",
  args: { chatId: user.properties.chatId, text: "Welcome 👋" },
});