Your organization's own files, as an app every workflow, agent and the assistant can use. List the files of your folders that were added, changed, renamed, moved or deleted since the last run, in the last days or between two dates — filtered by type, name, size, language, status, fields and notes — then read them, search them by meaning or exact words, save a run's output as a file, move, rename, annotate or delete files. Everything runs with the access of the person the run is for, and a workflow never reads its own output back as new files.
Knowledge is mapped and documented, but one-click connection isn't live yet — the app shows it as Coming soon. Only Google Calendar, Drive, Mail, and Tasks are connectable today; see the Standard integrations catalogue for what's live now.
| Category | ✅ Productivity |
| Connection | Coming soon not yet connectable — once live it will connect via Built in — nothing to connect. |
| Actions | 10 total — 4 read, 6 write |
Once connected, Knowledge exposes the following actions. The AI can call them with #-mentions in chat, an agent can be granted a subset as tools, and a workflow can run them in an integration-action node.
| Action | Type | What it does | Proxy |
|---|---|---|---|
Add Noteadd-note | Write | Add a note to a Knowledge file — what a person sees in its Notes panel. | — |
Delete Filedelete-file | Write | Delete a Knowledge file for good, with its text and history. Only the folder's owner may delete. | — |
Folder Activityfolder-activity | Read | Read the activity feed of Knowledge folders in a period: files added, changed, renamed, moved and deleted, notes and fields set, scans and translations. | — |
List Fileslist-files | Read | List the files of one or more Knowledge folders that were added, changed, renamed, moved or deleted in a period — since the last run, the last N days, between two dates, last week — filtered by type, name, size, language, status, fields and notes. Each file is listed once, under the most significant thing that happened to it. Files still being read are listed too, marked as still being read. | — |
Move Filemove-file | Write | Move a Knowledge file to another folder. The person this runs for must be able to change both folders. | — |
Read Fileread-file | Read | Read a Knowledge file's text — whole, a page range, or its stored summary. A long file is read as its summary unless the whole text is asked for. A file still being read answers that it is not ready yet. | — |
Rename Filerename-file | Write | Rename a Knowledge file. Its content, notes and history stay as they are. | — |
Save Filesave-file | Write | Save text or a file from an earlier step as a file in a Knowledge folder — as a new file, replacing the file of the same name, or added to the end of a text file. | — |
Searchsearch | Read | Search the files of Knowledge folders by meaning or by exact words, and get the matching passages with the file they come from. | — |
Set Fieldsset-fields | Write | Set fields on a Knowledge file (invoice number, amount, date…) and optionally its title. A field a person set by hand is left as it is and named in the answer. | — |
Actions tagged Write create, update, or delete data. In chat and agent paths they pause for your confirmation before running; workflows treat their deterministic wiring as implicit consent. Agent tools covers how to scope which actions an agent may use.
Knowledge is governed per organization: an admin sets a monetary spend cap and a monthly call quota. A quota of 0 disables the integration — it never means unlimited. See the Integrations overview for the full governance model.