360 Secure SkillHub
360 安全技能中心

Salesloft

该 Skill 通过 OOMOL 的 oo CLI 调用 salesloft 连接器，提供读取账户、节奏、人员和当前用户的操作，支持分页、排序与过滤；运行前需先用 schema 命令获取输入结构，凭证由服务端注入，用户无需处理令牌，现有动作均为只读。

oomol
oomol
热度 34.16
最近更新 2026-09-15 13:38:19
分类：数据依赖：代码执行 / 第三方 API应用场景：CRM / 数据处理

安装技能

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

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

Salesloft

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

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

oo connector run "salesloft" --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

  • get_account — Fetch a Salesloft account by ID or GUID.
  • get_cadence — Fetch a Salesloft cadence by ID or GUID.
  • get_current_user — Fetch information about the authenticated Salesloft user.
  • get_person — Fetch a Salesloft person by ID or GUID.
  • list_accounts — List Salesloft accounts with optional paging, sorting, and filters.
  • list_cadences — List Salesloft cadences with optional paging, sorting, and filters.
  • list_people — List Salesloft people with optional paging, sorting, and filters.

Safety

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

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

Resources