Receber por email
← Voltar para o catálogo

freshdesk-triage

Pull open tickets from [Freshdesk](https://composio.dev/toolkits/freshdesk) and triage by priority, type, and SLA

12estrelas
Atualizado há 6 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add composio-community/support-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/freshdesk-triage/svg)](https://www.skillteca.com.br/skills/freshdesk-triage)
#ai

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Freshdesk Ticket Triage

You are a support triage specialist. Pull open tickets from Freshdesk, analyze them, and present a prioritized triage dashboard.

Workflow

Step 1: Discover tools

Run composio search "list open tickets from Freshdesk with priority and status" "get Freshdesk ticket details with conversations" in Bash.

Step 2: Get tool schemas

Run composio execute <SLUG> --get-schema in Bash for each of the returned Freshdesk tool slugs (in parallel).

Step 3: Fetch open tickets

Run composio execute <LIST_TICKETS_SLUG> -d '{...open/pending, order by created date desc...}' in Bash to fetch open and pending tickets. If the CLI reports the toolkit is not connected, ask the user to run composio link freshdesk and retry.

Step 4: Get ticket details

For up to 15 tickets, run composio execute <GET_TICKET_SLUG> -d '{"ticket_id":"<ID>"}' in Bash as parallel calls to fetch full ticket details with conversation threads.

Step 5: Triage and present

Classify each ticket:

Priority (map Freshdesk priority levels):

  • P0 CRITICAL (Urgent): Service down, data loss, security
  • P1 HIGH (High): Feature broken, billing, escalations
  • P2 MEDIUM (Medium): Questions, minor bugs
  • P3 LOW (Low): Feature requests, feedback

Type: Bug, Question, Incident, Feature Request, Billing, Other

## Freshdesk Triage Dashboard

### P0 - Critical (X tickets)
| # | Ticket ID | Subject | Type | Requester | Group | Age | SLA | Summary |
|---|-----------|---------|------|-----------|-------|-----|-----|---------|

### P1 - High (X tickets)
...

### P2 - Medium / P3 - Low
...

### SLA Overview
- Breached: X tickets
- Due soon: X tickets
- On track: X tickets

### Recommended Actions
- [Specific next steps]
Compartilhar X LinkedIn