| 开发者 | alighasemirad |
|---|---|
| 更新时间 | 2026年11月6日 08:17 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0+ |
| 版权网址: | 版权信息 |
Yes. The drag-and-drop builder and every non-AI feature — multi-step forms, conditional logic, surveys, calculations, the Products field, Stripe payments, Google Sheets, Entry Tags, form analytics, spam protection, popups, user registration, submission management, webhooks, Slack notifications, import/export, and full visual customization — are 100% free. There is no premium version and there are no paid add-ons. The only thing you can pay for is AIDA credits for the optional AI features, and only after the free trial credits are used up.
No. The drag-and-drop builder needs zero coding. Building, styling, and embedding are all handled through the visual interface.
Text, Textarea, Email, Phone, Number, Date, Time, Month & Year, Checkbox, Radio, Dropdown, Name, Address, File Upload, Signature, Color Picker, Calculation, Products, an HTML content block, Page Break (multi-step), and four survey fields: Tabular Survey (Likert grid), Star Rating, NPS, and Opinion Scale. See the full field reference.
Yes. Every field supports show/hide logic with AND/OR conditions, and logic can also change your confirmation message, redirect, or which email is sent.
Yes. Enable multi-step mode and add Page Break fields where each step starts. You get step titles, custom button labels, progress bar styles, and answer-based branching that skips or jumps steps so visitors only see what applies.
Yes. Every form has a ready-made embed code that works on any site, including non-WordPress platforms and page builders like WP Bakery, Brizy, and Elementor. The embed keeps your design, resizes automatically, and stays isolated from the host theme. You can also share a direct link to the form as its own page.
Yes. When AI Conversation is on for a form, its settings have an Embed section with the code and a Copy button, and the AI Conversational Forms list has a "Copy embed code" button too. Paste the code into any website, WordPress or not. It works for logged-out and logged-in visitors and uses AIDA credits the same way as on your own pages. On a form with a Products field, the chat hands over to the regular form at the end, with the answers filled in, so the visitor can choose products there.
Yes. Each conversational form has an Appearance tab with a live preview that uses no AI credits. Start from a preset (Light, Dark, Transparent or "Match my form", which takes your form's colors and font), then change the colors, font (your theme's, the system font or a Google font), text size, corners, header, avatar and input. Show the chat in the page or as a floating button in a corner, with an optional teaser message. Administrators can also add custom CSS for one chat.
Yes, with the free Stripe Payments add-on (off by default; enable it under Forms → Add-Ons). Connect your own Stripe account and visitors pay on Stripe Checkout after submitting. The amount can be a fixed price, an amount the visitor enters, a Calculation result, or a Products order. Payment status and refunds are tracked on the Submissions screen, and card details are entered on Stripe's page, never on your site. The plugin adds no transaction fee or percentage — you pay only Stripe's standard processing fees.
Yes. The Products field and the Stripe Payments add-on are both free. List what you sell with prices, turn on Stripe Payments, and visitors choose products and quantities, see the total, and pay on Stripe Checkout, with each product on its own line. Prices always come from your form, never from the visitor's browser. The plugin adds no fee; you pay only Stripe's standard fees. Prices are one-time; recurring billing is not available yet.
Yes. Add a Calculation field and write a formula that uses other fields, for example a price times a quantity plus a fee. The total updates as the visitor fills in the form and is calculated again on your server when the form is submitted, so visitors cannot change it. A Calculation field can also set the amount of a Stripe payment.
Yes, with the free Google Sheets add-on (off by default; enable it under Forms → Add-Ons). Connect a Google service account, choose a spreadsheet and worksheet for each form, and map fields to columns. New submissions are added in the background and retried automatically if Google is slow or unavailable.
Yes, free and built in — no separate popup plugin. Display any form as a modal, slide-in, sticky bar, full-screen, welcome mat, or floating launcher, and control which pages it appears on, how it triggers, how often it shows, and what happens after submit.
Yes. Add the Signature field and visitors can sign with a mouse, finger, or stylus. The signature is stored securely and shown as an image in the entry details, on WordPress pages and embedded forms.
Yes, free and built in. Pick which form creates accounts and map its fields to the account email, username, password, and name. Choose the new role, customize the welcome email, and add an independent login form (with lost password and reset) to any page via the [auto_form_builder_login] shortcode — no default WordPress login screen.
Yes. Google reCAPTCHA and Cloudflare Turnstile are both included free — use either or both on any form.
Yes. Auto Form Builder integrates natively with Auto Form CRM, a premium WordPress CRM with contact management, a deal pipeline, automation, email campaigns, meeting scheduling, and live chat. Capture with Auto Form Builder, then nurture and close in Auto Form CRM. Learn more at autoformcrm.com.
The core builder is free and always will be, with no account required. The optional AI features run on our AIDA service: a free AIDA account comes with free trial credits, and after those are used, continued AI usage needs one-time credit packs bought on autoformcrm.com. So AI is a paid service after the free trial, while everything else stays free. Your credit balance is always visible in the plugin.
Only when you actually use an AI feature, and only the content it needs: the form description or uploaded document when building a form; the submission content when you summarize, reply, or "ask across submissions," or when the admin assistant answers a question; the messages you type into the admin assistant; and — only if you enable AI Conversation on a public form — the chat messages visitors type. Requests are authenticated with your AIDA token (kept encrypted on your server) and processed by our AI provider, Anthropic. Nothing is sent unless you opt in and use the feature. See "External Services" for full details.
Yes. Auto Form Builder is fully functional without any AI. The AI modules are switched on by default, but the plugin never contacts AIDA until you connect an AIDA account. If you never connect one, nothing is sent, and you can switch the AI modules off under Forms → Add-Ons. Every other feature works the same either way.
Yes. Edit the webhook under Settings → Webhooks, choose "Custom JSON template" and write the JSON, or start from the Meta Conversions API Lead example. Put tags inside quotes, for example "{email}". Field tags are the same as in emails; system tags include {event_id}, {event_time}, {page_url}, {page_url_clean}, {referrer}, {visitor_ip}, {user_agent}, {form_id}, {form_name} and {submission_id}, and the Ad Tracking add-on adds tags such as {gclid}, {utm_source}, {fbp} and {fbc}. Modifiers run left to right: |trim, |lower and |nospace tidy a value, |e164 writes a phone number with its country code, |sha256 hashes it (it must come last, and an empty value stays empty) and |number sends a number instead of text (only when the tag is the whole value). For example {phone|e164|sha256} or "{event_time|number}". "Validate & preview" shows the result with sample values before you save. To keep an answer out of every webhook, turn on "Never send to webhooks" in that field's settings in the form builder.
Yes. Choose a "File links" option in the notification's settings. A login link opens the file only for a logged-in user allowed to view submissions. A secure link works without logging in, for one file only, until it expires (7 days by default, at most 30). Each link is signed with your site's secret keys and holds no file name or server path, so it cannot be guessed or changed to open another file. Files are sent by the plugin with download-safe headers; only images open in the browser. A link stops working when it expires or when the entry or file is deleted, and secure links are rate-limited per visitor. Anyone who has a secure link can open that file until it expires, so use login links for sensitive files.
Yes. On the Submissions screen, click the eye icon on a row, or press Shift+V, to open the entry's answers in Quick view over the list. Previous and Next (or J and K) move through the list in its order, and opening an unread entry marks it read.
Use the same event ID in both. When the success message shows, the page fires an afb:lead event with the submission's event ID, and pushes afb_lead to the dataLayer for Google Tag Manager. For the Meta pixel: document.addEventListener( 'afb:lead', function ( e ) { fbq( 'track', 'Lead', {}, { eventID: e.detail.event_id } ); } ). In the webhook template, send "{event_id}". If the form redirects straight to another page, add the ID to the redirect address, for example https://example.com/thanks?eid={event_id}, and fire the pixel there.
Only while the Ad Tracking add-on is switched on, and only when a visitor arrives with an ad click ID (fbclid, gclid, gbraid, wbraid, msclkid) or UTM parameters, the site sets one first-party cookie, afb_attr, for 90 days (you can change this). It holds those values for the first visit, the last visit and the last ad click, with the landing page address (without its query string) and the referring site's name. It is set by your own site (HttpOnly, SameSite=Lax, and Secure on HTTPS), never sent to other sites, and is used to fill webhook tags and hidden fields such as {gclid} or {fbc}. The add-on reads the Meta _fbp and _fbc cookies but never writes them, and does not touch any other cookie. Suggested privacy policy text is added under Settings → Privacy. If your site is behind Cloudflare or a proxy, set "Visitor IP source" under Settings → Webhooks, so the add-on's limit on requests per visitor counts each visitor separately.
Visit autoformbuilder.com/support for documentation and support.