Dynamo DB to Kustomer integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Dynamo DB and Kustomer: authenticate both systems, choose the objects to sync (such as Dynamo DB's Items and Attributes), map fields visually, and changes propagate both ways in milliseconds — no code required.

On the Kustomer side: Messages, Companies, Custom Objects (Klasses), Users, plus custom fields where Kustomer exposes them. On the Dynamo DB side: Global Secondary Indexes, DynamoDB Streams, Global Tables, Tables. 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 Dynamo DB and Kustomer: Internal tools without API code; Trigger workflows from CRM changes; Query the CRM like a database. Back-office apps read and write the synced tables; Stacksync handles the Kustomer API, limits, and retries.

Dynamo DB: Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries. Authentication: AWS IAM credentials with SigV4 request signing. Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. Stacksync manages authentication, retries, and rate limits on both sides.

Kustomer: Custom object types are called Klasses, and they are the standard mechanism for landing external data like orders and subscriptions where agents work. Dynamo DB: Items are schemaless apart from the mandatory partition key (and optional sort key), so sync field mappings are defined per attribute rather than from a fixed schema. Stacksync's field mapping accounts for these differences between Dynamo DB and Kustomer without custom code.