360 Secure SkillHub
360 安全技能中心

GoDial

该 Skill 封装 GoDial 连接器的 5 个动作：列出账户、列出列表、列出列表内联系人、按 ID 获取联系人、创建联系人。使用前先用 schema 命令获取动作的输入输出约定，再用 JSON 载荷执行；写入类动作要求先获得用户确认。凭据由 OOMOL 服务端注入，需已安装并登录 oo CLI。

oomol
oomol
热度 52.73
最近更新 2026-09-16 15:40:04
分类：营销依赖：代码执行 / 第三方 API应用场景：CRM / 工作流 / 任务管理

安装技能

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

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

GoDial

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

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

oo connector run "godial" --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 one GoDial contact in a target list using the official external API form fields. [write]
  • get_contact — Fetch one GoDial contact by contact ID.
  • list_accounts — List GoDial accounts in the current company.
  • list_contacts_in_list — List all contacts currently stored in one GoDial list.
  • list_lists — List GoDial lists in the current company.

Safety

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

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

Resources