360 Secure SkillHub
360 安全技能中心

BoloForms

该 Skill 通过 OOMOL 的 oo CLI 调用 BoloForms 连接器，提供 get_form_responses、list_documents、list_template_respondents 三个读取动作，以及 send_template_for_signing 写入动作。凭据由服务端注入，使用前需已安装并登录 oo CLI；读取动作可直接执行，写入动作需先与用户确认载荷与影…

oomol
oomol
热度 51.09
最近更新 2026-09-15 13:20:53
分类：自动化依赖：第三方 API应用场景：API 集成 / 工作流

安装技能

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

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

BoloForms

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

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

oo connector run "boloforms" --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_form_responses — List response records for a specific form so they can be used in follow-up automations.
  • list_documents — List documents and form statistics from the current BoloForms workspace.
  • list_template_respondents — List the current signing participants and their statuses for a specific template.
  • send_template_for_signing — Start a signing request for a group of participants by using an existing template. [write]

Safety

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

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

Resources