Custom HTML element

Custom HTML inside the form. With fields that actually capture something.

Free HTML blocks exist at several vendors, usually as a surface for text, images and third-party embeds. Here the block is part of the form. An input inside it becomes an ordinary question with an answer in the lead, it can be made required, it survives the step change. And if your form came from a PDF, attach a hand-built field to the matching field in the document: on download the value is back where it belongs.

In the form builder, in every plan.

How It Works

From what you write to what gets captured

  1. 01

    Insert a section and start writing

    The free section sits in the form builder palette. One button drops in a starting frame with a style block of its own. The preview beside it shows exactly what gets delivered later: whatever disappears there disappears for the visitor too.

  2. 02

    Making sure a field arrives

    An input is captured as soon as you give it a question text. That text is what the answer appears under in the lead. Several fields sharing a name belong together, and that is exactly what a single choice or a multiple choice needs.

  3. 03

    And when it has to go back into the PDF

    If your form came from an imported PDF, attach the field to the identifier of the PDF field; the builder copies it for you with one click. On download the value then sits in the right place in the original document, even if you arranged the field completely differently.

  4. 04

    What actually arrives is listed below

    Under the code input the builder lists every detected field with its question text, kind, required flag and PDF mapping. A forgotten marker shows up there, instead of taking revenge later as a field that vanished without trace.

In Betrieb

Custom HTML

Where the builder ends, you keep writing.

A section of the form you write yourself in HTML and CSS. Pricing table, comparison grid, callout box, an input layout that has to look exactly like that and no other way. The fields you build into it are real: their answers land in the lead like every other one.

  • Rebuild an imported PDF form freely without losing the mapping
  • The next button sits wherever you put it
  • No JavaScript, and no fonts fetched from Google
custom html — written, rendered, captured
EIGENES HTML<style> .zeile { display:grid }</style><label>Vorname</label><input data-xm-id="Vorname_1" data-xm-required><input data-xm-qst="Wunsch- termin" type="date"><button data-xm-next> Weiter</button>SO SIEHT ES DER BESUCHERVORNAMENACHNAMEWUNSCHTERMINGut zu wissenWir melden uns binnen 24 Stunden.WeiterERKANNTE FELDERvornamePflicht→ Vorname_1 (PDF)wunschterminDatum→ Frage im LeadKEIN JAVASCRIPTKEIN FREMD-REQUEST

PDF Import

The file becomes a form. And becomes the file again.

asksteps reads the form fields from your PDF, builds the online form from it page by page, and writes the answers back into that exact document at the end. What you download is your original file — not a recreation that someone would have to approve all over again.

  • Text fields, checkboxes, dropdown lists, and signature fields are detected
  • One form step per PDF page
  • Read-only fields are left untouched
pdf import — detect fields, build the form
ANTRAG.PDFUnterschriftLESENSeite 1 von 3NACHNAMEGEBURTSDATUMFACHRICHTUNGUNTERSCHRIFTAusgefüllt kommt Ihr Originaldokument zurück — nicht ein Nachbau.
Features

What is possible in such a section

Your own buttons instead of the default bar

Next, back and submit can go on any element, a whole card included. Hide the default bar for that step so two next buttons do not end up stacked.

The usual field kinds

Text, email, phone, number, date, time, select, multi-select, text area. Plus hidden fields, which in practice means campaign and landing page travel along invisibly in the lead.

Error marking to your taste

Empty required fields get marked on the next click and the first one is focused. What such a marking looks like is up to your CSS.

Your theme colors are there

The section knows the colors of the selected theme. Use them and it stays coherent when the theme changes, instead of standing out in the wrong shade.

Readable in WordPress too

Alongside the widget, the WordPress plugin builds a summary of the first step that search engines can read. Questions from your own HTML are in there.

Checked before anyone sees it

Markup and CSS pass the same check in the builder and at the visitor, and render encapsulated. Your CSS cannot disturb the page around it, and nobody can run foreign code through a form configuration.

Frequently Asked Questions

Questions about custom HTML

Can I add JavaScript?

No. Script elements, event attributes and script URLs are removed. The reason is where it runs: your form is embedded on other people's pages, and executable third-party HTML would be a permanently stored security hole there, facing every visitor and not just you.

Can I embed third-party content, a calendar or a video?

Embedded frames are not allowed, because they trigger a third-party request before anyone has consented. For videos there is a form element of its own that loads only on click.

Can I drive branching from my own HTML?

No. Fields in the free section capture values, they do not steer jumps. Branching hangs on answers with an outgoing port and therefore belongs to regular elements.

Does this work in funnels too, not only in forms?

The free section exists in the form builder. In a funnel every tile carries an answer and with it a port for branching; a freely designed surface would have none. For whole screens in a funnel there is the intro screen instead.

Can the texts in my HTML be translated?

No. What gets translated are the texts of regular elements. A form meant to appear in several languages is better off building those sections from form elements. Or getting a version of its own per language.

What happens if I make a mistake?

Markup that is not allowed is removed rather than breaking the page: the wrapper disappears, the text remains. Because the preview runs the same check, you see the result immediately, and the list of detected fields shows which fields actually arrive.

Can I add new fields to my PDF through HTML?

No, only fields that already exist in the document. The mapping is created during import by reading what is in the PDF; asksteps cannot add a form field to a document afterwards. A hand-built field with no counterpart in the document therefore shows up in the lead but not in the downloaded PDF. If you need an extra field in the document, add it in a PDF program and upload the file again.

More on This Topic

Related pages

Write your first section

Included in the free account. The starting frame in the builder gets you past the blank page.

Create an account now