Two-way sync
Changes in Amazon S3 or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon S3 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; Amazon S3 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 People, Companies, Activities, Tasks in Nutshell aligned with Object tags, Object versions, Prefixes (folders), Multipart uploads in Amazon S3, in real time. A new account or deal can open its own folder in Amazon S3; a document filed in Amazon S3 can surface as a link and metadata on the matching record in Nutshell; and records from Nutshell can be written into Amazon S3 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.
Records from Nutshell are written into Amazon S3 as files or objects on the schedule you set, giving you a durable copy for backup, retention, and compliance without an export to run by hand.
Metadata kept in Amazon S3, such as document type, review state, or whether an agreement is signed, updates a field on the matching record in Nutshell, so people working the account see where the paperwork stands without opening storage.
Attachments that accumulate against a record in Nutshell collect in that customer's folder in Amazon S3, so the full document history lives in one place and is reachable by anyone who needs it.
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.
| Amazon S3 objects | Nutshell objects | How this pairing syncs | |
|---|---|---|---|
| Buckets Top-level, region-scoped containers that hold objects; enumerated to discover the namespaces and prefixes a sync should cover. | Companies Account records that group people and leads for account-level syncs | Buckets is specific to Amazon S3 and Companies to Nutshell — each maps to any object or custom field on the other side. | |
| Objects Files stored under a key; content is read with GET and written with PUT, and each object's key/size/ETag/LastModified is the unit indexed into a database. | Activities Logged calls, meetings, and emails used for engagement reporting | Objects is specific to Amazon S3 and Activities to Nutshell — each maps to any object or custom field on the other side. | |
| Object metadata System metadata (Content-Type, size, ETag, LastModified) plus user-defined x-amz-meta-* headers; user metadata is fixed at write time and only changeable by rewriting the object. | Tasks Rep to-dos mirrored into external work-management or reporting systems | Object metadata is specific to Amazon S3 and Tasks to Nutshell — each maps to any object or custom field on the other side. | |
| Object tags Up to 10 key-value tags per object, mutable in place via the tagging API independent of content, so classification and retention labels sync two-way without rewriting files. | Notes Free-text history attached to leads and contacts, replicated for a full timeline | Object tags is specific to Amazon S3 and Notes to Nutshell — each maps to any object or custom field on the other side. | |
| Object versions When bucket versioning is enabled every write creates a new version ID; prior versions and delete markers are readable for history and audit syncs. | Products Line items attached to leads, used to sync sold products into billing | Object versions is specific to Amazon S3 and Products to Nutshell — each maps to any object or custom field on the other side. | |
| Prefixes (folders) Logical path segments in object keys used to scope a sync and to parallelize throughput, since S3 rate limits partition by prefix. | Tags Segmentation labels mapped to lists or filters in downstream tools | Prefixes (folders) is specific to Amazon S3 and Tags 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.
DetectionAmazon S3 notifies Stacksync of record changes through webhook events. S3 Event Notifications push object-created, object-removed, and object-tagging events to SNS, SQS, Lambda, or EventBridge.
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 Amazon S3 through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon S3–Nutshell connection.
Changes in Amazon S3 or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon S3 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 Amazon S3 or Nutshell record.
Track your Amazon S3 ⇄ Nutshell sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon S3 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 Amazon S3 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 Amazon S3 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 Amazon S3 and Nutshell: authenticate both systems, choose the objects to sync (such as Amazon S3's Buckets and Objects), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Amazon S3: S3 Event Notifications push object-created, object-removed, and object-tagging events to SNS, SQS, Lambda, or EventBridge; there is no modified-since query, so polling relies on each object's LastModified from ListObjectsV2. On Nutshell: Webhook subscriptions for record events, with polling as fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Nutshell side: People, Companies, Activities, Tasks, plus custom fields where Nutshell exposes them. On the Amazon S3 side: Object tags, Object versions, Prefixes (folders), Multipart uploads. Stacksync auto-detects both schemas and converts types between the two systems.
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 Amazon S3 and Nutshell: CRM records archived into storage; Document status on the record; One place for a customer's files. Records from Nutshell are written into Amazon S3 as files or objects on the schedule you set, giving you a durable copy for backup, retention, and compliance without an export to run by hand.
Amazon S3: S3 REST API (also via AWS SDKs and the S3-compatible endpoint). Authentication: AWS IAM credentials — an access key ID and secret access key signed with AWS Signature Version 4; supports temporary STS credentials and cross-account IAM roles. 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.
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 Amazon S3 and Nutshell.