oto.cx
zohodesk

zoho

zohodesk.

List support tickets.

ajouter à otoauth : —prefix : zohodesk_*

setup & usage

⚠ zoho desk oauth self-client (4 fields)

Zoho Desk uses an oauth2 self-client with 4 secrets. In the Zoho API developer console, create a self client, generate a grant token with the Desk.* scopes, then exchange it for a refresh token. You need to provide oto with:

  • client_id and client_secret — from the self client
  • refresh_token — from the exchange
  • org_id — the id of your desk organization (orgId header) — optional: a single-portal token resolves the portal on its own, only fill it in if a call asks for it

    • scopes per surface — a token can authenticate with PARTIAL scopes (articles respond while tickets return SCOPE_MISMATCH). Request the ones you need:

  • tickets → Desk.tickets.READ (+ .WRITE to create/edit) · ticket search → Desk.search.READ + Desk.tickets.READ
  • contacts → Desk.contacts.READ (+ .WRITE) · departments → Desk.basic.READ · articles (KB) → Desk.articles.READ (+ Desk.search.READ to search them)

    • Fill in these fields in oto on your account (/account), connector zohodesk. byo only.

    ▸ what you can do

    Manage zoho desk support (tickets, threads, contacts) from claude.

  • "list open tickets" → zohodesk_tickets (status Open)
  • "open ticket #123 with its contact" → zohodesk_ticket (include contacts)
  • "create a ticket" → zohodesk_create_ticket (subject + departmentId + contactId)
  • "the replies on this ticket" → zohodesk_ticket_threads
  • "find the help article about X" → zohodesk_search_articles (query), then zohodesk_article for its full body
    • ⚙ multiple comptes

    this connector accepts multiple comptes: each stored credential becomes a named account (one name per compte), at your level, your team's or your org's.

  • the first one doesn't need a name; from the second on, each one carries its own (the first then takes the name "principal", renamable)
  • without specification, the agent takes the only stored compte, otherwise the one marked as default; otherwise the call is refused, naming the available comptes — never a random choice
  • target a compte for a call: _account="<name>" on the tool; list them: oto_identity(op='list', connector='zohodesk') (scope='org' or scope='group' for the org's or team's)
  • set the default: oto_identity(op='set', connector='zohodesk', identity_id='<name>'); rename: op='rename' with new_name
  • ⚠️ no tool walks through the comptes on its own: a total across several comptes is obtained by calling each one (_account) and adding up

    • outils

    chargement…

    utilisation

    claude code — installe le plugin oto — claude plugin marketplace add otomata-tech/oto-plugin — mcp + skill configurés.
    claude.ai — branche mcp.oto.cx/mcp en connecteur custom (guide)
    cli — pipx install oto-cli puis oto zohodesk …
    ← tous les connecteurscatalogue mcp →