> For the complete documentation index, see [llms.txt](https://storypress.gitbook.io/storypress-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://storypress.gitbook.io/storypress-docs/content-blocks/lead-form.md).

# Lead form

The **Lead form** block is a CRM lead form that collects information from visitors (e.g. name, email, phone) and sends it to your CRM or a custom endpoint.

***

## What you can do

* Add a **heading** (optional rich text) above the form.
* Add **form fields** (e.g. name, email, message) and optional **cookie-consent** fields.
* Set the **submit button** label (default: "Submit") and optional **success message** after submit.
* Optionally use a **card** layout and **background** (or **card inner background**) for the form area.
* Customize **button and input colors** (background, text, hover, active) and **label** color.
* Send submissions to a **custom endpoint** (URL) or use **board ID** / **group title** for CRM integration.
* Set a **form ID** so you can link to this form (e.g. `#my-form-id` from a CTA).

***

## Adding fields

Inside the Lead form block you add:

* **Form field** — A visible input (text, email, etc.). You can mark a field as **hidden** and set its **name** and **value** for internal use (e.g. campaign ID).
* **Form field (cookie)** — For cookie/consent fields when needed.

You need at least one form field. Add as many as you need for name, email, phone, message, etc.

***

## Main options

| Option                                                | Description                                                                                     |
| ----------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Heading**                                           | Optional rich-text block above the form.                                                        |
| **Fields**                                            | The form fields (required; add at least one).                                                   |
| **CTA**                                               | Button label (e.g. "Submit", "Send").                                                           |
| **Form ID**                                           | ID for deep-linking (e.g. `#my-form-id`). Use this in a CTA or menu link to scroll to the form. |
| **Success message**                                   | Text shown after a successful submit.                                                           |
| **Always stacked**                                    | When on, fields stay stacked vertically on all screen sizes.                                    |
| **Endpoint**                                          | Server or serverless URL that receives the form submission (must start with `https://`).        |
| **Board ID** / **Group title**                        | Optional CRM identifiers sent as hidden fields with the submission.                             |
| **Card** / **Background** / **Card inner background** | Layout and background options for the form container.                                           |
| **Colors** (tab)                                      | Button and input colors (background, text, hover, active, label, placeholder).                  |

***

## Tips

* Use **Form ID** so "Contact us" or "Request a demo" buttons can jump straight to the form.
* If your CRM expects a specific **board ID** or **group title**, set them so every submission is tagged correctly.
* The **endpoint** must accept POST and handle the field names you use; your StoryPress or CRM admin can provide the URL.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://storypress.gitbook.io/storypress-docs/content-blocks/lead-form.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.