360 Secure SkillHub
360 安全技能中心

Onfleet

该 Skill 通过 oo CLI 调用 OOMOL 的 onfleet 连接器，用于读取、创建、更新、克隆、完成和删除 Onfleet 配送任务。运行前可用 schema 查看动作字段，写入或破坏性操作需用户确认；凭证由 OOMOL 服务端注入。

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

安装技能

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

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

Onfleet

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

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

oo connector run "onfleet" --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

  • clone_task — Clone an existing Onfleet task with optional metadata and field overrides. [write]
  • complete_task — Force complete an active Onfleet task as successful or failed. [destructive]
  • create_task — Create a pickup or delivery task in Onfleet. [write]
  • delete_task — Delete an unstarted Onfleet task. [destructive]
  • get_task — Get one Onfleet task by ID.
  • list_tasks — List Onfleet tasks in a time range with cursor pagination and task filters.
  • update_task — Update supported fields on an Onfleet task. [destructive]

Safety

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

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

Resources