Forms, email and workflows in the Backend tab

Build a booking or contact form, read every submission in the forms inbox, send branded emails, and automate what happens next with workflows, all without code.

Content and data8 min read

A form is often the most important part of a small business site: it is how bookings, quotes and questions reach you. In Buildan.app every form works the moment you publish. Submissions land in an inbox, you get an email, spam is filtered out, and with the Backend tab you can add automatic replies and workflows that send emails, save records and more.

In this tutorial you edit the booking form of a hair salon site, publish it, read real submissions, switch on an autoresponder, and build a workflow that adds every new booking request to a list.

What you need

  • A site with a form. Most templates include one on their contact page, and you can add one from Insert in the editor.
  • Any plan. The Free plan accepts 100 form submissions a month, Pro 2,000 and Business 25,000.
  • In the Backend tab, the Free plan includes 3 workflows per site and 100 workflow runs a month. Pro raises that to 50 workflows and 10,000 runs, and adds server functions and sending email from your own domain. Business goes further (see Pricing).

Set up the form

Step 1: Select the form in the editor

Open your site in the editor and go to the page with the form. Click the form, then press Esc until the inspector on the right shows the form itself (its type reads form).

The Form group at the top sets the form's Name (it is how the form is listed in your inbox), the Button text and the Thank you message visitors see after sending. Below it, Fields lists every field in order. Drag a field by its handle to move it, and use Add field at the bottom for a new one.

1: the form on the page. 2: its fields, in order.

Step 2: Change a field

Click a field in the list to open it. You can change its Label, its Type and its Placeholder, make it Required, and set its Width to Full or Half so two short fields share a row.

Field types include text, email, phone (tel), number, long text (textarea), a menu (select), radio buttons, checkboxes, date, file upload, consent, web address and hidden. Menus, radio buttons and checkboxes take their Options one per line. File fields let you limit which files are accepted and how large they can be.

Show if shows a field only when another field has a certain value, is filled or is empty. Long forms can be split into Steps, and each field is then assigned to a step.

1: the field type. 2: the rest of the field's settings.

Step 3: Choose who is notified, and check spam protection

Scroll to After submit. In Notify, type the email addresses that should receive each submission, separated by commas. Leave it empty and notifications go to the site owner's account email, once that address is verified. Redirect to can send visitors to a page of your site, such as a thank you page, instead of showing the message in place.

Open Spam protection to see how forms are protected: every form has a hidden honeypot field, a minimum fill time and rate limits. Anything caught is kept apart in the Spam folder of your inbox, so you can still check it.

1: who gets an email for each submission. 2: built in spam protection.

Publish and receive submissions

Step 4: Publish and send a test

Choose Publish in the editor, then open the page on your live site and fill in the form yourself, the way a visitor would. Required fields are checked before the form is sent.

1: the published form, filled in by a visitor.

After sending, the visitor sees your thank you message. The form works the same on a phone.

1: the thank you message replaces the form.

Step 5: Read submissions in the Forms inbox

Back on your site's dashboard, open the Forms tab. All forms shows every submission, newest first, and each form has its own folder with a count of unread messages. Click a submission to read every field, with the date and the page it was sent from.

  • Reply opens an email to the visitor, when the form has an email field.
  • Spam moves a message to the spam folder, and Not spam brings it back.
  • Export CSV downloads the submissions as a spreadsheet.
1: a submission in the inbox. 2: every field it sent. 3: download them all as CSV.

Send emails automatically

Step 6: Switch on Email events

Open the Backend tab and choose Email, then Email events. These are ready made emails grouped by Forms, Store, Members, Content and Reports. Each one you switch on becomes a workflow you can open and change.

Switch on Autoresponder to the visitor to thank everyone who sends a form and send them a copy of what they wrote. It is sent to the address in the form's email field.

1: the autoresponder, switched on.

Step 7: Make the email yours with Template

Choose Template next to an event to open its email in the template editor. On the left you edit the Subject, the Preview text shown in inboxes, and the email's Blocks: headings, text, the submitted form fields, buttons and more. Brand, Background, Font and a logo address set the look.

The middle column previews the email with sample data, on a computer or a phone, and Plain text shows the text only version. Send me a test sends it to you. Choose Save when you are happy.

1: the subject, filled in with your site's name.

Automate with workflows

Step 8: Describe a workflow, or start from a trigger

Choose Workflows in the Backend tab. The quickest start is Describe an automation: write what should happen in a sentence, for example "When someone submits the booking request form, email me and add them to the Leads collection", and choose Propose a workflow. Proposals use a small amount of AI credits.

You see the proposal as numbered steps. Nothing is created until you choose Approve and turn on, or Discard it. To build one yourself, choose New workflow and pick what starts it: a form submitted, a store order, a CMS item, a site member, a schedule, an incoming webhook, a button click, a changed database record, an abandoned cart or a subscriber.

1: describe what should happen. 2: review the proposal before anything is created.

Step 9: Check the steps on the canvas

The workflow opens on its canvas. The first card is the trigger, here Booking request form submitted, and each card below it is a step. Click a card to change its settings on the right, and use the + buttons to add a step: send an email, notify yourself, post to Slack or Discord, add a subscriber, create or update a CMS item or a database row, call an address, set variables, branch with a condition, wait, loop, or run AI text.

Values from the form are written like {{ trigger.data.email }}, and suggestions appear as you type. Test run tries the workflow without waiting for a real visitor. The switch at the top turns the workflow on or off, and Save keeps your changes.

1: the trigger. 2: the first step. 3: add another step here.

Step 10: Follow each run in Run history

When the next visitor sends the form, the workflow runs. Run history lists every run with its status. Click one to see each step with what went in and what came out, which makes problems easy to spot. Secrets are hidden, and runs are kept for 30 days.

1: the run. 2: each step's input and output.

Let visitors sign in

Step 11: Turn on site members

Members in the Backend tab lets visitors create accounts on your site. Switch on Member accounts, then choose whether Anyone can sign up and whether members can Sign in with an email link (no password). You get the addresses of the log in, sign up and member area pages to link from your menu or buttons.

Under Members only pages, list the paths only signed in visitors may open, for example /members/* for every page under /members. You can also add Profile fields to store a little extra about each member. The Welcome email event under Email events greets new members.

1: member accounts on. 2: pages only members can open.

Tips and pitfalls

  • Verify your account email. Form notifications go to the addresses in Notify, or to your verified account email when that box is empty.
  • Keep forms short. Ask only for what you need, mark only the essentials Required, and use Show if for questions that apply to some people only.
  • Add a consent field when you will contact people later. The inbox shows whether the visitor gave consent on the form.
  • Name your forms clearly. The form name appears in the inbox, in notifications and in workflow triggers.
  • Test workflows before you rely on them. Use Test run, then send the real form once and check Run history.
  • Watch your allowances. The Workflows page shows runs this month and workflows on the site against your plan.

Summary

Forms work as soon as you publish. Set the fields, the thank you message and who is notified in the editor, and read, reply to and export submissions in the Forms tab. In the Backend tab, Email events add ready made emails such as an autoresponder, the template editor makes them yours, and Workflows automate the rest: describe one in a sentence or build it step by step, then follow every run in Run history. Members lets visitors sign in and keeps pages for them only.

Next, store content in CMS collections or connect a database, so a workflow can save leads where you already keep them.

Try it now.

Follow this tutorial in your own account. Buildan.app is free to start, and you can upgrade when you need more.