Egnyte
Browse, upload, share and search files and folders in Egnyte.
About
Egnyte ships in the w6w first-party pack. It declares 19 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.egnyte- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Storage · Productivity
Overview
Egnyte stores and shares company files, and this app lets a workflow work with that content directly: browse folders, create, move, copy and delete files and folders, upload and download file content, and lock a file while a process edits it.
It also covers sharing and discovery. A workflow can create shareable links with an access level, expiry and password, list or revoke existing links, and search file names and text content across everything the connected user can see. User lookups round out the picture so a step can resolve who owns or uploaded a document.
A fit for filing generated reports into the right project folder, handing a customer a time-limited download link, archiving finished work by moving it between folders, or kicking off a process when a search finds a matching document. Every Egnyte customer has its own domain, so each connection records the domain it belongs to.
Build with Egnyte
Three routes to the same 19 actions. The Workflow tab is generated from Egnyte's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Download File
file-download Download a file's content, returned base64-encoded (and as text when it decodes as UTF-8). Intended for small and medium files — the whole body is held in memory.
Lock File
file-lock Lock a file so others cannot modify it. Keep the lock token — Unlock File needs it.
Upload File
file-upload Create or overwrite a file at the given path from text or base64 content. Uses the single-request upload, which Egnyte documents for files up to 100 MB; larger files need the chunked flow, which this action does not cover.
Create Folder
folder-create Create a folder at the given full path. The parent folder must already exist.
Get Folder Statistics
folder-stats Total size and item counts for a folder, including all files and subfolders.
Copy File or Folder
item-copy Copy a file or folder to a new absolute path. If the destination does not include the original folder name, only the folder's contents are copied.
Delete File or Folder
item-delete Delete a file or folder (it goes to the trash). Give an entry ID to delete only one version of a file.
Get File or Folder
item-get Fetch metadata for a file or folder by path. For a folder, turn on 'List contents' to include its files and subfolders (paginated); for a file it includes its versions.
Get File or Folder by ID
item-get-by-id Fetch a file (by its group_id) or a folder (by its folder_id). IDs survive renames and moves, unlike paths.
Create Link
link-create Create a shareable link to a file, folder or upload destination. Set either an expiry date or an expiry click count, not both.
List Links
link-list List shareable links with full details. Non-admins see only the links they created; admins see every link in the domain.
Search Files and Folders
search Search names and text content. Results are limited to what the connected user can access. The query must be 3–100 characters and a page holds at most 20 results.
List Users
user-list List the domain's users, optionally filtered by exact email or username (case-insensitive). Needs the user-management scope and, on most domains, an admin token.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Egnyte's real ids.
{
"manifestVersion": "2",
"name": "egnyte-example",
"steps": [
{
"id": "file-download",
"uses": {
"app": "io.w6w.egnyte",
"action": "file-download",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"path": "<path>"
}
}
]
}Here are some of the things you can do
-
Download File
readfile-download -
Lock File
performfile-lock -
Unlock File
performfile-unlock -
Upload File
performfile-upload -
Create Folder
performfolder-create
+14 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Egnyte, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Egnyte. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "file-download",
payload: {
path: "<value>",
// entryId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action file-download --payload '{"path":"<value>"}'Give an AI agent Egnyte — without giving it Egnyte's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.egnyte#file-download",
"input": {
"path": "<path>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Egnyte connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Egnyte's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Egnyte itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Egnyte declares its own checks, so its health is a property of the app rather than something the host guesses at.
Egnyte Public API status
The 'Public APIs and Integrations' components on status.egnyte.com. The rest of the platform (web UI, sync, AI services) is deliberately not part of the verdict.
Account domain reachable
Unauthenticated request to this connection's Egnyte domain. A 401 passes — it proves the account is serving; credential validity is the `auth:*` check's job.