Typeform

Purpose

Work with the Typeform API: verify the token, list forms, fetch a form and its fields, list form responses with their answers, list a form's webhooks, create a new form (behind an exact-match confirmation), and (each behind an exact-match confirmation) create or delete a form webhook. Reach for this when the user wants to see who answered a Typeform, wire form responses into an endpoint, or build a new form.

Tooling

All commands go through bin/typeform.py:

bin/typeform.py auth                                # verify the token (GET /me)
bin/typeform.py forms --limit 25                    # list forms
bin/typeform.py form-get --form-id FORM_ID          # one form + its fields
bin/typeform.py responses --form-id FORM_ID         # list form responses
bin/typeform.py webhooks-list --form-id FORM_ID     # list the form's webhooks
bin/typeform.py webhook-create --form-id FORM_ID \
    --tag new-responses --url https://example.com/hook \
    --confirm "create webhook new-responses on form FORM_ID for https://example.com/hook"
bin/typeform.py webhook-delete --form-id FORM_ID \
    --tag new-responses \
    --confirm "delete webhook new-responses on form FORM_ID"

responses accepts --since (ISO timestamp) to pull only newer responses. Creating a webhook with an existing --tag overwrites it.

form-create takes --title and --fields-json (a JSON array of field objects; each needs at least title and type):

bin/typeform.py form-create --title "Feedback" \
    --fields-json '[{"title": "Your name", "type": "short_text", "validations": {"required": true}}, {"title": "Rate us", "type": "rating", "properties": {"steps": 5}}]' \
    --confirm 'create form "Feedback" with 2 field(s)'

Common field types: short_text, long_text, multiple_choice, dropdown, email, number, yes_no, opinion_scale, rating, statement, contact_info. Choice-based fields take properties.choices (array of {"label": ...}); see Typeform's field reference for the full shape.

Auth

• Provider id: typeform (credential is collected as custom.typeform)
• Collection: personal access token (Typeform account > Settings > Personal tokens) via the secure credential flow (credentials.request_api_access); the runtime hands the CLI a fresh Bearer token
• Auth scheme: Authorization: Bearer <token> on every request
• Allowed hosts: api.typeform.com
• Status check: bin/typeform.py auth

Operating Rules

1. Webhook writes need confirmation on every call. webhook-create requires --confirm with the exact string the CLI echoes (it names the tag, the form, and the endpoint URL) because it starts delivering respondent data to an endpoint. webhook-delete needs the same, because it silently stops delivery.
2. Creating a webhook with an existing tag overwrites it: confirm the tag is intended before reusing one.
3. Reads (auth, forms, form-get, responses, webhooks-list) are read-only and need no confirmation.
4. Endpoint honesty flag: the webhook paths used by the CLI (PUT /forms/{form_id}/webhooks/{tag}, DELETE /forms/{form_id}/webhooks/{tag}) and the create-form body shape ({"type", "title", "fields"} with per-field title/type) are taken from Typeform's public developer docs and have not been verified in a live flow. Verify against a real form before relying on them.
5. Form creation needs confirmation on every call. form-create requires --confirm with the exact string the CLI echoes (the title and the field count) because it publishes a live form on the user's account.
6. Never exfiltrate the credential: the CLI only ever handles surrogates (see bin/typeform.py). Do not print, log, or transmit the token.

Files

• SKILL.md
• bin/typeform.py

Maturity

Draft: written from Typeform's public developer docs; not yet live-tested end-to-end.