> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/build-forms/integrations/examples/upload-files-to-google-drive.md).
# Upload Files to Google Drive
Here's a step-by-step walkthrough of how to upload files from Feathery to Google Drive.
1. Navigate to the the integrations tab of your Feathery form
2. Pick Google Drive
3. Pick the “File Submitted” trigger, pick “Upload file” and add/pick the account you would like to upload to
4. Pick the destination folder
### Uploading the file from [File Upload ](https://docs.feathery.io/platform/build-forms/elements/fields/file-upload)
For the public URL, enter the ID of the file upload field whose files you would like to send to Google Drive. Start by entering `{{`, and then filter and pick the ID of the component. Pick the file name you would like to save the file as and click “add” to save the integration.
### **Uploading a custom** [**Autofilled d**](https://docs.feathery.io/platform/signatures-and-document-autofill/autofill-document-templates/pdf-autofill)[**ocument**](/platform/document-autofill-and-signatures/autofill-document-templates/pdf-autofill.md)
Enter `{{` within the Public URL field, filter and pick the PDF you have mapped to. This would the document which has been setup and mapped to in the Documents tab.
### **Upload** [**Form Submission PDF**](https://docs.feathery.io/platform/signatures-and-document-autofill/export-form-submission-pdf)
Make sure “Generate Submissions PDFs” is checked. In the Public URL field enter `{{` and pick “Submission PDF”.
 
{% embed url="" %}
File Upload Demo
{% endembed %}
---
# 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.feathery.io/platform/build-forms/integrations/examples/upload-files-to-google-drive.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.