Build

Build contact forms, newsletter sign-ups and full account flows in the Elementor editor — no shortcodes, no field codes to memorise.

NovaSpark does not process form submissions. It lays them out. The actual work — validation, spam checks, sending mail, creating accounts — is done by software built for it, so every plugin and integration you already rely on keeps working.

Two ways to build one #

Both produce the same markup, so you can move between them later without restyling.

The rest of this page covers the flexible route, since it is the one with settings to explain. The quick widget exposes the same choices in one panel.

NovaKit Form #

Drag NovaKit Form onto the page from the NovaKit Form category. It arrives with a Fields container already holding Name, Email, Message and a Submit button — delete, reorder or add to them. The settings are on the widget, under Content → Form.

The form wraps the Fields container from the outside, so everything you set on that container — direction, gap, alignment, width — still arranges the fields exactly as you laid them out. Select it by clicking the space around the fields, or through the Navigator.

The field widgets #

Ordinary Elementor widgets. Arrange them however the layout needs.

Newsletter forms use NovaKit Newsletter Field instead, and account forms use NovaKit Account Field — both explained below.

A prompt box

Form: Textarea has a Behaviour section for chat and AI prompts. Everything in it is off by default.

Fill it from buttons with quick prompts.

Field names

Each field has a Field Name — what it is called in the submission and in your email. Leave it empty and it is taken from the label, which is usually right.

Two rules are enforced for you. Names must be unique within a form, so a duplicate is renamed rather than silently overwriting the other field. And a few names belong to WordPress — name, author, s — so a field called name becomes your-name, exactly as Contact Form 7’s own default does, and for the same reason.

Contact forms #

1. Create the form in Contact Form 7Contact → Add New. Name it, save, and leave the form template alone — NovaSpark fills it in.
2. Set up the Mail tabRecipient, subject, reply-to. That stays yours; NovaSpark only writes the field list between two markers in the mail body.
3. Build the layoutA NovaKit Form with Powered By set to Contact Form 7, your form selected, and field widgets inside.
4. Save the pageThis writes your field list into the Contact Form 7 form, so it validates what you actually built.

Newsletter sign-ups #

1. Connect MailchimpMailchimp for WordPress → Settings, paste your API key, save. That is the whole setup.
2. Build the layoutA NovaKit Form with Powered By set to Mailchimp Newsletter, then pick an audience.
3. Add the fieldsNovaKit Newsletter Field widgets, then NovaKit Form: Submit.
4. SaveThe form record is created and your required fields written into it.

You pick an audience, not a form. Mailchimp for WordPress needs a form record to hang the audience on, so NovaSpark creates and maintains one behind the scenes. You never open its form editor. A form you did build there yourself still appears in the dropdown under its own name, and is never rewritten.

Merge tags

NovaKit Newsletter Field has no Field Name control, deliberately — the merge tag is the name. Its dropdown lists the tags your audience actually has, read from Mailchimp rather than typed from memory: EMAIL, FNAME, LNAME, PHONE and whatever else you have added.

Mailchimp collects an address as several values at once, so address-type merge fields are not in the dropdown. Collect them as separate text merge fields, or on a Mailchimp-hosted form.

Sign in, sign up and password reset #

These run on WordPress itself — no Contact Form 7 involved. Every authenticate and registration_errors filter still runs, so a security or two-factor plugin keeps working. What NovaSpark adds is that the visitor never leaves the page you designed.

Set Powered By to WordPress Accounts, then choose which flow this form is:

You never type field names. There is one set of fields, and the flow decides what each is called when it arrives. A field with no meaning in its flow — Remember me on a sign-up form — simply does not render, and says so in the editor.

The password field changes the behaviour

On a sign-up form the Password field is optional, and whether you include it decides what happens:

Add Confirm Password alongside and the two must match. Turning on Show/Hide Button on any password field cuts failed sign-ins on phones considerably.

Where the new password is chosen

The second half of a reset happens after the visitor leaves and comes back from their email. On the set a new one form, open Advanced → NovaKit Settings → Display Conditions → Edit Conditions and add an Include rule Account → Visitor followed a password reset link. Give the sign-in form the same rule as Exclude, and the page swaps cleanly.

That condition is a real check against WordPress, not a glance at the URL — an expired or forged link reports false and the form never appears.

The reset key never appears in the address bar. On arrival it is moved into a secure cookie and the URL is cleaned — a URL gets copied, shared, logged by the server and leaked through the referrer header, and that URL alone is enough to take over an account.

What signed-in visitors see

A sign-in form shown to someone already signed in is nonsense, so When Signed In defaults to hiding it. Give them something instead: a second container set to NovaKit Settings → Display → Visitor is signed in → Show, using the NovaKit User dynamic tags for their name, email and avatar.

Use Account URL → Sign out for the log-out link. A hand-typed logout URL is refused by WordPress, because it needs a security token only that tag can generate.

If the page has nothing else on it, use Page Settings → Signed-In Redirect instead and send them elsewhere entirely.

Custom Action #

Custom Action sends a form wherever you say, with no form plugin in between. Use it for a chat box, a CRM or an automation. It has no email or storage of its own: for those, use Contact Form 7.

With Stay on Page off, the browser leaves the page: to your URL, or back to this page with the result. With it on, nothing reloads, which is what a chat box needs. See Connect a chatbot for the code, and Hooks and filters for nk_form_custom_submit.

Putting forms in tabs #

Sign in and sign up on one page, as two tabs, is the common arrangement. Each tab’s panel in NovaKit Tabs is a container, so the forms go straight into it.

1. Add NovaKit Tabs to the pageOne item per form: sign in, sign up, and the reset request.
2. Build each form in its tabSelect a tab in the widget’s settings to show its panel, then drop the form into it.
3. Hide the reset tab from the navigationSet Show in Navigation to off on that item.

That last step is what keeps “Reset password” out of the tab row. Resetting is not a peer of signing in and signing up — it is where you go when you cannot get in — so the row shows two options and the third is reached from a link inside the sign-in panel. The panel is still fully present, just unlisted.

Linking between tabs

Two ways to point a “Forgot your password?” link, both fine:

A tab switcher is one arrangement, not a requirement. Separate pages work identically, and the Account URL tag still resolves between them.

Where the message appears #

Every engine’s message looks the same, and every form widget styles it in one place: Style → Message.

Set the colours when the form sits on a dark section: the defaults are tuned for light backgrounds. To put the message somewhere else entirely — beside the button, in another column — drop a NovaKit Form: Message widget there. It has the same style controls, and whatever you leave unset on it follows the form’s.

The wording stays the engine’s own, so a translation or rewrite in Contact Form 7 or Mailchimp is what visitors see. While a Contact Form 7, newsletter or Stay on Page form is sending, the submit button shows a small spinner in its own text colour.

Testing #

After a successful reset the visitor is not signed in automatically. That matches WordPress: possession of a mailbox is enough to change a password, and a deliberate sign-in is the moment the new one is confirmed to work.

Failed attempts hand back what was typed — except passwords, which are never stored anywhere that outlives the request.

What NovaSpark owns #