native Google file formats (like: .gdoc) support

[petermuldoon]

Native .gdoc support (or a direct Google Drive sync for knowledge vaults) would save a huge amount of time in uploading files into Vaults.  Only supporting Microsoft files formats seems like an oversight that hopefuly can easily to fixed.  I have hundreds or thousands of Google Doc (.gdoc) files and use Google Sheets and Google Slides as well.  I cannot add files to HubSpot Vaults by creating copies of these files in Microsoft equivilent formats.  Please add these mainstream formats. Thanks

[karstenkoehler · Accepted solution]

@petermuldoon thank you for clarifying - the same steps would apply, you would have to request this in the ideas section.

Sharing here here the Idea you created "Files in Vaults with extensions that support native Google file formats ( like .gdoc)" (thanks @petermuldoon) so that other Community Members can add their upvote and use cases.

For context, keep in mind that Google files like gdoc don't contain the actual content, there just a small shortcut file (a JSON file) that contains:

• A link to the document online

• Some metadata (title, ID, etc.)

It does not contain your text.

[RubenBurdin · Accepted solution]

Hi @petermuldoon , your frustration is understandable, especially if your knowledge base already lives 100% in Google Workspace. What Karsten explained is the key technical reason behind the limitation: native Google files like .gdoc, .gsheet, and .gslides don’t actually contain the document content. They’re essentially pointer files with an ID and a URL, not the text itself, so HubSpot can’t ingest or index them the way it does with .docx or .pdf files (https://knowledge.hubspot.com/files/supported-file-types).

With how Vaults work now in 2025, especially as a source for Breeze and AI agents, HubSpot needs the full file contents locally so it can parse, chunk, and reason over them. Linking out to Google Docs wouldn’t give the AI anything to read unless HubSpot built a much deeper Google Drive integration that fetches and keeps content in sync, which is a non-trivial product change.

Practically speaking, today the only real workaround is exporting Google Docs to a supported format like .docx or .pdf before uploading, or maintaining a parallel “AI-ready” copy of critical docs in a supported format. Not ideal, but at least predictable. You did the right thing by submitting an Idea, that’s genuinely the only channel that influences this kind of roadmap item, especially for newer features like Vaults tied to AI.

Hopefully more teams upvote it. You’re definitely not the only one running into this.

[RubenBurdin · Accepted solution]

Hi @petermuldoon , your frustration is understandable, especially if your knowledge base already lives 100% in Google Workspace. What Karsten explained is the key technical reason behind the limitation: native Google files like .gdoc, .gsheet, and .gslides don’t actually contain the document content. They’re essentially pointer files with an ID and a URL, not the text itself, so HubSpot can’t ingest or index them the way it does with .docx or .pdf files (https://knowledge.hubspot.com/files/supported-file-types).

With how Vaults work now in 2025, especially as a source for Breeze and AI agents, HubSpot needs the full file contents locally so it can parse, chunk, and reason over them. Linking out to Google Docs wouldn’t give the AI anything to read unless HubSpot built a much deeper Google Drive integration that fetches and keeps content in sync, which is a non-trivial product change.

Practically speaking, today the only real workaround is exporting Google Docs to a supported format like .docx or .pdf before uploading, or maintaining a parallel “AI-ready” copy of critical docs in a supported format. Not ideal, but at least predictable. You did the right thing by submitting an Idea, that’s genuinely the only channel that influences this kind of roadmap item, especially for newer features like Vaults tied to AI.

Hopefully more teams upvote it. You’re definitely not the only one running into this.

[petermuldoon]

A user can mark multiple files in their GDrive at once. Then there is a
download feature where a zip file is created. Nicely, the zip file stores
the gdoc files as .doc files (same is true for spreadsheet files.). So if
HubSpot could accept the upload of a zip file - which once unzipped, will
be files in the .doc and .xls formats required.

The upload feature is limited to 20 files at a time (another setback for
me). I have 370 document files and one zip file is much better.

[karstenkoehler · Accepted solution]

@petermuldoon you can always request this in the ideas section - but keep in mind that few tools accept zip files as a file format due to the risk it could pose upon unpacking the files.

[petermuldoon]

Ok, well it would still be a big improvement to allow many more files for
each upload - say 100 instead of 20. I could create a temp folder to unzip
to, then upload (100 at a time). Side note, I know its new software and
will settle down over time, but even when uploading 20 files, the process
often fails to load them all and you are left trying to figure it out what
missed.

[karstenkoehler]

Hi @petermuldoon,

What are you referring to when you say HubSpot vault? I'm not familiar with any feature that is named that way.

In general however, correct, Google file types are not currently supported: https://knowledge.hubspot.com/files/supported-file-types

You could request this from the product team by submitting a post here: https://community.hubspot.com/t5/HubSpot-Ideas/idb-p/HubSpot_Ideas

Best regards

[petermuldoon]

See Vaults - under Breeze, Knowledge, then see button on right side of
screen to Create Vault. They are necessary for using AI agents.
[image: image.png]

[karstenkoehler · Accepted solution]

@petermuldoon thank you for clarifying - the same steps would apply, you would have to request this in the ideas section.

Sharing here here the Idea you created "Files in Vaults with extensions that support native Google file formats ( like .gdoc)" (thanks @petermuldoon) so that other Community Members can add their upvote and use cases.

For context, keep in mind that Google files like gdoc don't contain the actual content, there just a small shortcut file (a JSON file) that contains:

• A link to the document online

• Some metadata (title, ID, etc.)

It does not contain your text.