Connect ChatGPT or Claude
Open Selling on Dashboard, click Build with AI, and choose ChatGPT or Claude. You can also open Account, choose AI Builder in its sidebar, and choose the provider tab under the AI Form Builder heading. 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.
The public ChatGPT and Claude directory connections are awaiting publication. During this update, the provider choices show availability information instead of opening the retired GPT or asking you to configure a server. You can keep building and editing forms in EZFormz normally. Public first-time connection and native-device verification are still release requirements.
On the development website, authorized private testers can choose either provider to prepare EZFormz Dev in a new conversation. Add your form request and send it. Existing dev connections are reused. Private first-time setup is available only on dev and is separate from the public directory process. Enter passwords and security codes only on the EZFormz dev sign-in page.
After publication, the public connection will use the provider's listing and normal account approval screens. Each person installs or enables EZFormz when required, signs in to their own EZFormz account and approves its requested access. Customers should not need a server URL, OAuth-client configuration or an API key. Provider account and workspace policies can affect availability. Once connected, you can keep using EZFormz in that provider without returning to the website for every request.
Each provider keeps its own account connection. Signing into a different EZFormz account on this website does not switch the account connected inside ChatGPT or Claude. If a form appears missing, confirm which account is connected there before creating a duplicate or reconnecting.
Before approving a new connection, confirm your current password on the EZFormz authorization page. If 2FA is enabled, also enter an authenticator code or an unused recovery code. Add your first password if prompted, then return to review the connection. Never enter your EZFormz password or security codes in an AI chat. If confirmation fails or your account changes, choose Try again to reopen the approval page and review it again; approval is not repeated automatically.
New EZFormz OAuth access tokens last one hour. A supported client refreshes them automatically without another approval; the rotating refresh credential lasts up to 90 days since its last refresh. Revocation, expiry, or a detected reuse of an older refresh credential requires connecting again. An existing connection is not silently switched to another EZFormz account.
Read-only tools and tools that make changes are separate. ChatGPT and Claude apply their own confirmation preferences, and EZFormz checks your permissions on every request. The authorization page shows your account, requested access and the destination you return to after approval.
Understand what the connection can do
If a request is rejected as too large, ask the assistant to split the catalogue or other changes into smaller requests. Rejected oversized requests do not run the requested tools or save those changes.
An oversized result is different: a requested change may already be saved. Read the current saved state before retrying. The assistant can request smaller Builder sections or pages instead of trying to return the whole catalog.
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.
Those permissions also apply inside a full form_blocks replacement. Ordinary field content needs Fields access; Products checkout settings need Products; the Products block's shipping label, required-shipping switch, and per-option shipping behavior need Shipping; and payment methods, destinations, limits, crypto details, collect-later behavior, and method fees need Payment settings. Adding or removing a Products or Payment Instructions block also needs Fields plus that block's owning permission. If one request mixes allowed and blocked changes, EZFormz rejects the complete request instead of saving a reduced list.
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 under the current form-view permission; P&L unit costs are separate;
- owner-only variant seller notes through the targeted Builder tools when connected as the owner;
- 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 form block list, or changing order status and tracking. Ask the AI to read the current form again immediately before a full block-list replacement; EZFormz rejects an omitted, moved, or changed older unsupported block, or a newly authored unsupported block type, instead of silently filtering it.
- 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.
Both clients can read compact Builder sections and follow continuation pages for large catalogs. Product and variant lists are separate. A page is only part of the catalog until the continuation ends. If the form or stock changes while pages are being read, the assistant must start that section again.
Targeted Builder edits preserve untouched products, variants and settings. Each save checks the reviewed form version and commits its changes together. Existing local stock quantities and alerts also check their reviewed stock values. Owners can also manage shared inventory counts and variant connections through the AI connection. Collaborators with product-edit permission can change local stock; shared counts and changing a stock source remain owner-only. Stock operations save separately from form-content changes. Review shared-count deletions and source changes carefully. If another editor changed the form, review the latest state before trying again. A confirmed commit remains saved even if its follow-up read is unavailable.
P&L costs use their own tools and permissions. The assistant can edit product/variant defaults, shipping and fee defaults, order-specific costs and expenses or credits. Product editing permission alone does not grant P&L access. Cost amounts are saved in cents with the current row version; a missing cost and a known zero cost are distinct. Old product unit_cost fields are rejected. Read the saved P&L value before retrying a timed-out cost edit.
AI edits cover ordinary Builder settings, all block types, product/variant configuration, shipping, promotions, themes, receipts, confirmation content and access settings. You can save or use private templates, append products from supported CSV rows, and load a retained saved version or content backup. Applying a template replaces blocks and keeps the form’s current products. Restored variants that must be recreated start with zero local stock, so review inventory before selling. Confirm content replacement before the assistant saves it. Invitations, collaboration access, account security and provider credentials still use their own pages. Very large individual entries may require the Builder; the connection reports the limit instead of silently dropping content.
Supported raster images can be hosted from a real downloadable file reference or image URL and then attached through an authorized form edit. Whether a file uploaded in chat is available to the connector depends on the provider and client. If it is unavailable, use Builder’s image upload. Hosting an image does not attach or publish it, and hosted display images are not a private-document upload feature.
The assistant can find authorized retained P&L forms and provide CSV or Excel download links for a report. Those links use the normal signed-in EZFormz permission checks; they are not public access links.
AI-created forms begin as drafts through the supported API. Publishing remains a separate write. Use the editing link returned by the assistant to open a draft in the Builder. Buyer links are for published forms. Review access mode, products and stock, sale prices, payment destinations, shipping, coupons or automatic sales, confirmation content, and public appearance before publishing.
Reconnect or change accounts
Older public connection credentials may also require a fresh sign-in and approval after the integration update. If the assistant asks for a missing permission, reconnect EZFormz in your AI provider and review the new permission list. P&L requires its own access; form-editing permission does not include it. If the wrong account is connected, revoke that connection under Account → Connected Apps, sign in to the intended EZFormz account, then connect again. Never retry a timed-out write blindly: ask the assistant to check the saved value first.
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.