Put the form on your own website
When the link is enough, when it is not, and what to hand a developer.
For admins.
Read this first
Most people who arrive here do not need any of it.
If what you want is for someone on your website to fill in a form and have the answers land in Klienta, the link from Build a form and collect answers already does that. Put a button on your site that opens it. Nothing to build, nothing to maintain, and it keeps working when you change the form.
You need this guide only when the form has to look like your site — your fonts, your page, no jump to another address. That costs a developer, and it is worth being sure before you ask for one.
The three ways, in order of effort
Rendering flowchart...
Send the link. Covered in the other guide. No code.
Let your form tool send it. If the form on your site was built with something that can call a webhook when someone submits, point that webhook at us. You fill in a few fields in that tool rather than writing anything.
Have your server send it. Your own page, your own design. Your server receives the submission as it does today, then passes it on to us. This is the one that needs a developer.
The last two are the same thing underneath — a request signed with a key. Only who makes it differs.
Keys
A key is what lets something outside Klienta send us answers. Open the form and go to Keys.
Make a separate key for each website or server, so you can turn one off without stopping the others.
Press New key and give it a name that says which website or server will use it, so a key can be turned off later without guessing what it was for.
A test key lets you try the whole path without a single false lead.
Two things about keys are worth saying plainly, because getting them wrong is expensive:
- You see a key once. Klienta keeps only a scrambled copy and cannot show it to you again. Give it to the developer when you make it; if it is lost, make another and turn the old one off.
- A key never goes in the page. It belongs on a server, where visitors cannot read it. Anyone who gets it can post answers into your CRM as if they were real people.
Test keys let you try the whole path without creating leads. Live keys turn answers into real records, and can only be made once the form is published.
What to hand the developer
Open Your own server. It contains a ready-made request with your form's own questions in it — send the developer the page, or copy the block. Give them the key separately and securely; Klienta shows it only when you create it.
They need three things from it: the address to post to, the key, and the header that stops a double submission from becoming two leads if the network hiccups. That Idempotency-Key must stay the same every time one submission is retried; make a new unique value only for the next, genuinely different submission.
The one thing that will catch you out
The example carries a version number. Klienta keeps accepting older versions on purpose, so that publishing a change never breaks somebody's website in the middle of the day.
The cost is that publishing does not carry your website forward. Add a question, publish, and the answers from your own form keep arriving exactly as before — without the new answer. Nothing fails. The column simply stays empty.
After you publish a change, open Your own server and compare the schemaVersion in its example with the one in your website's integration. If they differ, the fix is one number, on your server, by whoever wrote it.
The example always shows the current published version. Keep the number in your server in step with it.
What comes back
Nothing changes at the reading end. Answers sent this way land in Responses beside the ones from the hosted page, and become the same leads in Lead Intake. The channel filter tells the two apart when you want to know which is which.
If a key is ever exposed, open Keys, turn it off, and make another. The form keeps collecting from the hosted link the whole time.