oto.cx
lightfield

lightfield

lightfield.

Lightfield accounts — the COMPANIES in the CRM: search them, read one, create

add to otoauth : —prefix : lightfield_*

setup & usage

⚠ lightfield api key

create an API key in Lightfield (Settings → API keys, admins only — docs), then paste it into oto.

  • byo-only: no shared oto key — it is your CRM's data, each organization sets its own
  • ⚠️ scopes are chosen at key CREATION and cannot be added afterwards. Tick at least accounts:read, contacts:read, opportunities:read; to write, add the matching :create and :update; to send email, emails:create. A key without CRM read is refused by the "test connection" button, which will tell you the scopes actually granted
  • sending email additionally requires a Google or Microsoft mailbox connected in Lightfield by the key owner
    • ▸ the CRM whose fields belong to you

    Lightfield's field model is specific to EACH workspace: the keys are the ones your team created, not universal names.

  • before the first write → lightfield_accounts(op="definitions") (same for contacts, opportunities, notes, tasks): it is the list of valid keys
  • "which companies in the CRM match…" → lightfield_accounts(op="search", filters={...})
  • "the up-to-date state of this company" → lightfield_accounts(op="get", record_id="…")
  • "create / update this company" → lightfield_accounts(op="upsert", fields={...}) (add record_id to update)
  • custom objects → lightfield_objects(op="list") then op="definitions" on the returned slug
  • write an email from the connected mailbox → lightfield_emails(op="send", sender="…", to=[...], dry_run=False)
    • · three costly pitfalls
  • ⚠️ `op="search"` reads an index that may lag. After a write, re-read with op="get": search may return the state from BEFORE. This is stated in the vendor docs, and it shows most when chaining write-then-verify
  • ⚠️ `limit` caps at 25 (imposed by the API): beyond that, paginate with offset
  • ⚠️ sending can neither reply nor forward: op="send" ALWAYS creates a new message, never a reply in an existing thread — if the context matters, quote it yourself in the body. And op="send" is dry-run by default: you need dry_run=False for anything to go out
    • ⚙ 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='lightfield') (scope='org' or scope='group' for the org's or team's)
  • set the default: oto_identity(op='set', connector='lightfield', 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 lightfield …
    ← tous les connecteurscatalogue mcp →