360 Secure SkillHub
360 安全技能中心

Salesmate

该 Skill 通过 oo CLI 调用 Salesmate 连接器，按动作 schema 执行公司查询/创建、产品创建/删除、活跃用户列表和模块列表等 CRM 操作；写入与删除动作需先向用户确认，凭证由 OOMOL 服务端注入。

oomol
oomol
热度 41.85
最近更新 2026-09-15 13:51:24
分类：协作依赖：代码执行 / 读写文件 / 第三方 API应用场景：CRM

安装技能

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

执行命令安装此 skill： npx secure-skills-cli add oo-salesmate
Metadata
name
oo-salesmate
description
Salesmate (salesmate.io). Use this skill for ANY Salesmate request — reading, creating, updating, and deleting data. Whenever a task involves Salesmate, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Salesmate","author":"OOMOL","version":"1.0.2","services":["salesmate"],"icon":"https://static.oomol.com/logo/third-party/salesmate.svg"}

Salesmate

Operate Salesmate through your OOMOL-connected account. This skill calls the salesmate 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 Salesmate. 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 "salesmate" --action "<action_name>"

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

oo connector run "salesmate" --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_company — Create a company record in Salesmate CRM. [write]
  • create_product — Create a product in Salesmate. [write]
  • delete_product — Delete a Salesmate product by product ID. [destructive]
  • get_active_users — List active Salesmate users.
  • get_company — Get a Salesmate company record by company ID.
  • list_modules — List Salesmate internal module identifiers.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Salesmate 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 — Salesmate 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=salesmate

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

Resources