typeform-integration_skill

This skill helps you manage Typeform data by connecting, listing, and updating forms, workspaces, and resources through Membrane.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill typeform-integration

  • _meta.json281 B
  • SKILL.md5.8 KB

Overview

This skill provides a Typeform integration I created to manage forms, responses, themes, images, webhooks, and workspaces through the Membrane CLI. It lets you list, retrieve, create, update, and delete Typeform resources while Membrane handles authentication and token refresh. Use it when you need programmatic access to Typeform data without managing API keys or auth flows.

How this skill works

The skill invokes Membrane CLI actions and proxy requests to call Typeform endpoints. It discovers available actions (list-forms, get-form, list-responses, create-webhook, etc.), passes JSON inputs, and executes them under an established Membrane connection. For custom needs, it proxies raw HTTP requests to the Typeform API while injecting correct auth headers and base URL.

When to use it

  • Synchronize form metadata or responses into your data warehouse or CRM.
  • Automate creation or updates of forms, themes, or workspaces.
  • Audit or backup all forms, webhooks, and images from an account.
  • Fetch responses for reporting, segmentation, or follow-up workflows.
  • Trigger or manage webhooks programmatically for integration pipelines.

Best practices

  • Always create a Membrane connection instead of sharing API keys; Membrane manages credentials and refresh.
  • Run membrane action list --intent=QUERY to discover existing actions before crafting custom API calls.
  • Prefer pre-built Membrane actions for pagination and edge-case handling to reduce complexity and token use.
  • Use membrane request proxy only for endpoints not covered by actions, and pass JSON with --json for clarity.
  • Test in a non-production workspace first when deleting forms or responses to avoid accidental data loss.

Example use cases

  • Export all responses for a specific form to a CSV nightly using list-responses and a simple transform.
  • Create branded themes then apply them to new forms via create-theme and update-form actions.
  • List workspaces and enumerate their forms to generate a backup manifest of form IDs and metadata.
  • Programmatically create or update webhooks for a survey workflow to forward responses to a webhook consumer.
  • Proxy a custom Typeform API endpoint to retrieve advanced analytics not available in pre-built actions.

FAQ

No. Create a Membrane connection and authenticate in the browser; Membrane securely handles tokens for you.

Can I run arbitrary Typeform API calls?

Yes. Use membrane request to proxy HTTP calls to the Typeform API when pre-built actions don't cover your use case.

How do I find the correct action ID for an operation?

Run membrane action list --intent=QUERY --connectionId=CONNECTION_ID to discover action IDs and input schemas.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational