360 Secure SkillHub
360 安全技能中心

Sendmator

该 Skill 借助 OOMOL 的 oo CLI 调用 sendmator 连接器，提供联系人查询、创建、更新、删除共五个动作，执行前可先用 schema 子命令读取输入输出契约。凭据由 OOMOL 服务端注入；写操作与删除类破坏性操作需先与用户确认。

oomol
oomol
热度 44.93
最近更新 2026-09-16 15:46:27
分类：营销依赖：代码执行 / 第三方 API应用场景：CRM / API 集成 / 工作流

安装技能

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

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

Sendmator

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

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

oo connector run "sendmator" --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_contact — Create a Sendmator contact with optional external ID, tags, custom fields, and metadata. [write]
  • delete_contact — Permanently delete a Sendmator contact by ID. [destructive]
  • get_contact — Get a Sendmator contact by ID.
  • list_contacts — List Sendmator contacts with cursor pagination and optional filters.
  • update_contact — Update a Sendmator contact's profile fields, active status, tags, custom fields, or metadata. [write]

Safety

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

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

Resources