# Forms

> Receive a static site's contact forms without a backend — mark the form, and submissions arrive in the cabinet and your chats.

Source: https://livops.dev/en/docs/forms

A static site has no server of its own to read a form. Livops reads it for you: mark an ordinary HTML form, deploy, and whatever visitors send shows up in the project's **Forms** tab, in Telegram and in your team's webhooks.

## A contact form

Add `data-livops-form` and a `name` to the form. That is the whole setup.

```html
<form name="contact" method="POST" data-livops-form data-livops-honeypot="company">
  <!-- a field people never see; a bot fills it in -->
  <p hidden><label>Company <input name="company"></label></p>

  <label>Name <input name="name" required></label>
  <label>Email <input name="email" type="email" required></label>
  <label>Message <textarea name="message"></textarea></label>
  <button type="submit">Send</button>
</form>
```

- `method="POST"` is required. Both `application/x-www-form-urlencoded` (the default) and `multipart/form-data` are read.
- The form must be in the HTML the build produced. For a form that JavaScript draws (React, Vue), keep a hidden copy with the same `name` and fields in `index.html`, or send a `livops-form` field with the form's name.
- File uploads are not accepted yet: a submission with a file is refused.

## Where the visitor goes after sending

- **No `action`** — the form posts to its own page and the visitor sees a short thank-you page in the site's language (from `<html lang>`).
- **`action="/thanks"`** — the form posts to `/thanks`, and the visitor is sent to your own `/thanks` page.
- **Sent with `fetch`** and `Accept: application/json` — the answer is `{"ok":true}` and you show your own message.

```js
await fetch(form.action, {
  method: 'POST',
  headers: { Accept: 'application/json' },
  body: new FormData(form),
})
```

## Spam

- **Honeypot.** Name a hidden field in `data-livops-honeypot`. A submission that fills it is kept in the **Spam** list, is not counted and does not notify you — and the sender sees the same thank-you page as a person.
- **Rate limit.** One visitor can send 10 submissions in 10 minutes.
- **Size.** At most 64 KB and 50 fields per submission. HTML tags are stripped from every value.

There is no CAPTCHA.

## Reading submissions

The project's **Forms** tab lists every form with its count. For one form you can search, narrow by date, switch between the inbox and spam, **download a CSV** of exactly what is shown, mark a submission as spam or not, and delete it. The assistant can tell you about the tab but cannot delete anything.

Each submission also arrives in Telegram (when the bot is linked) and in your team's webhooks — Slack and Discord get a formatted message, other addresses get the `form.submission` event as JSON.

## Limits and privacy

- **100** submissions a month on the free plan, across all your sites; **5,000** once the account pays for anything or is on a plan. Spam does not count. Past the limit, 100 submissions cost 1 credit; out of credits, the visitor is told the site is not taking messages right now.
- Submissions are kept for **90 days**, then deleted.
- The sender's IP address is not stored. The rate limit keeps only a salted hash in memory, reset every 10 minutes.
