360 Secure SkillHub
360 安全技能中心

Detrack

提供 Detrack 连接器的动作清单（创建、删除、查询、列出、搜索、更新作业及仓库列表），先获取动作 schema 再以 JSON 负载执行；写与删除操作须经用户确认；凭证由 OOMOL 服务端注入，首次使用需安装 CLI 并完成登录与连接。

oomol
oomol
热度 39.45
最近更新 2026-09-15 12:42:13
分类：自动化依赖：代码执行 / 第三方 API应用场景：API 集成 / 工作流 / 任务管理

安装技能

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

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

Detrack

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

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

oo connector run "detrack" --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_job — Create a delivery or collection job in Detrack API V2. [write]
  • delete_job — Delete one Detrack job identified by D.O. number and date. [destructive]
  • get_job — Retrieve one Detrack job by D.O. number and date.
  • list_depots — List depots available in the connected Detrack account.
  • list_jobs — List and filter delivery or collection jobs from Detrack API V2.
  • search_jobs — Search Detrack jobs with structured operational and customer filters.
  • update_job — Update selected fields on one Detrack job identified by D.O. number and date. [write]

Safety

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

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

Resources