Connect ChatGPT or Claude
Open Build with AI on Dashboard, choose ChatGPT or Claude, or open Account → AI Form Builder and choose the provider tab. Provider account features and connector availability can change independently of EZFormz, so follow the setup shown by the provider instead of relying on a promised external plan name.
For ChatGPT, open the EZFormz Form Builder from the ChatGPT tab. Send a first message or use its connection starter, sign in only on ezformz.net, review the authorization request, and approve it if the access matches your intent. The supported connection uses OAuth; do not paste an API key into an ordinary ChatGPT conversation.
For Claude, add a custom connector in Claude and use the MCP server URL https://ezformz.net/mcp. Enable that connector in the conversation, then describe the form or operation. When prompted, sign in on ezformz.net and review the authorization request. OAuth sign-in is preferred because the connection can be reviewed and revoked under Account → Connected Apps. Use a static API key only when the client cannot use the OAuth connection, and enter it only in the client's designated credential control, not in an ordinary chat message.
The EZFormz OAuth access token lasts 30 days and its rotating refresh credential lasts up to one year. A supported client can refresh automatically. Revocation, expiry, or a long period without a usable refresh credential requires authorization again.
Understand what the connection can do
The current AI connection can request broad access to create, edit, publish, duplicate, and delete forms; manage products, prices, costs, stock, shipping, coupons, sales, themes, and images; view orders and analytics; and update order status, tracking, and seller notes. The underlying account and collaborator permissions still apply.
Data returned under those permissions can include:
- complete form configuration, including blocks, payment instructions or destinations, confirmation text, redirects, and Google Sheet URLs;
- product and variant details, including unit costs under the current form-view permission;
- buyer names, email addresses, shipping addresses, submitted answers, payment-evidence references, and order notes when order-view permission is available; and
- analytics and operational identifiers for accessible forms and orders.
Supported tools return only whether a form password exists, not the raw form password. They do not expose login codes, authenticator secrets, recovery codes, passkeys, sessions, or saved shipping and tax provider API keys. That boundary does not protect a secret that you manually put into a form, prompt, note, or chat.
Prompts, tool results, and conversation history are also processed under the AI provider's own privacy and retention terms. Avoid unnecessary buyer data. Never send login or recovery codes, API or provider keys, OAuth tokens, private crypto keys or seed phrases, full payment credentials, or one-time links in a prompt.
Build and review safely
- Ask the AI to inspect the relevant form before editing it.
- Describe the products, prices, payment method, shipping, and appearance you want, but omit secrets and unnecessary personal data.
- Keep a new form as a draft while reviewing blocks, prices, stock, payment destinations, confirmation text, and public appearance in the EZFormz builder.
- Explicitly confirm consequential actions such as publishing, deleting, replacing an entire option list, or changing order status and tracking.
- Reopen the form or order in EZFormz after a write. Treat the saved EZFormz state, not the AI's prose, as proof of the result.
Large catalog work may be split into small batches. The API supports compact description_missing=true product reads with pagination so a client can update a reviewed batch and then request the next one. If the assistant says a batch is complete, verify those products in EZFormz before asking it to continue; a conversational claim is not proof that the full catalog changed.
AI-created forms begin as drafts through the supported API. Publishing remains a separate write. Review access mode, products and stock, prices and unit costs, payment destinations, shipping, coupons or automatic sales, confirmation content, and public appearance before publishing.
Disconnect access
Open Account → Connected Apps and revoke the connection to stop its future OAuth access to EZFormz. If a static API key was used, revoke that key separately under AI Builder → API Keys. Then remove or disconnect EZFormz in the AI provider when appropriate.
Revocation does not erase prompts, chats, exports, or other data the provider already retained. Use the provider's own deletion and retention controls for those copies. For direct integration work, continue to Use the EZFormz API safely.
The AI connection is an automation surface, not a guarantee that generated text, product photos, unusual layouts, or inferred configuration will be correct. Fine-tune the result in the builder and report a reproducible EZFormz tool failure through support; questions about the provider's chat application belong with that provider.