# Url queries in forms

**URL:** <https://community.noloco.io/t/url-queries-in-forms/1811>\
**Category:** Ask for Help\
**Created:** [March 18, 2025, 8:06pm UTC](https://community.noloco.io/t/url-queries-in-forms/1811 "2025-03-18T20:06:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sdamceski](https://avatars.discourse-cdn.com/v4/letter/s/e495f1/32.png) [@sdamceski](https://community.noloco.io/u/sdamceski)\
**Post date:** [March 18, 2025, 8:06pm UTC](https://community.noloco.io/t/url-queries-in-forms/1811/1 "2025-03-18T20:06:49Z")

</div>

I’m working on a form with specific configurations and need to pass query parameters for various fields. I can successfully pass all the fields I need, except for the phone number, full name, and address fields. These fields have sub-fields, and I’m struggling to find a way to include them. Has anyone successfully done this before?

Thank you in advance.

---

<div class="post-metadata">

**Author:** ![carlos](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@carlos](https://community.noloco.io/u/carlos)\
**Post date:** [March 19, 2025, 3:34am UTC](https://community.noloco.io/t/url-queries-in-forms/1811/2 "2025-03-19T03:34:18Z")

</div>

Hi @sdamceski,

We don’t support passing query parameters for Noloco phone number, full name, and address fields. This is because these fields contain multiple sub-values, making them incompatible with query parameters at the moment. Hopefully, the team can figure out a way to make it work at some point.

---

<div class="post-metadata">

**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\
**Post date:** [September 23, 2025, 7:27am UTC](https://community.noloco.io/t/url-queries-in-forms/1811/3 "2025-09-23T07:27:52Z")

</div>

Hey @sdamceski - good news is that we now natively support prefilling _Full Name, Phone Number_, and _Coordinates_ fields from the URL in any form.

Right now, we still don’t support address fields, so if you’re relying on that, you might need to use a text field instead.

Thanks for mentioning it though - looking forward to any other feedback you might have