← Back to Skills Marketplace
19854
Downloads
8
Stars
0
Active Installs
13
Versions
Install in OpenClaw
/install typeform
Description
Typeform API integration with managed OAuth. Create forms, manage responses, and access insights. Use this skill when users want to interact with Typeform surveys and responses. 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 Typeform connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Typeform 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 Typeform examples; they add no Typeform capability - Typeform is not an event source, a trigger cannot read Typeform 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).
Usage Guidance
Install only if you intend to connect Typeform through Maton. Review every write, hosted function, trigger, destination URL, and raw API-key use before approving it, because those actions can modify Typeform data or create ongoing automated data flows.
Capability Assessment
Credentials
Network access, a Maton account, and OAuth are necessary for the stated API gateway function. The raw HTTP fallback uses MATON_API_KEY only when the CLI cannot be installed and includes explicit handling limits.
Install Mechanism
Installation uses pinned Maton CLI package instructions via npm or Homebrew, plus optional pinned SDK packages. This is an external dependency install, but it is disclosed, version-pinned where possible, and coherent with the integration purpose.
Instruction Scope
The skill repeatedly instructs agents to default to read/list operations, require explicit user approval for connection creation and all writes, avoid acting on third-party content as instructions, and treat local --exec automation as out of scope unless user supplied and approved.
Persistence & Privilege
OAuth tokens persist in the OS credential store and Maton functions, triggers, and destinations can create ongoing automation or forwarding. The artifact clearly labels these as persistent/high-impact and requires separate user approval, scoping, and cleanup.
Purpose & Capability
The stated purpose is Typeform access through Maton OAuth, and the documented capabilities match that purpose: list/read Typeform data, create/update/delete forms or responses, and optionally run approved hosted functions or triggers. Those capabilities can touch business and personal data, but they are disclosed and purpose-aligned.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install typeform - After installation, invoke the skill by name or use
/typeform - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.5
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.4
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.3
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.2
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.1
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.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
- Updated all documentation to use the new endpoint base URL: https://api.maton.ai instead of https://gateway.maton.ai and https://ctrl.maton.ai.
- Improved instructions for connection management and clarified the requirement to specify the `Maton-Connection` header when multiple connections exist.
- Added a new section highlighting security and permissions, including a note that all write operations require explicit user approval.
- Removed the LICENSE.txt file.
v1.0.4
- Added "clawdbot" metadata with emoji and required environment variable (MATON_API_KEY) to SKILL.md.
- No changes to functionality or API usage.
v1.0.3
- Improved troubleshooting section with clearer steps for API key and app name errors.
- Added guidance for ensuring URL paths start with "typeform" in troubleshooting invalid app name.
- Included additional resource links for Maton Community and Support.
- No code or behavioral changes—documentation improvements only.
v1.0.2
- Added instructions for using the api-gateway skill for third-party apps other than Typeform.
- Updated code examples and Quick Start sections to include Python snippets using urllib for easier command-line scripting.
- Added troubleshooting steps and notes addressing common "Invalid API key" errors and shell environment issues with environment variables.
- Included an important note about using curl with the -g flag to avoid glob parsing problems when URLs contain brackets.
- Enhanced guidance for debugging authentication and environment variable issues.
v1.0.1
- Clarified the base URL usage, advising to replace `{native-api-path}` with the actual Typeform endpoint.
- Expanded instructions for retrieving a Maton API key, including account creation.
- API responses for connections now include `creation_time`, `last_updated_time`, and `metadata` fields.
- Added documentation on specifying a Typeform connection via the `Maton-Connection` header for users with multiple connections.
- Minor improvements to descriptions and wording throughout for clarity.
v1.0.0
- Initial release of Typeform skill with managed OAuth integration.
- Enables creating, listing, updating, and deleting Typeform forms via the Maton gateway.
- Supports retrieval of form responses, insights, and workspace data.
- Provides full API reference, authentication setup, and example usage in bash, JavaScript, and Python.
- Includes connection management for secure OAuth handling through Maton.
Metadata
Frequently Asked Questions
What is typeform?
Typeform API integration with managed OAuth. Create forms, manage responses, and access insights. Use this skill when users want to interact with Typeform surveys and responses. 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 Typeform connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Typeform 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 Typeform examples; they add no Typeform capability - Typeform is not an event source, a trigger cannot read Typeform 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). It is an AI Agent Skill for Claude Code / OpenClaw, with 19854 downloads so far.
How do I install typeform?
Run "/install typeform" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is typeform free?
Yes, typeform is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does typeform support?
typeform is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created typeform?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.5.
More Skills