oto.cx
crm attio

attio

crm attio.

crud complet attio : records (companies, people, deals), notes markdown, tasks, lists, entries, threads, meetings, call recordings, workspace members. chaque utilisateur configure sa propre clé api.

ajouter à otoauth : api key (per-user)prefix : attio_*

setup & usage

⚠ your attio api key

attio exposes one api key per workspace. go to your attio workspace's developer settings, api section, and create a key (access token).

  • paste it into oto on your account (/account), attio connector
  • no shared platform key: everyone sets their own
  • remember to tick the records + notes + tasks + lists permissions depending on what you want to do; to touch the schema (attributes, options, deal stages), the object_configuration:read-write permission (list_configuration:read-write for a list)
  • note: the official attio mcp connector is often preferred; oto keeps the code for custom implementations
    • ▸ what you can do

    drive your attio crm (companies, people, deals) + notes, tasks, lists and comments from claude.

  • "look up the company acme" → attio_record(op="search", object="companies"), then attio_record(op="get", object="companies") for the details
  • "create a contact jean dupont at acme" → attio_record(op="create", object="people")
  • "add a note on this deal" → attio_note(op="create") (title + markdown, attached to the record)
  • "list my open tasks" → attio_task(op="list"), and attio_task(op="create") to add one
  • "add the negotiation stage to my deals" → attio_attribute(op="statuses", target="objects", identifier="deals", attribute="stage") to re-read what exists, then attio_attribute(op="create_status", title=…); same gesture for a select option (op="create_option") or a new attribute (op="create", definition). ⚠️ writes the crm schema, and the attio api cannot undo it
    • ⚙ 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='attio') (scope='org' or scope='group' for the org's or team's)
  • set the default: oto_identity(op='set', connector='attio', 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 attio …
    ← tous les connecteurscatalogue mcp →