Two-way sync
Changes in Egnyte or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Keep Egnyte and Nutshell in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Nutshell holds the customer relationship as structured records; Egnyte holds the files that belong to those relationships, from contracts and proposals to signed agreements and statements of work. The two are linked in practice and disconnected in software: someone downloads a document, renames it, and uploads it to the right folder, or exports records out to storage for retention. Done by hand, files drift away from the records they belong to and copies fall out of date.
Stacksync keeps Notes, Products, Tags, Users in Nutshell aligned with Links, Metadata, Events and Audit reports, Files in Egnyte, in real time. A new account or deal can open its own folder in Egnyte; a document filed in Egnyte can surface as a link and metadata on the matching record in Nutshell; and records from Nutshell can be written into Egnyte as files or objects for backup, archival, and compliance. You choose which side owns what, and Stacksync keeps the two consistent as either one changes.
Attachments that accumulate against a record in Nutshell collect in that customer's folder in Egnyte, so the full document history lives in one place and is reachable by anyone who needs it.
When an account or deal is created in Nutshell, a matching folder or container opens in Egnyte, named and organized the same way, so files have a home the moment they are needed.
A contract, proposal, or signed agreement filed in Egnyte surfaces as a link on the matching record in Nutshell, so the customer's paperwork sits with the relationship instead of a shared drive.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Egnyte objects | Nutshell objects | How this pairing syncs | |
|---|---|---|---|
| Users Accounts managed via the Users API; provisioned, updated, and deactivated in sync with an HRIS or identity provider. | Users Rep records used to resolve ownership when syncing assignments | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Events and Audit reports File, login, permission, and sharing activity read via the Events API and Audit Reporting API; consumed read-only for compliance. | Leads Nutshell's deal object; synced as the pipeline record linked to people and companies | Events and Audit reports is specific to Egnyte and Leads to Nutshell — each maps to any object or custom field on the other side. | |
| Files File content managed via the fs-content endpoint (upload/download, chunked for large files); synced two-way with other stores. | People Individual contacts, kept consistent with marketing and outreach tools | Files is specific to Egnyte and People to Nutshell — each maps to any object or custom field on the other side. | |
| Folders Folder hierarchy managed via the fs endpoint (create, move, rename, delete); the tree structure is mirrored during sync. | Companies Account records that group people and leads for account-level syncs | Folders is specific to Egnyte and Companies to Nutshell — each maps to any object or custom field on the other side. | |
| Groups Groups and membership managed via the Groups API; kept aligned with directory or IdP groups that drive folder access. | Activities Logged calls, meetings, and emails used for engagement reporting | Groups is specific to Egnyte and Activities to Nutshell — each maps to any object or custom field on the other side. | |
| Permissions Folder permissions listed, set, and removed via the Permissions API; effective permission for a user/folder is computable. | Tasks Rep to-dos mirrored into external work-management or reporting systems | Permissions is specific to Egnyte and Tasks to Nutshell — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionEgnyte notifies Stacksync of record changes through webhook events. Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata,.
DeliveryEach detected change is written to Nutshell through its API, with automatic retries and rate-limit backoff.
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
DeliveryEach detected change is written to Egnyte through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Egnyte–Nutshell connection.
Changes in Egnyte or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Egnyte or Nutshell data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Egnyte or Nutshell record.
Track your Egnyte ⇄ Nutshell sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Egnyte and Nutshell.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Egnyte and Nutshell with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Egnyte and Nutshell objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Egnyte and Nutshell: authenticate both systems, choose the objects to sync (such as Egnyte's Users and Events and Audit reports), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Egnyte and Nutshell: One place for a customer's files; A folder per account or deal; Documents linked back to the record. Attachments that accumulate against a record in Nutshell collect in that customer's folder in Egnyte, so the full document history lives in one place and is reachable by anyone who needs it.
Egnyte: REST Public API (pubapi/v1) with File System, Users, Groups, Permissions, Links, Metadata, Events, and Webhooks endpoints. Authentication: OAuth 2.0 scoped access tokens (Authorization Code or Implicit for partner apps, Resource Owner Password for internal apps, Refresh Token flow); token sent in the Authorization header. Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. Stacksync manages authentication, retries, and rate limits on both sides.
Nutshell: The deal object is called a Lead in Nutshell, and it links to separate People and Company records rather than replacing them. Egnyte: File content operations use a separate fs-content endpoint (upload/download) from the fs metadata endpoint, and large files use chunked upload. Stacksync's field mapping accounts for these differences between Egnyte and Nutshell without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Egnyte and Nutshell records are not retained after a sync operation.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 411 integrations available for Egnyte and Nutshell.