Forms that think.

Showing 25 of 30 from the live probe.

• Create a form

  Create a new form, survey, questionnaire, or intake form from a title and a complete list of fields. Use when the user wants to make/build/create a form, survey, poll, intake, registration, application, or feedback form. Works without sign-in: returns a draftToken for an anonymous draft that can be edited and previewed immediately. Pass the FULL field list in one call rather than adding fields one by one. Signed in, the form is created in the active workspace (the result names it) — if the user

• Update form details

  Change a form's title, description, URL slug, settings (language, retention, thank-you message, redirect, welcome screen, presentation/layout, embed behavior) or branding/design (theme colors, font, logo, background image). Use this DIRECTLY for any design/theming request on a form — 'make it dark', 'use a serif font', 'add a background image', 'make the logo bigger', 'rounder corners', 'add a welcome screen' — no need to call get_form or get_brand_kit first: theme patches merge one level, and o

• Get the brand kit

  Show the workspace's brand kit: the org-level brand definition (logo, colors, font, corner radius, tone of voice) that every form inherits as its default design. Use when the user asks about their brand, brand kit, brand colors/logo, or why forms look the way they do. Individual forms override it via update_form branding.theme.

• Set the brand kit

  Set or update the brand kit — the brand definition (logo, colors, font, radius, tone of voice) applied as design defaults to EVERY form in the ACTIVE workspace, existing and future, with no republish. Use this DIRECTLY (no need to list workspaces or forms first) whenever the user wants their forms to match their brand: 'make all my forms look like my brand', 'set up my brand colors', 'use the logo and colors from my website'. If asked to read their website, extract the logo URL and brand color y

• Add fields

  Add one or more questions/fields to an existing form, optionally at a specific position (0 = first).

• Update a field

  Change one field/question on a form: label, required, options, bounds, validation, or adaptive follow-up config. Identify the field by its key.

• Remove a field

  Remove one field/question from a form by its key. Does not delete collected responses.

• Reorder fields

  Set the exact order of a form's fields. Pass every existing field key exactly once, in the new order.

• Split a form into steps

  Turn a form into a multistep form (a funnel/wizard) by defining ordered pages/steps and which fields go on each — or make it single-page again by passing an empty pages list. Use this DIRECTLY (no need to call get_form first) whenever the user asks to split, group, break up, or reorganize a form's questions into steps, pages, sections, or funnel stages ('make it multistep', 'split into three steps', 'group questions into pages', 'typeform-style funnel'). Validation is self-correcting: if a field

• Import an image to forms.ax hosting

  Copy an image from a public https URL onto forms.ax hosting (EU storage, served from the workspace's own form domain) and get back a stable URL. Use BEFORE setting a logo, background image, or image block when the user's image lives on their website or another host — imported assets never break from hotlink changes, never cause mixed-content warnings, and let no third party track respondents. Then use the returned url in set_brand_kit (logo_url), update_form branding.theme.backgroundImageUrl, or

• Design the form layout

  Design Mode: add content blocks between a form's questions and put fields side by side in columns. Use this DIRECTLY (never call get_form first) whenever the user asks to add an image, photo, picture, text/explanation, YouTube/Vimeo video, or divider to the form itself, or wants fields side by side / on one row / in two columns ('put first and last name side by side'). Blocks: { key, type: image|text|video|divider, url (image/video), alt, markdown (text: paragraphs, **bold**, *italic*, [links](h

• Configure AI follow-ups

  Enable or disable AI follow-up questions ('adaptive intake') on a text field, with a natural-language instruction describing what a complete answer contains. When a respondent answers too thinly, the form asks up to max_followups clarifying questions inline.

• Publish form

  Publish a form so respondents can fill it in — returns the public URL to share. Requires sign-in (triggers it automatically). Use when the user wants to publish, go live, share, or get the link to a form. Republish after edits to make them live.

• Close form

  Stop accepting new responses on a published form. Existing responses are kept. Use when the user wants to close, pause, or stop a form.

• Delete form

  Permanently delete a form AND all its responses. Irreversible. Requires confirm: true after the user has explicitly confirmed.

• Send test response

  Submit a sample/test response to a published form so summaries and analysis have data to work with. Sample answers are generated unless provided.

• Configure notifications

  Set where new-response notifications go for a form: email addresses, Slack, and/or a webhook URL (HTTPS POST per response). For Slack, prefer slack: "connect" — it returns a link the user clicks to pick a channel (no webhook setup on their side).

• Connect an integration

  Continuously sync each new completed response into an external tool: google_sheets (rows in a spreadsheet), notion (items in a database), airtable (records in a table) or hubspot (CRM contact + note per response). Returns a link the user clicks to authorize — forms.ax creates the spreadsheet/database/table automatically. Use action "disconnect" to stop syncing. For a one-time CSV download use export_responses instead; for email/Slack/webhook notifications use configure_notifications.

• List forms

  List the user's forms with status, response counts and public URLs. Use when the user asks what forms they have, or to find a form's id.

• Get form details

  Get one form's full definition: fields, settings, branding, status, public URL, QR-code link and embed snippet (when published). Read-only — for showing the user their form. NOT needed before editing: the edit tools (update_form, set_layout, set_pages, field tools) work directly and return actionable errors.

• List responses

  List responses to a form (paginated, scoped — never an unbounded dump). Use when the user asks to see, read, or browse responses/submissions/answers.

• Get a response

  Get ONE specific response in full, including its adaptive follow-up transcript. Use when the user points at a single response ('show me response number 5', 'open that response', 'the details of Jane's answer'). For browsing several responses use list_responses instead.

• Summarize responses

  Summarize open-text answers into themes, sentiment and notable outliers. Use when the user asks what people said, for common themes, feedback summary, or sentiment.

• Analyze responses

  Compute counts, choice distributions, number/rating stats, completion rate, drop-off, and the adaptive-vs-static A/B comparison. Use for stats, numbers, breakdowns, how many, completion rate.

• Export responses (CSV)

  Export all of a form's responses as a CSV file and return a time-limited download link.