Twenty CRM

--- name: oo-twenty-crm description: "Twenty CRM (twenty.com). Use this skill for ANY Twenty CRM request — reading, creating, updating, and deleting data. Whenever a task involves Twenty CRM, use this skill instead of calling the API directly." allowed-tools: [Bash(oo *)] metadata: title: "Twenty CRM" author: "OOMOL" version: "1.0.4" services: ["twenty_crm"] icon: "https://static.oomol.com/logo/third-party/twenty_crm.svg" --- # Twenty CRM Operate **Twenty CRM** through your OOMOL-connected account. This skill calls the `twenty_crm` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens. ## Running an action Assume the user has already installed the oo CLI, signed in, and connected Twenty CRM. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error. **1. Inspect the contract** to get the authoritative input/output schema before building a payload: ```bash oo connector schema "twenty_crm" --action "<action_name>" ``` **2. Run the action** with a JSON payload that matches the input schema: ```bash oo connector run "twenty_crm" --action "<action_name>" --data '<json>' --json ``` - `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`. - The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`. Each action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields. ## Available actions - `create_record` — Create one Twenty record for a workspace object. [write] - `delete_record` — Delete one Twenty record by object API name and record UUID. [destructive] - `list_metadata_objects` — List Twenty metadata objects for the connected workspace. - `list_records` — List Twenty records for one workspace object using the generated schema-per-tenant REST API. - `retrieve_record` — Retrieve one Twenty record by object API name and record UUID. - `update_record` — Update one Twenty record by object API name and record UUID. [write] ## Safety - Untagged actions are reads (get / list / search) — safe to run directly. - **Actions tagged `[write]` change Twenty CRM state — confirm the exact payload and effect with the user before running.** - **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.** ## First-time setup These are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason. - **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>): ```bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux ``` ```powershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell ``` - **Not signed in / authentication error** — sign in to your OOMOL account once: ```bash oo auth login ``` - **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Twenty CRM is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at: ```text https://console.oomol.com/connections/twenty_crm ``` - **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying. - **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL. ## Resources - Twenty CRM homepage: https://twenty.com - API documentation: https://docs.twenty.com/developers/extend/api

存档时间线

版本索引永久保留；内容副本只保留最新 1 份，更早版本仅留索引与哈希（存档时间线的证据链不会因此断裂）。

下载存档内容副本

相关资产