> For the complete documentation index, see [llms.txt](https://docs.documint.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.documint.me/integrations/hubspot/working-with-custom-object-data.md).
# Working with Custom Object Data
The Documint app can only [launch](/integrations/hubspot/installing-the-documint-app.md#launching-the-documint-app) from **Contacts, Companies, Deals, or Tickets**, so if you would like to work with custom objects, you will need to switch records **within** the Documint app.
First launch the app from a contact, company, deal or ticket and select the template you would like to use.
Once in the dashboard, click on the "change" label that is in the record controls at the top of the dashboard. That will open a record selection overlay.
In the record selection overlay you can switch to your custom object (or any object type for that matter) with the object type dropdown in the top left corner.
Now you will see a new list of records for your selected object type. Pick the one you want to use, and you will return to the document view.
Next, let's add some variables to your template.
---
# 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.documint.me/integrations/hubspot/working-with-custom-object-data.md?ask=&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.
