> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/component-designer/ai-custom-components/auto-generate-parameters-and-actions.md).

# Auto-Generate Parameters and Actions

Jet Admin’s AI can automatically generate the parameters and actions your custom component needs — based entirely on your prompt.

<figure><img src="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FnfGjBFE2a3V14ifJQaPO%2FFrame%208473-min.jpg?alt=media&amp;token=25a9cfe4-c358-4c48-bd92-cf12cdb5fa78" alt=""><figcaption></figcaption></figure>

### How It Works

1. **Write a Clear Prompt**\
   Describe what your component should do, including any fields or interactions.\
   Example:

   > "A user profile card showing name, email, and a button to send a message."
2. **Let the AI Auto-Generate**\
   After processing your prompt, Jet Admin automatically:
   * **Creates parameters** (e.g., `name`, `email`, `profileImage`)
   * **Adds actions** (e.g., `sendMessage` function on button click)
3. **Review and Customize**\
   Once generated:
   * Review the parameters and actions.
   * Adjust or rename them if needed.

{% @arcade/embed flowId="Qix2MXQkru95sk9RSGEs" url="<https://app.arcade.software/share/Qix2MXQkru95sk9RSGEs>" %}

{% hint style="info" %}

### 📋 Best Practices

**Mention Actions Clearly in Your Prompt**:\
If you want something clickable or interactive, make sure to say it.

**Use Descriptive Names**:\
Good field names (like `userName` instead of just `text`) help with clean, understandable code.

**Check and Test**:\
Always preview your generated actions to ensure they behave as expected.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/classic-app-builder/component-designer/ai-custom-components/auto-generate-parameters-and-actions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.