360 Secure SkillHub
360 安全技能中心

Twenty CRM

该 Skill 通过 OOMOL 的 oo CLI 调用 twenty_crm 连接器，在已连接的 Twenty CRM 工作区中列出元数据对象，并按对象 API 名称与记录 UUID 查询、创建、更新或删除记录。凭据由 OOMOL 服务端注入；写操作与删除操作需先与用户确认。首次使用可能需安装 CLI、登录并连接账号。

oomol
oomol
热度 44.55
最近更新 2026-09-15 13:18:47
分类：自动化依赖：代码执行 / 第三方 API应用场景：CRM / 工作流 / 数据处理

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-twenty-crm
Metadata
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.2","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; 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 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:

oo connector schema "twenty_crm" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

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):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    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:

    https://console.oomol.com/app-connections?provider=twenty_crm

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources