forked from spencerm/freshservice-claude
spencerm
0b6747812f
The pesco instance defines 13 ticket statuses, not the 4 defaults, so a (status:2 OR status:3) 'open tickets' filter silently dropped Working, Scheduled, Waiting*, Pending Approval, etc. — undercounting 24 open tickets as 1. Add a status helper that reads the status field from /ticket_form_fields and treats only ids 4/5 (and closed/resolved-labelled) as terminal. Expose list_ticket_statuses() and a list_tickets(unresolved=True) shortcut that builds the full non-terminal status clause automatically. Document the gotcha in the skill reference. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
freshservice-claude
A Claude skill for working with Freshservice ITSM from chat / Cowork — view, create, update, reply to, and triage tickets; look up and update assets/CMDB; find agents, requesters, groups, and departments; and manage changes, problems, and releases via the Freshservice REST API v2.
Layout
| File | Purpose |
|---|---|
SKILL.md |
Skill entry point — setup, common commands, guardrails |
reference.md |
Endpoints, status/priority codes, filter-query syntax |
scripts/fs.py |
Stdlib-only API helper (auth, URL building, paging, errors) |
Install
Copy the skill into your Claude skills directory:
cp -R . ~/.claude/skills/freshservice
Configure credentials
mkdir -p ~/.freshservice
cat > ~/.freshservice/credentials <<'EOF'
FRESHSERVICE_DOMAIN=yourcompany
FRESHSERVICE_API_KEY=your_api_key
EOF
chmod 600 ~/.freshservice/credentials
python3 ~/.claude/skills/freshservice/scripts/fs.py check
The API key is in Freshservice → profile picture → Profile settings → API key.
FRESHSERVICE_DOMAIN accepts the subdomain (yourcompany) or the full host.
Environment variables of the same name override the file.
Usage
The skill activates when you mention Freshservice or a ticket/asset/change in chat. Under the hood it calls:
python3 scripts/fs.py request <METHOD> <PATH> [--param KEY=VALUE ...] [--data '<JSON>']
See SKILL.md and reference.md for details.