formfacade.com valid

FormFacade

Agent guidance for FormFacade: branded, customer-facing Google Forms embedded in business websites.

For agents: FormFacade makes Google Forms branded and customer-facing, embeddable in business websites. Agent guidance and docs for customizing Google Forms.

google formsembedded formsform customizationbranded formslead capture

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T14:33:50.900Z. Cached copy · Source on formfacade.com

# FormFacade

> Agent guidance for FormFacade: branded, customer-facing Google Forms embedded in business websites.

FormFacade helps businesses improve the design and customer experience of Google Forms, collect leads and feedback, score answers, and use features such as file uploads, Sheets lookups, prefill, and notifications.

- [FormFacade](https://formfacade.com/)
- [Customize Google Forms](https://formfacade.com/website/)
- MCP endpoint: `https://formfacade.com/mcp/101214642160492007877`

## Before using MCP

Ask the user to sign in and authorize the FormFacade account they want to use. The endpoint's numeric `ownerId` selects the product connector; it is not the user's account ID. Do not request or put a customer `userId` in the URL. Never expose credentials or tokens.

## Create or update forms

- **New form:** use `create_form`. It creates and publishes a live form from `format` (`html` or `markdown`), optional `language`, and a text `document`. Include the title, requested sections, questions, field types, and choices. It accepts text, not binary image/PDF uploads. Convert readable source files to document text first. It returns a preview; do not call `preview` again in the same turn.
- **Existing form:** first call `list_forms`, find the intended form, and use its returned `publishId`; never guess IDs. Use `update_form` with `publishId` and `instruction` to add, change, or remove a field, section, choice, or wording on the live form. Use `get_form` to inspect it and `preview` when asked to view it.
- **Full replacement:** `overwrite_form` and `is_actively_collecting_responses` are not implemented. Do not simulate replacement with `update_form`. The planned `overwrite_form` should support `overwrite: "auto" | "force"`, check response activity since creation, and enforce the check in the same write operation. `force` should only follow the user's explicit request.

The standard product MCP tools are `create_form`, `list_forms`, `get_form`, `update_form`, `preview`, and `progress`. `progress` opens the settings checklist; it does not configure every branding, CSS, embed, or integration feature. `list_submissions` and `analyze_submissions` are disabled. The separate `edit_form` tool is restricted to an API-key-protected edit-only route.

Related sites

Other listed sites in Business software. See the whole category →

Machine-readable: GET /v1/resolve?q=formfacade.com · GET /v1/domain/formfacade.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for formfacade.com:
1. POST https://agentwebmap.com/v1/sites/formfacade.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://formfacade.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/formfacade.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/formfacade.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.