Egnyte
Egnyte is the one content platform with a real change feed, and Caryvane uses it: incremental copies ask Egnyte what changed since the last cursor instead of re-listing everything, and a webhook lets a copy run as changes happen.
What you need #
- The Egnyte domain (
acmefor acme.egnyte.com). - An Egnyte user who can see the folders — sign-in happens in the browser. (An access token can be pasted by hand instead.)
- Optionally a base path;
Sharedby default.
Add it as a storage target #
- Storage → Add → Egnyte. Enter the domain.
- Connect Egnyte Account and allow.
- Test. Caryvane registers its change webhook with Egnyte at the same time.
Test on the target's row proves the credentials; a target that fails shows the provider's own message until it is fixed. From then on it can be a job's destination, a cloud-to-cloud source, a cloud drive, or an archive.
What it supports #
| Capability | Egnyte |
|---|---|
| Streams uploads | Yes |
| Version history | Sidecar |
| Realtime cloud-copy source | Yes — Egnyte webhook, registered by Caryvane |
| Incremental copy by change feed | Yes — Events API cursor |
| Cloud-drive mount | Yes |
| Reachable from the Cloud Agent | Yes |
| Browse in the console | Yes |
Things to know #
Tokens expire after 30 days of Egnyte's own policy; Caryvane refreshes them while the connection is in use and shows an authentication failure on the target's row when a refresh is refused (typically the user's Egnyte password changed). Sign in again from Edit.
Rate limits. Egnyte throttles; the provider backs off and continues rather than failing the run.