360 Secure SkillHub
360 安全技能中心

AroFlo

该 Skill 借助 OOMOL 的 oo CLI 调用 aroflo 连接器，提供获取单个客户、任务、用户，以及按名称、业务单元、状态、资源和日期等条件列出客户、任务、用户的只读动作。凭据由 OOMOL 服务端注入，使用前需安装并登录 oo CLI 且完成 AroFlo 连接；每次执行的动作输入输出以连接器实时 schema 为准。

oomol
oomol
热度 40.20
最近更新 2026-09-16 15:48:12
分类：搜索依赖：第三方 API / 代码执行应用场景：CRM / 工作流

安装技能

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

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

AroFlo

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

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

oo connector run "aroflo" --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_client — Retrieve a specific AroFlo client by encoded client ID.
  • get_health_status — Retrieve the public health status for the AroFlo API.
  • get_task — Retrieve a specific AroFlo task by encoded task ID.
  • get_user — Retrieve a specific AroFlo user by encoded user ID.
  • list_clients — List AroFlo clients with optional partial-name filtering and field selection.
  • list_tasks — List AroFlo tasks with business unit, status, resource, date, and pagination filters.
  • list_users — List AroFlo users for an organisation with optional name and access filters.

Safety

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

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

Resources