360 Secure SkillHub
360 安全技能中心

Delighted

该 Skill 通过 oo CLI 的 delighted 连接器操作 Delighted 账户，支持查询 NPS 指标、列出调研回复、退订/退信人员名单，以及创建、更新、删除人员和退订操作。凭据由 OOMOL 服务端注入，写入与破坏性操作需先与用户确认。

oomol
oomol
热度 50.88
最近更新 2026-09-15 13:56:26
分类：营销依赖：代码执行 / 第三方 API应用场景：CRM / 市场分析

安装技能

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

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

Delighted

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

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

oo connector run "delighted" --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_or_update_person — Create or update a Delighted person and optionally schedule a survey request. [write]
  • delete_person — Delete a Delighted person and all related survey history. [destructive]
  • get_metrics — Retrieve Net Promoter Score and related metrics from Delighted.
  • list_bounced_people — List bounced people in the connected Delighted account.
  • list_people — List people in the connected Delighted account.
  • list_survey_responses — List survey responses collected in the connected Delighted account.
  • list_unsubscribed_people — List unsubscribed people in the connected Delighted account.
  • unsubscribe_person — Add a person to the Delighted unsubscribe list. [destructive]

Safety

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

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

Resources