> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/custom-apps-documentation/create-your-first-app/create-your-app.md).

# Initial setup in Make

{% hint style="info" %}
In our step-by-step examples, we use the Geocodify API. You can follow along with our example or you can select a different API to build your first custom app.
{% endhint %}

To set up your custom app for Geocodify:

{% stepper %}
{% step %}
Log in to Make and go to the **Custom Apps** section.

<div align="left"><figure><img src="/files/iRflBbH7OU8X0jSgSlCZ" alt="" width="132"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
In the upper-right corner, click **+ Create app**.
{% endstep %}

{% step %}
In the pop-up window, fill in the app details. The chart below contains the values to use for your Geocodify app.

<div align="left"><figure><img src="/files/61y2TGohGPmw6eD0TiIy" alt="" width="365"><figcaption></figcaption></figure></div>

<table><thead><tr><th width="150" valign="top">Field</th><th width="207" valign="top">Value</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top"><strong>Name</strong></td><td valign="top">geocodify-app</td><td valign="top">A unique identifier for your custom app. This is an internal name and is not visible in the scenario builder. Must match the following Regex: <code>/^[a-z][0-9a-z-]+[0-9a-z]$/</code><br><br><br><br></td></tr><tr><td valign="top"><strong>Label</strong></td><td valign="top">Geocodify</td><td valign="top">Name of the custom app in the scenario editor.</td></tr><tr><td valign="top"><strong>Description</strong></td><td valign="top">Provides geocoding and access to a spatial database.</td><td valign="top">Optional: Description of the custom app.</td></tr><tr><td valign="top"><strong>Theme</strong></td><td valign="top">#46367f</td><td valign="top">Color of the app in the scenario editor. Specified with a hex code.</td></tr><tr><td valign="top"><strong>Language</strong></td><td valign="top">English</td><td valign="top">The language of your app.</td></tr><tr><td valign="top"><strong>Audience</strong></td><td valign="top">Global</td><td valign="top">Where the app is available. At the moment, this parameter doesn't have any effect.</td></tr><tr><td valign="top"><strong>App logo</strong></td><td valign="top"></td><td valign="top">Optional: Logo of the app used in the scenario editor.<br><br>For more information on logo specs, see the <a href="/pages/KQApAWAFprQ8A2NOBFKX">App logo article</a>.</td></tr></tbody></table>
{% endstep %}

{% step %}
Click **Save**.
{% endstep %}
{% endstepper %}

You can now see your custom app listed on the Custom Apps page where you can view the [Make app environment](/custom-apps-documentation/create-your-first-app/apps-environment.md) to continue with the setup of the [connection](/custom-apps-documentation/create-your-first-app/apps-environment/connection.md), [Base](/custom-apps-documentation/create-your-first-app/apps-environment/base.md), and [module](/custom-apps-documentation/create-your-first-app/apps-environment/module.md) for your app.


---

# 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://developers.make.com/custom-apps-documentation/create-your-first-app/create-your-app.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.
