Content types and limits
Which file types Gurusup accepts, the size and archive limits you can hit, and what each connector brings in from the apps you connect.
Admins and members can upload files. Adding data on a webhook source is for admins only. Both accept the same file types. For the steps, see Upload content and Send data with a webhook.
Accepted file types
| Type | Upload files | Add data on a webhook source |
|---|---|---|
Word (.docx) | Yes | Yes |
PowerPoint (.pptx) | Yes | Yes |
Excel (.xlsx) | Yes | Yes |
PDF (.pdf) | Yes | Yes |
Web page (.html, .htm) | Yes | Yes |
Markdown (.md, .markdown) | Yes | Yes |
Plain text (.txt) | Yes | Yes |
CSV (.csv) | Yes | Yes |
JSON (.json), including Roam and TiddlyWiki exports | Yes | Yes |
Org-mode (.org) and AsciiDoc (.adoc) | Yes | Yes |
Obsidian Canvas (.canvas) | Yes | Yes |
TiddlyWiki note (.tid) | Yes | Yes |
TextBundle (.textpack) | Yes | Yes |
MediaWiki export (.xml) | Yes | Yes |
Evernote export (.enex) | Yes | Yes |
ZIP archive (.zip), including a BookStack Portable ZIP | Yes | Yes |
TAR.GZ archive (.tar.gz, .tgz) | Yes | Yes |
Upload files is the dialog on Sources. During setup and on Home, Drop files opens a side panel called Upload documents with the same file types. Add data is under Content on a webhook source's page: it opens the Send files to dialog. Both dialogs accept the same file types and show the same list under See supported files.
Text files must be saved as UTF-8. JSON files must be valid JSON. An .xml file is read only when it is a MediaWiki export. How each export comes in, and what Gurusup leaves out, is in Exports from other tools.
Limits
| Limit | Upload files | Add data on a webhook source |
|---|---|---|
| File size | 256 MiB (268,435,456 bytes) per file | 25 MiB (26,214,400 bytes) in total for all files in one send. Gurusup says "Upload exceeds the 25 MiB (26,214,400 bytes) combined limit. Choose fewer or smaller files." |
| Number of files | Files are prepared one at a time | 1000 files in one send |
| Archive nesting | 4 levels of archive inside archive | 4 levels |
| Entries in the archives | 100,000 | 100,000 |
| Expanded size, all files together | 1 GiB | 1 GiB |
| Expanded size, one file | 64 MiB | 64 MiB |
| Compression ratio of an archive | 200 to 1 | 200 to 1 |
| Path depth inside an archive | 32 folders | 32 folders |
| Length of a file name or path | 1024 bytes | 1024 bytes |
A file over the size limit is refused with "Upload exceeds the 256 MiB limit. Choose a smaller file."
Messages you may see
| Message | What to do |
|---|---|
| "At most 1000 files may be uploaded." | Send fewer files at a time (webhook Add data). |
| "These files are larger than the upload limit. Upload fewer or smaller files." | Send fewer or smaller files. |
| "The upload exceeds the nested archive depth limit." | Flatten the archive. |
| "The uploaded archives exceed the entry count limit." | Split the archive. |
| "A file exceeds the expanded size limit." or "The uploaded files exceed the total expanded size limit." | Split the archive, or remove very large files from it. |
| "An archive entry exceeds the compression ratio limit." or "An archive exceeds the compression ratio limit." | Re-create the archive without the highly compressed file. |
| "This archive has password-protected files. Remove the password and upload it again." | Remove the password. |
| "name needs a password to open. Upload a copy that opens without a password." | Save a copy of the PDF that opens without a password. An encrypted PDF that opens without one is accepted. |
| "name does not allow text extraction. Ask its owner for an authorized copy that permits text extraction, then upload it." | Ask whoever made the PDF for a copy that allows text extraction. |
| "name can't be opened as a ZIP archive. Re-create it and upload it again." (also for TAR.GZ) | Create the archive again. |
| "name can't be read as text. Save it as plain text (UTF-8) or as a Word file and add it again." | Re-save the file as UTF-8, or as a Word file. |
| "name can't be read as JSON. Check its syntax and upload it again." | Fix the JSON. |
| "name can't be read as a PDF. Check that it opens, then upload it again." | Check the PDF opens, then try again. |
| "name has formulas without saved results. Open it in Excel, save it, and add it again." | Open the workbook in Excel, let it recalculate, save it, and add it again. |
| "The upload contains an unsafe archive symlink." or "unsafe archive link" | Remove links from the archive. |
| "Gurusup can't read PDF files right now. This is on our side. Contact support and we'll sort it out." (also for Office files) | Contact support. |
Messages about the connection, such as "Could not connect to upload the file.", and the Retry and Choose another file buttons are in Upload content.
What Gurusup skips
Inside an upload, Gurusup lists anything it cannot read with a reason that names the file, and does not count it. The rest of the upload still goes through. The same messages appear in Upload files, in Send files on a webhook source, in a Notion export and when an assistant sends files.
| Reason shown | Meaning |
|---|---|
| "name is a kind of file Gurusup can't read. Save it as a PDF, Word or Excel file and add it again." | The file type is not on the list above. This includes images and other binary files inside an archive. |
| "name has no text Gurusup can read, which usually means it's a scan. Export it with selectable text or save it as a Word file, and add it again." | The PDF has no text layer. Gurusup does not read the picture. |
| "name has no text to read. Check that it has content, then add it again." | A Word, PowerPoint or Excel file with nothing to read. |
| "name can't be opened. Open it in Word, Excel or PowerPoint, save a new copy and add that." | A Word, PowerPoint or Excel file that is damaged. |
| "This HTML file has no readable text. Export a version with the page content, then upload it again." | A web page with no text Gurusup can use. |
| A message that starts "This BookStack export", "This MediaWiki export", "This Evernote export", "This Canvas file", "This TiddlyWiki file" or "This TextBundle" | The export could not be read, or it holds no pages or notes with text. The message says how to export it again. The full list is in Upload content. |
Gurusup also ignores the hidden metadata files that macOS adds to archives, and the folders where tools keep settings, trash or copies, such as .obsidian, .logseq, .trash and .git. It leaves out CLAUDE.md and AGENTS.md at the root of an agent-maintained wiki. The upload dialog only offers the file types above, so an image is not offered in the file picker.
If two entries in your selection share the same path, Gurusup lists the colliding paths and turns Confirm upload off until you remove one.
What each source brings in
| Source | What Gurusup reads | Name on Sources |
|---|---|---|
| Slack | New messages in the channels the app has joined. Each channel becomes its own source. Earlier history, direct messages and channels the app has not joined are not read. | One row per Slack workspace, named Slack · workspace name, for example Slack · Acme. Its channels are listed inside, each named Slack #channel-name. A group message is named Slack followed by its members. |
| Notion | The pages you share, from the moment you connect. Older pages come in with Import history (pages edited in a window), with the page picker under Content (only while an import runs), or from a Notion export: Markdown & CSV, with Include subpages, as the ZIP Notion gave you. | Notion: account name |
| HubSpot | Deals, with their linked contacts and activity, from the moment you connect. Earlier deals come in with Import history. | HubSpot: account name |
| Webhook | The JSON object your tool sends to the URL, when it sends it. Files sent with Add data become one document each, named after the file path. | The App name you chose |
| Uploaded files | Each file once, with no ongoing sync. Files inside an archive become one document each, and so does each page of a wiki or note export. | Local Uploads |
If a Notion or HubSpot account has no name, the source is just Notion or HubSpot.
The other connectors (HappyScribe, Holded, ClickUp, Asana, Linear, Granola, tl;dv, Factorial, Sesame, Zernio, monday.com, Attio, Mintlify and Documentation.AI) each have their own page under Connectors overview.
Webhook payloads
Send a POST request with a JSON object as the body. Arrays and other JSON values are rejected. No field is required. If ingestion is paused for your organization, Gurusup accepts the request and answers that it was ignored, but does not store the data.
Names you may also see on Ingest, in the source filter, are Manual knowledge (knowledge saved through an assistant) and Human answer (replies from colleagues).