> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/automation/flow-builder/connectors-and-apis/custom-data-fields.md).

# Custom Data Fields

How to use custom data fields you generated in your Apps and APIs?

## How to use custom data fields you generated in your Apps and APIs?

### Step 1: On the right hand side-panel, click on the + button next to apply changes to create and add custom fields to any integration or helper

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48000511221/original/zelZ88NY63hhUr2OLtBAVoTV6hGCVB4Zjw.png?1561475432)

### Step 2: - A grey layover pops up and you can enter your custom field-name and select your desired input type

**Note**: Do **not** enter the same field names as the API uses as standard field names. E.g. If Zendesk uses \`external\_id\` as a standard field name. You should not enter \`external\_id\` again as a custom field name, unless we have not provided the field name yet for any reason. This should generally not be the case, as most SaaS systems ensure themselves that field names are not the same, but better to be on the save side.

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48000511241/original/wjGyrflCZ45MutV12sbSvN3WSVxbnFuQsg.png?1561475467)


---

# 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.locoia.com/automation/flow-builder/connectors-and-apis/custom-data-fields.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.