# Ask: Address

The **Ask: Address** node allows you to request a user's address within a Flow.

The node will ask a user for their address, and will perform a lookup via the [Google Maps Geocoding API](https://developers.google.com/maps/documentation/geocoding/get-api-key).

#### Installing

To install the skill you need to provide a Google Maps API key. You can [read on how to obtain an API key here](https://developers.google.com/maps/documentation/geocoding/get-api-key#console). After creating your API key, store it in the 'Integrations - Secrets'.

#### Settings

Via the 'Settings - Google Maps' settings page, you can configure boundaries for addresses.

1. **Enable bias to specified region**\
   This enables you to only allow addresses which are located in the specified country.
2. **Enable bias to specific boundary**\
   Here you can specify two points on the map: the outermost north-east part and the outermost south-western part of an area. Together they form a square in which the address must be located.
3. **Components filter expression**\
   This allows for a more fine-grained expression with which the addresses must comply.

<figure><img src="/files/iNHRyENSVpDXbuE3GaTQ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/YN9z1gERRjEJ9A5U2JjU" alt="" width="375"><figcaption></figcaption></figure>

### Built-in variables

Once the address is validated by the user, the following built-in [variables](/studio/flows/variables.md) are available, making it easier for you to build your Flow around different parts of the address:

| Variable          | Description                                                                         |
| ----------------- | ----------------------------------------------------------------------------------- |
| **Full address**  | The complete address on a single line                                               |
| **Longitude**     | The longitude of the address location, e.g. 4.897070                                |
| **Latitude**      | The latitude of the address location, e.g. 52.377956                                |
| **Name**          | In case a POI (Point of Interest) was provided, this will be the name of the POI    |
| **Postal Code**   | The postal code (zip code) of the address                                           |
| **Country Code**  | The ISO 3166-2 country code                                                         |
| **Country**       | The full name of the country                                                        |
| **City**          | The city                                                                            |
| **Subpremise**    | When an address is split into multiple subpremises, e.g. "E" in 92-E Clapham Street |
| **Street number** | The house number on the street                                                      |
| **Street**        | The street name                                                                     |

### Node properties

| Property  | Description                                             | Required |
| --------- | ------------------------------------------------------- | -------- |
| Question  | The initial message to ask for the user's address       | Yes      |
| Remember  | To store the variable in the user object                | No       |
| Assign to | The variable where the collected address will be stored | No       |

## Resources

* [Address Flows](/store/skills/address-flows.md)
* [Variables](/studio/flows/variables.md)
* [Google Maps Geocoding API Documentation](https://developers.google.com/maps/documentation/geocoding/get-api-key)


---

# Agent Instructions: 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://manuals.dialox.ai/studio/flows/nodes/ask-address.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.