↑↓ selectEnter openEsc close

    1. Elbuz

    How to build a form and receive requests

    9 min readUpdated

    An organizer form collects answers from outside people: requests, surveys, questionnaires, briefs. Each answer lands in the “Answers” list, and the sender becomes a contact card.

    When you need this:

    • A site request form without a developer — “Create widget” gives code to paste into a page.
    • A questionnaire sent as a link — “Preview” builds the form page; its address is the link.
    • Requests are copied into Contacts by hand — with name and email fields, the contact is created automatically, without duplicates.
    • Your CRM handles requests — the form sends answers to your server.

    Where to start: Organizer → “Forms” → build the fields in the builder.

    What a form can do

    How to build a form and share it

    The most practical of the five types: a form collects answers from outside people — a request, a survey, a contractor questionnaire, an order brief. You build the fields in the builder: drag the field type you need into the form and label it.

    Step by step

    1. Build the form fields in the “Forms” window.
    2. Click “Preview” — the system builds a ready page with the form and opens it. That page's address is the public link: share it with participants, nothing else to set up.
    3. Or put the form on your site: “Copy” puts the HTML code of the form itself on the clipboard, “Create widget” puts embed code there. Then open the editor of the right page on your site and paste the snippet.
    4. To see answers, click “Answers”: the list is at the top, and below it is the filled-in form for the row you selected.

    The form link changes every time you click “Preview”. Each click rebuilds the page, deletes the previous file, and saves a new one at a new address. The old address you sent out stops opening.

    So share the link once the form is finished, and if you had to fix something, send out the new link. The code from “Create widget” shows that same page on your site, and the button also rebuilds it — so after a new “Preview” or a new widget, paste the code on your site again.

    How to name fields so requests become contacts

    When someone submits the form, the system does more than add the answer to the list. It also creates a contact in Contacts and sends an email to the employee who owns the form record — with a table of all answers and the respondent's address as the reply-to, so you can reply straight from your mailbox.

    But the system only recognizes fields with specific names. You set the names in the builder, and they must be exactly these:

    Field nameWhat happens to it
    emailgoes to the “Email” column of the answers list, becomes the contact's email and the reply-to address in the email; it is also used to check whether the contact already exists. Without a filled-in email, no contact is created
    namethe contact's name and the “Name” column of the answers list; without it, the card is created with an empty name
    firstname and lastnamean alternative to the previous one: the system builds the name from the two fields
    descriptionstored as a separate answer field, but the answers list has no column for it — the text is visible in the filled-in form below the list
    any otherthe answer is saved and visible in the filled-in form below the list, but it doesn't get a column in the list and doesn't go to Contacts
    Where an answer goes and when a contact appears. The top branch is the most common surprise: your own server doesn't add a second receiver, it replaces ours
    YesNo — the defaultNoYesYesNoSomeone filled inand submitted the formIs “Link to yourserver” filled in?The answer goes only there:“Answers” stays empty, no contactis created, no email is sentThe answer appearsin the “Answers” windowIs the email fieldfilled in?No contact is createdIs the email addressalready in Contacts?No new card is createdA new contact is createdEmail with the answers table —to the form record owner
    • Action or result
    • Decision: the path depends on the answer

    Hence a simple recommendation: in every form that collects requests, add fields named name and email. Then every request becomes a customer card on its own, repeat requests from the same address don't create duplicates, and the answers list is readable at a glance, not row by row.

    What to do with contacts the form created

    They have no service group or “from form” mark. The card goes to the first group in Contacts — in the standard set that's suppliers, not customers; its source field gets the code jumper, like any contact created via the . So you can move it, merge it with a duplicate, and delete it like any other card.

    The answers list won't break: each answer keeps its own copy of the name, email, and description, not a link to the card. Merging or deleting a contact doesn't change rows in the “Answers” window, and vice versa — deleting an answer doesn't delete the contact.

    Only the duplicate check changes, because it looks for the email among existing cards:

    • if the contact is in the Trash, a new answer from the same address finds it there: no new card is created, and the card isn't restored from the Trash;
    • if the contact was deleted permanently, or after a merge no card has this address, the next answer from it creates a new contact.

    How to receive answers on your own server

    The form settings have a “Link to your server to retrieve data from the form” field. If it's empty, answers come to Elbuz with everything described above.

    A filled-in field replaces the receiver, it doesn't add a second one. The form will send answers only to your address: the “Answers” window stays empty, no contact is created, no email is sent. That's the right choice when your handles the form, and a mistake when you just wanted to “send a copy to myself too”.

    The same place sets custom and JavaScript for the form page — so it looks like your site, not the standard one.

    Scenarios

    Requests from your site should become contact cards

    What to do. In the “Forms” window, add fields named name and email, and make the email required. Leave the “Link to your server to retrieve data from the form” field empty. Click “Create widget” and paste the code from the clipboard into the editor of the right page on your site.

    What you get. Each submitted form appears in “Answers” with the “Name” and “Email” columns filled in. If the address isn't in Contacts yet, a contact with this name and email is created. The form record owner gets an email with the answers table, and the reply-to address is the email of the person who filled in the form.

    What won't happen. A repeat request from the same address doesn't create a second card: the answer is saved, the contact stays single. The card goes to the first group in Contacts, not the customer group — you'll have to move it by hand. After every new “Preview” or “Create widget”, paste the code on your site again.

    Your CRM handles requests, not Elbuz

    What to do. In the form settings, enter your handler's address in the “Link to your server to retrieve data from the form” field. Then click “Preview” or “Create widget”: the address gets into the form page when the system builds it, not when you fill in the field.

    What you get. The form sends all fields as a POST request to your address, together with the service fields item_id and item_type — your system uses them to tell one form from another.

    What won't happen. The “Answers” window is empty, no contact is created in Contacts, no email goes to the form owner: all of that is done by the Elbuz receiver, which the answer no longer reaches.

    What to do when requests don't arrive

    What you seeWhyWhat to do
    The form link you sent out no longer opensyou clicked “Preview” again, and the page was rebuilt at a new addresssend out the new link; next time, share it after the last edit
    Form answers don't appear in the “Answers” windowthe server address field is filled in — answers go only thereclear the field if you need the answers in the system
    The “Email” and “Name” columns in the answers list are emptythe form fields have different namesrename the fields to email and name
    No contacts are created from the formthe form has no email field, or the respondent left it empty; if the address is already in Contacts, no new card should appear anywayadd an email field and make it required
    The new answer email goes to the wrong employeethe email goes to the form record ownercheck who owns the record and the email address in their card

    FAQ

    How do I share a form without embedding it on my site?

    Click “Preview” — the system builds a page with the form, and you can send its address to participants. Each later click on “Preview” creates a new address, and the old one stops working.

    Can I send form answers to my own system?

    Yes, you enter your server's address in the form settings. But this replaces delivery rather than duplicating it: answers stop coming to the organizer, no contact is created, and no email is sent (your own receiver).

    Why aren't contacts created from the form?

    A contact is created only when the form has an email field and the respondent filled it in; the same address won't create a second card. The name comes from the name field or the firstname and lastname pair (field names).

    Which group do contacts from the form appear in?

    In the first group in Contacts — in the standard set that's suppliers, not customers. There's no separate “from form” mark: you move, merge, and delete the card like any other (contacts from the form).

    Can I style the form to match my site?

    Yes. The form settings let you set custom CSS and JavaScript for its page — then the form looks like your site, not the standard one (form settings).

    Where it is and who has access

    Menu
    Organizer → Forms
    Access right
    the “Forms” window in “Group permissions”
    Prepare
    an email address in your employee card — the request notification is sent there

    A form is an organizer record, so it has the same participants, status, reminders, comments, and change history as a note or a document. What all record types share is covered in the general article.

    Related topics

    • If you need the big picture on notes, spreadsheets, documents, presentations, and forms — organizer documents.
    • If the person who sent a request became a contact and you need to work with them — contact card.
    • If you need a presentation with a site widget instead of a form — how to make a presentation.

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free