360 Secure SkillHub
360 安全技能中心

Fillout

该 Skill 通过 OOMOL 的 oo CLI 调用 Fillout connector，支持列出表单、读取表单元数据与提交记录，以及创建和删除提交。写入与删除操作要求先确认；首次使用需安装 CLI、登录并连接 Fillout，凭据由服务端托管。

oomol
oomol
热度 53.52
最近更新 2026-09-15 12:20:38
分类：数据依赖：代码执行 / 第三方 API应用场景：数据处理 / 工作流

安装技能

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

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

Fillout

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

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

oo connector run "fillout" --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_submissions — Create one or more submissions for a Fillout form. [write]
  • delete_submission — Delete one Fillout form submission by submission ID. [destructive]
  • get_form_metadata — Get metadata and configured questions for one Fillout form.
  • get_submission — Get one Fillout form submission by submission ID.
  • list_forms — List forms available to the authenticated Fillout account.
  • list_submissions — List submissions for one Fillout form with documented pagination and filters.

Safety

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

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

Resources