← 返回 Skills 市场
6734
总下载
3
收藏
0
当前安装
17
版本数
在 OpenClaw 中安装
/install jotform
功能描述
JotForm API integration with managed OAuth. Create forms, manage submissions, and access form data. Use this skill when users want to interact with JotForm forms and submissions. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a JotForm connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a JotForm action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with JotForm examples; they add no JotForm capability - JotForm is not an event source, a trigger cannot read JotForm data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
安全使用建议
Install only if you intend to let Maton connect to your JotForm account. Review any write, deletion, webhook, trigger, destination, or hosted-function action before approving it, because those can change form data or create ongoing forwarding of future submissions.
能力评估
Credentials
Requested Bash, Read, Grep, and Glob plus network access are proportionate to invoking a CLI-based API gateway. The raw HTTP/API-key fallback is limited to environments where the CLI cannot be installed and includes secret-handling warnings.
Install Mechanism
Installation uses pinned Maton CLI/SDK versions via npm, Homebrew, pip, or npm SDK. This is purpose-aligned for an API integration, though users are trusting the Maton toolchain and account connection.
Instruction Scope
Runtime instructions default to read/list operations, require explicit user approval for connection creation and all POST/PUT/PATCH/DELETE actions, and warn that external API content and trigger payloads are untrusted data.
Persistence & Privilege
OAuth credentials, webhooks, hosted functions, triggers, destinations, and watch checkpoints can persist beyond one run. The artifact discloses this and adds approval, least-privilege, deletion, and destination-scope guidance, so no hidden persistence was found.
Purpose & Capability
The skill's capabilities match its stated purpose: JotForm OAuth access, form/submission reads, form and submission writes, webhook management, and optional Maton-hosted functions/triggers. These can affect business data, but the artifact repeatedly scopes them to the user's connected JotForm account and documented endpoints.
如何使用
- 确保已安装 OpenClaw（本地或 Docker 部署）
- 在对话框中输入安装命令：
/install jotform - 安装完成后，直接呼叫该 Skill 的名称或使用
/jotform触发 - 根据 Skill 的参数说明提供必要输入，即可获得结构化输出
版本历史
v1.2.9
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.8
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.7
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.6
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.5
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.4
- Removed the skill-card.md file for a cleaner project structure.
- No changes to functionality or user experience.
v1.2.3
Fix the raw HTTP fallback example: restore the gateway base URL in the GATEWAY constant (and the fastmail streaming call), which a previous edit had replaced with a placeholder
v1.2.2
Resolve remaining audit findings: state one consistent endpoint policy instead of conflicting scope claims, qualify the local-execution and high-impact wording, note that locale examples are illustrative, and correct app-specific auth, method and upload-path documentation
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.5
- Changed API and connection management base URLs from gateway.maton.ai/ctrl.maton.ai to api.maton.ai.
- Updated all code examples and references to use the new api.maton.ai endpoint.
- Clarified connection header usage, now specifying to always include Maton-Connection when using multiple connections.
- Added Security & Permissions section, requiring explicit user confirmation for any write operations.
- Minor corrections and improved instructions throughout the documentation.
- Removed the LICENSE.txt file.
v1.0.4
- Added metadata section for clawdbot integration, including a brain emoji and required MATON_API_KEY environment variable.
- No other changes detected.
v1.0.3
- Added troubleshooting guidance for "Invalid App Name" errors and clarified correct API URL paths.
- Expanded the resources section with links to the Maton Community and support.
- Updated error troubleshooting to separate API key and app name issues for better clarity.
- No functional changes to the API or usage; documentation improvements only.
v1.0.2
- Added a note in the description recommending the api-gateway skill for third party apps other than JotForm.
- Replaced most shell/curl examples with Python code snippets using urllib for easier cross-platform use and improved environment variable handling.
- Added important notes about using curl with bracketed URLs (`curl -g`) and shell environment variable expansion issues when piping output (e.g., with jq).
- Added a "Troubleshooting: Invalid API Key" section with step-by-step debugging instructions.
- Minor updates to authentication header instructions for clarity.
v1.0.1
- Base URL section clarified: Now instructs to use `{native-api-path}` to match the JotForm API endpoint.
- Getting an API key: Now explicitly states users can "sign in or create an account".
- Connection details updated: Connection JSON response now includes `creation_time`, `last_updated_time`, and `metadata`.
- New section: Added instructions for specifying a JotForm connection via the `Maton-Connection` header for users with multiple connections.
- General documentation improvements for clarity and completeness.
v1.0.0
JotForm API integration skill v1.0.0
- Initial release of JotForm API integration with managed OAuth via Maton.
- Create, retrieve, and delete forms and submissions.
- Manage webhooks on JotForm forms.
- Supports connection management through Maton control panel.
- Includes comprehensive usage instructions and code examples for authentication and API access.
元数据
常见问题
JotForm 是什么？
JotForm API integration with managed OAuth. Create forms, manage submissions, and access form data. Use this skill when users want to interact with JotForm forms and submissions. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a JotForm connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a JotForm action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with JotForm examples; they add no JotForm capability - JotForm is not an event source, a trigger cannot read JotForm data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 6734 次。
如何安装 JotForm？
在 OpenClaw 或 Claude Code 对话框中运行命令「/install jotform」即可一键安装，无需额外配置。
JotForm 是免费的吗？
是的，JotForm 完全免费，采用 MIT-0 许可证，可自由下载、安装和使用。
JotForm 支持哪些平台？
JotForm 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。
谁开发了 JotForm？
由 byungkyu（@byungkyu）开发并维护，当前版本 v1.2.9。
推荐 Skills