oto.cx
wttj

welcome to the jungle

wttj.

The Welcome to the Jungle organizations this token reaches — start here:

ajouter à otoauth : —prefix : wttj_*

setup & usage

⚠ your welcome to the jungle api token

you need an api token for the welcome to the jungle ats (ex-welcome kit).

  • it cannot be generated in the interface: request it from wttj via help.welcometothejungle.com, describing your use
  • ask for the scopes me_r, organizations_r, jobs_r, candidates_rw (or candidates_r for read-only), comments_w, moves_r
  • paste it into your connector keys (or let your org share theirs)
  • vendor docs: developers.welcomekit.co
    • ▸ what you can do

    drive your wttj ats: everything starts from an organization, a job offer is a job, its stages are read on the job, a candidate belongs to a job.

  • "which organizations can i see?" → wttj_organization (gives the organization_references)
  • "which jobs are published?" → wttj_job(op="list", status="published"); a job's stages → wttj_job(op="get")
  • "who is interviewing for this role?" → wttj_candidate(op="list") with job_reference and job_stage_id; details → wttj_candidate(op="get")
  • "add this candidate" → wttj_candidate(op="create"); "move them to the next stage" → wttj_candidate(op="update", job_stage_id=…); archive → archived=true
  • "log yesterday's conversation" → wttj_comment (write-only: the api does not read comments back)
  • "what moved on this role?" → wttj_moves (per job; requires the moves_r scope on the token)
    • ⚙ 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='wttj') (scope='org' or scope='group' for the org's or team's)
  • set the default: oto_identity(op='set', connector='wttj', 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 wttj …
    ← tous les connecteurscatalogue mcp →