360 Secure SkillHub
360 安全技能中心

Workiz

该 Skill 通过 OOMOL 的 oo CLI 调用 Workiz 连接器，提供 get_job、get_lead、list_jobs、list_leads、list_team_members 五个只读动作，可按标识获取单条记录，或按日期、状态与分页条件列出工单和线索。凭据由 OOMOL 服务端注入，首次使用需安装 oo CLI 并登录 OOMOL 账号。

oomol
oomol
热度 23.06
最近更新 2026-09-15 12:27:36
分类：数据依赖：代码执行 / 第三方 API应用场景：CRM

安装技能

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

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

Workiz

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

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

oo connector run "workiz" --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_job — Get one Workiz job by its unique identifier.
  • get_lead — Get one Workiz lead by its unique identifier.
  • list_jobs — List Workiz jobs with date, offset, open-state, and status filters.
  • list_leads — List Workiz leads with date, offset, open-state, and status filters.
  • list_team_members — List active team members in the connected Workiz account.

Safety

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

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

Resources