> For the complete documentation index, see [llms.txt](https://docs.planetcrust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.planetcrust.com/docusign/docusign/query-find-form-data-for-envelope.md).
# Query: Find Form Data for Envelope
Docusign Operation
The Find Form Data for Envelope query extracts all form field data entered by signers in a completed DocuSign envelope.
{% embed url="" %}
#### Example User Story
I want to find all form data from a signed DocuSign contract, so I can automatically update our database with the client’s selected options and details.
#### Fields
| Field Name | Field Type | Required |
| ---------- | ---------- | -------- |
| envelopeId | String | Yes |
### Related Connections
[Docusign](/docusign/docusign.md)
### Related Automations
Example link
### Code (Apache v2.0): Operation
```
{
"handle": "find-form-data-for-envelope",
"state": "inDev",
"meta": {
"short": "Find Form Data for Envelope",
"description": "Retrieves form data associated with a specific envelope in DocuSign."
},
"input": [
{
"name": "envelopeId",
"type": "String",
"required": true,
"meta": {
"description": "The unique identifier of the envelope."
}
}
],
"output": [
{
"name": "formData",
"type": "String",
"selector": ["formData"],
"meta": {
"description": "The form data associated with the envelope."
}
}
],
"steps": [
{
"type": "http",
"http": {
"method": "GET",
"path": {
"value": "/v2.1/accounts/{{accountId}}/envelopes/{{envelopeId}}/form_data",
"placeholders": [
{
"name": "accountId",
"type": "String",
"description": "The unique identifier of the DocuSign account.",
"required": true
},
{
"name": "envelopeId",
"type": "String",
"description": "The unique identifier of the envelope.",
"required": true
}
]
},
"headers": {
"Content-Type": {
"value": "application/json"
}
}
}
}
]
}
```
---
# 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.planetcrust.com/docusign/docusign/query-find-form-data-for-envelope.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.
