> For the complete documentation index, see [llms.txt](https://docs.pazly.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pazly.dev/integrations/collecting-subscriptions/subscriptions-and-contact-info-with-tally-forms.md).
# Subscriptions & Contact Info with Tally Forms
Tally Forms is a visual form development platform, which is built with the non technical use in mind. They made it easy for everyone to create and use forms. Let's learn how to collect email subscribers on your Pazly website.
Make an account with Tally They have a very generous free offer which might be enough for your one page website. Once you've signed up and logged in, create a new form or clone of their templates. In the example below, I cloned the **Subscribe template.**\
**Make sure to publish the form.**
**Pazly allows you to embed \ in every text element.** Simply build your website and choose the text element that will carry this subscription form. **On the Tally Forms page**, click share, then scroll until the Embed Form. Click on Standard, then Get the Code. \
Copy the Embed Code of your Tally Form, Paste it in your Pazly website text content field. Try it out in Pazly by clicking the Preview button
{% embed url="" %}
---
# 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://docs.pazly.dev/integrations/collecting-subscriptions/subscriptions-and-contact-info-with-tally-forms.md?ask=&goal=
```
`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.