---
title: "Forms: collect enquiries from your site | Briks"
url: https://briks.dev/docs/forms
description: "Add a form to your Briks site, test it in preview, find every entry in the studio, get each one by email in production and pass them on with a webhook."
last_updated: 2026-10-08
---

# Forms: collect enquiries from your site

Forms on a Briks site send each message to the studio, where it's kept for you, and once the site is in production each one is emailed to you as well. This page covers adding a form, testing it safely, finding entries, and passing them to other tools.

6 minute read Checked against the studio on 8 October 2026

## How a form works

1. A visitor fills in the form. Required fields, email addresses and phone numbers are checked on the page before anything is sent.
2. The message goes to Briks, which keeps it in your project's **Forms** list and rings the bell in the studio with its subject and page.
3. In production, Briks also emails it to you. On a preview it's kept but not emailed.
4. The visitor sees “Sending your message…”, then a thank you (by default “Thank you. Your message has been received.”). If sending fails, they see a plain error and their words stay in the form.
5. Each form sent counts as an enquiry in [Analytics](https://briks.dev/docs/analytics).

Forms that save records

Some features save each entry as a record instead, such as a booking form for a class with limited places. Those entries live in the [Database](https://briks.dev/docs/database) tab, not in the Forms list this page describes.

## Add a form

A form is part of a page, so you add one the way you change anything else: by asking in the Studio. Name the fields, say which are required, and give it a subject so you can tell your forms apart in the list and in your inbox.

1. Open the Studio

   Where: Studio

   Open your project. The prompt box sits under the conversation.

2. Describe the form

   Where: Prompt box

   Say which page it goes on, its fields, which are required, the button's words, the subject, and what visitors read once it's sent.

3. Send

   Where: Send

   A change holds 5 credits and is charged for the work it takes. What it doesn't use comes back.

4. Look at the result

   Where: Your site

   When it's published, open the page and check the form at phone width too.

A change request A wedding photographer in Cornwall

> On the Contact page, add an enquiry form with name, email, phone, wedding date, venue and a message. Make name, email and date required. Button: Check my date. Subject: Wedding enquiry. After sending, say: Thanks, I'll reply within two working days.

Entries arrive under **Forms** with the subject Wedding enquiry, and in production each email's subject reads “Wedding enquiry from Tamsin Hale Photography's website”.

## Test it in preview

Before you publish to production, send a few tests from the preview address. Each entry is kept with a **preview** label and nothing is emailed, so you can try a form as often as you like.

1. Open the preview

   Where: Top bar

   On a wide screen, click your site's address beside the project name. It opens in a new tab. On a smaller screen, use **Open in new tab** above the preview.

2. Try to break it

   Where: Your site

   Leave a required field empty and send: the form should point you to it. Type a broken email address: it should say it doesn't look right.

3. Send a real one

   Where: Your site

   Fill everything in properly and send. You should see the thank you.

4. Find it in the studio

   Where: Settings, Forms

   Open or refresh the Forms page. Your test sits at the top, marked **preview**.

Tip

Put Test 1, Test 2 and so on in the name field so you can tell tests apart later. Entries can't be deleted, but only the newest 100 are shown, so old tests drop out of view as real entries arrive.

## Where entries appear

Where

1. Projects
2. Your project
3. Settings
4. Forms

The Forms page lists the newest 100 messages, newest first. Each shows when it arrived, the form's subject, the page it came from, and one of four marks: **emailed**, **not emailed** (the email failed), **preview**, or **held, not emailed** for likely spam. Below that, every field and its answer. Everyone in the workspace can read the list, Viewers included.

A message that reads as spam is kept, tagged **Likely spam** and never emailed, and no webhook or notice goes out for it. If it is real, an Owner, Admin or Editor presses **Not spam** to take the tag off. It is not emailed afterwards, so answer it from the list.

There is no export

Entries can't be downloaded, and only the newest 100 are shown. If you need a lasting record, keep the emails, or send each entry to another tool with a webhook as it arrives (see below).

## Where the emails go

In production, each entry is emailed to the person who created the project. If they've left the workspace, it goes to the workspace's first Owner. There's no setting to send form emails to another address today. The weekly analytics email and traffic alerts go to the same person.

- **Subject:** the form's subject and your site's name, as in the example above.
- **Replying:** if the form has an email field, the message is set to reply to the visitor, so pressing Reply answers them directly.
- **Allowance:** these emails come from Briks to you, so they don't use your [site email](https://briks.dev/docs/site-email) allowance.

## Spam and limits

- Every form carries a hidden field that people never see. A bot that fills it in is thanked and nothing is kept.
- One visitor can send 5 messages in 10 minutes, and a site takes up to 300 a day. Past that, visitors read “Too many messages were sent from here. Try again a little later.”
- A form can have up to 20 fields, and each answer can be up to 5,000 characters. Fields left empty are dropped from the entry.

## Send entries to another tool with a webhook

A webhook is a message Briks sends to another service's web address when something happens on your site. With the **Form received** event, every new entry is passed on as it arrives. Each delivery is signed so the other tool can check it came from your project, and it's tried up to 5 times over about 45 minutes if that tool doesn't answer.

Where

1. Projects
2. Your project
3. Settings
4. Webhooks

1. Get an address from the other tool

   Where: Your other tool

   Most automation, spreadsheet and customer list tools can give you a web address that accepts incoming webhooks. Copy it.

2. Add the webhook

   Where: Add webhook

   Paste it into **Address**, add a **Note** if you like, and under **Events** make sure **Form received** is ticked. Click **Add webhook**.

3. Keep the signing secret

   Where: Your signing secret

   It's shown once. Give it to the receiving tool if it checks signatures.

4. Test it

   Where: Webhooks

   Use **Send a test event** from the webhook's menu, then send a real test from your preview.

Each delivery carries the form's subject, the page, every field and answer, the visitor's reply address, and whether the entry came from production. Preview entries are passed on too, so have your tool skip those if it should only see real ones.

| Plan | Webhooks per project |
| --- | --- |
| Free | 1 |
| Starter | 5 |
| Pro | 10 |
| Studio | 25 |
| Agency | 50 |

A webhook A building firm's quote requests

> Ashdown Builders adds a **Form received** webhook pointing at the spreadsheet tool its office uses, so each quote request lands as a new row.

The email still arrives, the entry still shows under **Forms**, and the office team works from the spreadsheet.

### An entry arrived but no email did.

Check the entry's mark. **preview** means the site isn't in production yet. **not emailed** means sending failed, and the entry is safe in the list. If it says **emailed**, look in your spam folder and check who created the project.

### Can several people get the emails?

Form emails go to one person. Forward them from that inbox, or use a webhook to post each entry into a tool your team shares.

### Can I delete an entry?

Not today.

## Read next

- [Data and automation **Webhooks** Send a signed message to another tool when your site is published, a form is sent or a record changes. Payloads, signatures, retries and deliveries explained.](https://briks.dev/docs/webhooks)
- [Your site's features **Analytics** See who visits your site, where they come from and what they do, counted without cookies. Ask about your visits in plain words, set goals and get weekly emails.](https://briks.dev/docs/analytics)
- [Publishing and domains **Publish to production** Take a Briks site from preview to production: what the launch check reads, what blocks a launch, how to fix each finding and how to go back to preview.](https://briks.dev/docs/publish-to-production)
- [Data and automation **Database** Find what your site stores, edit and add records by hand, and download collections as JSON or CSV, with who can do what and the limits that apply.](https://briks.dev/docs/database)

Still stuck?

Write to [hello@briks.dev](mailto:hello@briks.dev) with your project's name and what you expected to see. A screenshot helps.