> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/utils/forms/form-trigger.md).

# Form Trigger

### Overview

The **Form Trigger Component** creates web-based forms, collects entries, and processes submitted data dynamically. It provides a unique form URL and sends submitted form data to an output port.

### Usage

This component is used to generate forms with configurable fields and receive responses for further processing in workflows.

#### Properties

| Property                      | Type      | Description                                                            |
| ----------------------------- | --------- | ---------------------------------------------------------------------- |
| `generateInspector`           | `boolean` | Enables the dynamic generation of an inspector for form configuration. |
| `generateEntryOutPortOptions` | `boolean` | Enables dynamic generation of form entry output port options.          |
| `url`                         | `string`  | The unique URL for accessing the generated form.                       |

#### Input Ports

| Port | Description                                                                  |
| ---- | ---------------------------------------------------------------------------- |
| `in` | Accepts form configurations such as title, fields, and CTA (Call-To-Action). |

#### Output Ports

| Port    | Description                |
| ------- | -------------------------- |
| `entry` | Emits submitted form data. |

#### Processing Logic

1. **Generates Web Form**:
   * Creates a publicly accessible web link for the form.
   * Displays the form with configured fields and call-to-action text.
2. **Handles Form Submissions**:
   * When a user submits the form, the entries are sent to the `entry` output port.
   * Supports custom JavaScript and CSS for styling and tracking.
3. **Sends Response**:
   * Upon submission, the user is redirected to a thank-you message or page.

#### Output Data Schema

| Property        | Type     | Description                                       |
| --------------- | -------- | ------------------------------------------------- |
| `title`         | `string` | The title of the form.                            |
| `description`   | `string` | The description of the form.                      |
| `fields`        | `object` | The defined input fields of the form.             |
| `cta`           | `string` | The label of the submit button.                   |
| `thanksMessage` | `string` | The thank-you message displayed after submission. |
| `entries`       | `object` | The form submission data.                         |

### Notes

* **Webhook-Based Execution**: Captures and processes form submissions in real-time.
* **Customizable Design**: Supports JavaScript and CSS for styling and tracking.
* **Ideal for Data Collection**: Useful for surveys, feedback, and automation workflows.

This component is essential for workflows requiring automated form generation, structured data collection, and real-time response processing.


---

# 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:

```
GET https://docs.appmixer.com/connector-configuration/utils/forms/form-trigger.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.