@tplog/pi-zendy
Pi package for Dify Enterprise support ticket analysis
Package details
Install @tplog/pi-zendy from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@tplog/pi-zendy- Package
@tplog/pi-zendy- Version
0.3.6- Published
- Jun 1, 2026
- Downloads
- not available
- Author
- tplog
- License
- MIT
- Types
- extension
- Size
- 77.5 KB
- Dependencies
- 0 dependencies · 1 peer
Pi manifest JSON
{
"extensions": [
"./extensions/zendy.ts"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
zendy
Pi extension for Dify Enterprise support ticket analysis. Analyze Zendesk tickets with natural language — from ticket metadata to Helm chart values to source code.
Powered by pi.
What it does
zendy is a single pi extension that provides:
- LLM Tools — Direct API access to Zendesk, Helm Watchdog, and Knowledge Graph. No external CLI dependencies.
- Slash Commands —
/zendy-configto set up credentials,/zendy-statusto check connectivity. - Session Safety — Automatic workspace isolation and cleanup for source code analysis.
Typical workflow:
pi → "Analyze ticket #1959" → agent calls zendy_ticket_get →
identifies version → agent calls zendy_helm_get →
synthesizes findings → drafts reply
Prerequisites
- pi installed globally:
npm install -g @earendil-works/pi-coding-agent
Install
pi install npm:@tplog/pi-zendy
Configure
Start pi and run:
/zendy-config
This interactively collects Zendesk credentials (subdomain, email, API token) and Knowledge Graph API key.
Alternatively, set environment variables:
export ZENDY_ZENDESK_SUBDOMAIN=dify
export ZENDY_ZENDESK_EMAIL=you@example.com
export ZENDY_ZENDESK_API_TOKEN=your_token
export ZENDY_KG_API_KEY=your_kg_key
Credentials are stored in ~/.zendy/config.json (mode 0600). On first run, zendy auto-imports
from legacy zcli and zendesk-kg config files if they exist.
Commands
| Command | Purpose |
|---|---|
/zendy-config |
Configure Zendesk and KG credentials |
/zendy-status |
Check connectivity to all services |
Tools
The agent can call these tools directly:
| Tool | Description |
|---|---|
zendy_ticket_get |
Fetch ticket metadata, comments, and user info |
zendy_ticket_search |
Search live Zendesk tickets |
zendy_helm_get |
Query Helm chart values, images, validation by version |
zendy_kg_search |
Semantic search over historical tickets |
zendy_source_status |
Check source analysis workspace |
Legacy Launcher
For users of the old zendy CLI:
npm install -g @tplog/pi-zendy
zendy
The legacy launcher starts pi with the zendy extension and system prompt. It still supports
zendy preflight and zendy cleanup-src as standalone subcommands.
How it works
zendy registers as a pi extension package. The extension provides tools (callable by the LLM),
slash commands (for human engineers), and session lifecycle hooks (workspace creation, cleanup).
All data access goes through direct REST APIs — no zcli, zendesk-kg, or other CLI tools
are required at runtime.