oto.cx
zohosign

zoho

zohosign.

Zoho Sign signature requests and templates — read only. Sending, reminding

add to otoauth : —prefix : zohosign_*

setup & usage

⚠ zoho sign oauth (connect with zoho, or a self-client)

zoho sign uses the same zoho oauth as the crm and desk. the simplest: click authorize oto with zoho on the connector card and pick your zoho region (data center) — nothing to copy. with a self-client from the zoho api developer console (use the console of your region, e.g. api-console.zoho.eu), provide oto with:

  • client_id and client_secret — from the self client
  • refresh_token — from the grant token exchange
  • data_center — com, eu, in, au, jp or ca (the domain of your zoho sign url: sign.zoho.eu → eu)

    • scopes per access level — read: ZohoSign.documents.READ, ZohoSign.templates.READ · full (default): the same plus ZohoSign.documents.CREATE (send from a template) and ZohoSign.documents.UPDATE (remind, recall). nothing deletes.

    ▸ what you can do

    follow and send zoho sign signature requests from claude.

  • "which requests are still waiting for signature?" → zohosign (op list, status inprogress)
  • "who has signed the nda sent to a@b.com?" → zohosign (op list, search recipient_email), then op get
  • "get the signed pdf" → zohosign (op download_pdf), the completion certificate → op download_certificate
  • "send the partnership template to ann" → zohosign (op get_template) for its recipients and fields, then zohosign_act (op send_from_template, try dry_run first)
  • "remind the signers" → zohosign_act (op remind), "recall this request" → zohosign_act (op cancel)
    • ⚙ 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='zohosign') (scope='org' or scope='group' for the org's or team's)
  • set the default: oto_identity(op='set', connector='zohosign', 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…

    usage

    claude code — install the oto plugin — claude plugin marketplace add otomata-tech/oto-plugin — mcp + skill configured.
    claude.ai — add mcp.oto.cx/mcp as a custom connector (guide)
    cli — pipx install oto-cli then oto zohosign …
    ← tous les connecteurscatalogue mcp →