Changelog

Connect multiple Google accounts and choose an account for each form’s uploads and Sheets destination. When retiring an account, move future uploads or unpublish affected forms. Archive it to retain historical file access, or disconnect it while keeping response records and files in Drive. Reconnect the original account to restore access.

Every visible question now needs a label before publishing. With field suggestions enabled, finishing a new question can also add an example placeholder, useful help text, or choices and scale labels already listed in your question. Your labels, required settings, and authored details stay yours.

New questions can use Gemini to suggest an answer type from their wording, including explicit numeric scales. The answer control appears immediately and can update after a typing pause. Manual type choices and edited options stay yours. If suggestions are unavailable, writing continues with the local candidate.

New forms open straight in the editor. Write questions and edit choices, rankings, matrix labels, and repeated questions on the page. Use each block's grip to change its type or settings, drag to a marked destination, and undo edits. Preview the form and adjust its light and dark palettes from the same toolbar.

Remote agent connections now use signed tokens limited to Fillo's MCP endpoint and the permissions you approve. Existing valid connections upgrade during their normal token refresh, keeping their permissions and grant expiry. New clients can connect through metadata URLs; existing client registration remains available. Your forms, responses, and usual Fillo sign-in stay in place.

Drafts now open in the editor; published forms open in Responses, with publishing and sharing alongside the answers. Starting with a coding agent uses one copyable prompt. Browse compact template summaries and open a live preview only when you choose a form.

Server signatures can now bind respondent names, email addresses, and traits to their account ID. Legacy ID-only signatures retain account identity while unsigned profile values are discarded. Unverified reply addresses are labeled in team emails, and fixed-text receipts have shared per-recipient caps that survive restarts.

Signing in now returns you to your last-used project, including from another browser. Choosing a project, creating one, or opening a form updates that preference. A specific form or invitation link still takes you to its intended destination.

Team emails with selected answers and a valid respondent reply address now contain the questions and answers in plain text, with a short Sent via Fillo footer. Reply or forward them without carrying management links or administrative notes into the conversation. Link-only notifications still keep answer content private.

Select responses with the checkboxes on the left, or hold Shift to select a range. Re-send selected responses, download them as CSV, or delete them with their uploaded files. The header checkbox selects the loaded rows. In a response's actions menu, Copy includes every question and answer, including hidden values, ready to paste into a coding agent for debugging.

CLI and local MCP installations now run newer compatible stable releases automatically. The CLI also refreshes skills it manages in your current project and user scope. Start an existing installation with @latest once to enable updates. Checks happen at most hourly, fall back offline, and can be disabled with FILLO_AUTO_UPDATE=0. SDK dependencies still follow your package manager.

MCP connections can now choose a task area or search tools and read one contract at a time. Response reads can select answer fields or return only row identifiers and timestamps. Existing connections keep their complete tool catalogue, and every call keeps its project permissions and approval checks.

Team emails can now include the answers you choose. Select a respondent email field and Reply goes directly to that person from your mailbox. Each email opens its specific response in Fillo. Notifications are queued and retried after temporary failures, with delivery status and retry in Responses. Existing forms keep link-only emails until you opt in.

Connecting ChatGPT or Claude now prepares a new account's workspace before you approve access. Build with agent offers a prompt for your connected chat agent or your coding agent, and live forms guide you through collecting and checking your first response.

If your code ships a form Fillo can't render, such as the same field id twice, visitors now see the version you published on Fillo instead of an error. Development shows the reason, the form's Overview says what's wrong, and you get one email a day until it's fixed.

Forms your agent creates through Fillo's MCP now open in the dashboard editor like any other form, and your agent can keep updating them. If you've changed a form since the agent's last update, the agent is asked to start from your version, so your edits are never overwritten. Forms synced from code can switch to the dashboard in one step.

Limit a form to one response per verified email, and people confirm their address with a 6-digit code before they fill it in. Their device stays confirmed for 30 days. Let them update their answer and start the date on today, and a daily diary opens on today's entry, ready to add to or correct.

A form can now carry its own light and dark colors and follow the visitor's device. Its Fillo link takes on the form's look: the page wears its background and color mode, with your logo above the form. Set both in the Design panel, or with theme.dark and theme.logo from code and agents. Buttons also pick readable text for any accent color.

Everything now comes in three volumes: 5,000, 25,000, or 100,000 completed responses a month, from €35 ($39). Yearly billing gets two months free. There's no overage: a form keeps collecting when you go over, and Fillo emails you at 80% and 100% to suggest the next volume. Subscribe and manage billing in Settings → Billing & plan.

Paste one setup prompt into Claude Code, Codex, Cursor, or any coding agent, or follow the steps for yours. In Claude Code and Codex, one plugin installs the Fillo skill and the hosted MCP server together. Cursor and VS Code add the MCP server in one click.

Fillo now supplies account names, email addresses, and workspace/project labels to OpenAI clients that support multiple connections. A stable account identity helps the client recognize the same Fillo account after you reconnect. Each tool call keeps the selected connection's project and permissions.

Download a working n8n workflow and Postgres setup for client intake. It saves one review item per response, preserves review status when answers change, and handles repeated or out-of-order deliveries. The guide includes credential setup and recovery after a failed database write.

Claiming a preview now helps you switch to the account that owns it. Email signup lets you correct an address without losing your name, and creates your account only after you open the sign-in link. Agent setup guides now finish with an explicit workspace claim, so a temporary preview is not mistaken for a saved account.

Everything in the dashboard now works from the terminal, the management API, and MCP: publish and unpublish, release held responses, retry delivery, switch destinations on or off, and manage members, storage, origins, and credentials. Outward changes ask before they run, and anything irreversible needs the target typed out — or, for an agent, a person’s click.

Forms now open on Overview with navigation focused on that form. Review responses without leaving the page, find forms and settings from one search, and add integrations from a searchable catalog. Settings, sign-in, and agent setup share clearer controls, with copyable setup prompts for your coding agent.

Set an upload field’s Max files to as many as 200 in the form editor. Hosted forms handle large selections in batches, and saved progress keeps every uploaded file. Existing forms keep their configured file limits.

Choose a Google Drive folder for each form from Settings → File storage, or keep Fillo's automatic folder. See the selected folder and open it in Drive. Folder changes apply to new uploads; existing files stay in place. You can return to the default folder at any time.

Search the product form library by what you need: try ‘customers leaving’, ‘bugs’, or ‘AI feedback’. Every form now has its own link, with a working preview and the original sources, so you can share a specific form with your team.

Feedback, bug reports, onboarding, and research forms, with sources you can inspect. Try a form, enter your email, and save it to a workspace immediately. Add your product’s details, publish, and share a link; confirm your email afterward. Agents can use the same questions and schemas.

If you start a preview through the CLI or an agent and leave it unclaimed, Fillo now sends a few early reminders with a fresh workspace link. Open the newest link to save the workspace to your account and keep building.

Reorder choice options directly in the builder, create prefilled links without assembling query strings by hand, and share hosted forms with a social card generated from the form itself.

Connect Discord once, choose a channel for each form, and triage responses from the message. The new n8n community node starts workflows on accepted responses and reads forms and responses without a custom bridge.

Start with the file request itself, choose Google Drive, Box, Amazon S3, or Cloudflare R2, and send people a hosted upload link. Large files travel browser-direct to the connected destination while Fillo keeps the response and file reference together.

Keep forms, responses, API keys, and destinations isolated by project while sharing the workspace bill, members, storage connections, and reusable integration accounts.

Turnstile now works on any embed domain through a small Fillo-hosted challenge frame. The check stays invisible unless Cloudflare needs a click, and host pages no longer need to load Cloudflare's script.

From the same coding session, an agent can provision or select a project, scaffold a form, publish it, inspect responses, and hand the workspace back to you. The CLI, local MCP server, and remote MCP path now share that lifecycle.

Send accepted responses to public or private Slack channels without pasting a webhook. In HubSpot, record native form activity on the Contact timeline and optionally create or update associated Companies and Deals.

Collect guest lists, order lines, work history, or any bounded set of repeated answers. Respondents add and remove instances, validation stays scoped to each row, and responses remain structured across the grid, API, CSV, and webhooks.

Calculate totals and other numeric values live from validated answers, then use the result in logic, headings, exports, and destinations. Number inputs also gain decimal precision, prefixes, suffixes, and thousands separators without changing the stored value.

Phone input, keyboard behavior, screen-reader announcements, focus states, forced colors, right-to-left layouts, and dark mode all received a full pass. The DOM renderer also adds file progress, cancel, retry, and the same human-check flow as React.

Reference pages, practical migration and framework guides, built-in search, Markdown twins, and llms.txt now make the same product guidance useful to people and coding agents.

Require a server-verified Turnstile challenge per form, or branch a multi-page flow to another page or directly to completion. The renderer and server share the same reachability rules, so skipped required fields stay skipped.

Connect a compatible coding agent to Fillo to provision a workspace, scaffold and publish forms, and inspect responses without leaving the session. The hosted and local MCP paths use the same Fillo APIs and project boundaries.

See whether each webhook, integration, and notification was delivered, is retrying, or failed. Per-destination health and one-click replay make the handoff visible after a response is accepted.

Require identity signed by your server and hold every other submission in a quarantined view. Held responses stay out of destinations, notifications, exports, and counts until your team releases them.

Create scoped, revocable keys and manage Fillo server-to-server: list forms and versions, page through responses, inspect respondent history, and delete responses through the versioned API.

Override field, validation, navigation, and upload strings so an embedded form speaks the same language as the surrounding product. Failed uploads now offer retry, and conditional logic works across pages.

Insights are now cohort-driven, and each number opens the responses behind it. The daily digest uses the same view of starts and drop-off.

Choose who counts as the same respondent and what happens when they return: identify by browser, contact field, or signed-in person, then keep the first answer or let a verified person update it.

Use the Google picker to choose a spreadsheet and tab you already own instead of creating a new destination for every form.

Recognize a signed-in person, optionally verify that identity on your server, and let them resume in-progress answers across reloads or devices. In-progress responses, resume links, and a daily digest make drop-off visible.

Author a form with Fillo JSX components that compile to the same schema as defineForm, then restyle every rendered part through appearance classes and data attributes.

Start a Zap the moment a new response arrives. REST hooks deliver per-form output fields, so downstream steps can map real answer names instead of guessing from a generic payload.