Two-way sync
Changes in Close or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.
Keep Close and Google Cloud Spanner in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Google Cloud Spanner, where it can be queried and joined like everything else.
Stacksync mirrors Opportunities, Activities, Tasks, Custom Activities from Close into Secondary indexes, Change streams, Views, Databases in Google Cloud Spanner with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Close with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Accounts, contacts, and custom objects from Close become tables in Google Cloud Spanner you can join with application data directly.
Signup, usage, or lifecycle changes written to Google Cloud Spanner sync onto the matching records in Close, giving go-to-market teams live product context.
Back-office apps read and write the synced tables; Stacksync handles the Close API, limits, and retries.
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.
| Close objects | Google Cloud Spanner objects | |
|---|---|---|
| Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. | Interleaved tables Child rows physically co-located with parents; synced as related records. | |
| Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. | Secondary indexes Used to make incremental read queries efficient on non-key columns. | |
| Users Sales reps referenced as owners on leads, opportunities, and activities. | Change streams Capture inserts, updates, and deletes for log-style change data capture. | |
| Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Views Read-only projections useful for shaping data before it leaves Spanner. | |
| Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Databases Top-level containers that scope schema and sync configuration. | |
| Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Tables Relational tables mapped one-to-one to sync targets. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Google Cloud Spanner connection.
Changes in Close or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Close or Google Cloud Spanner data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Close or Google Cloud Spanner record.
Track your Close ⇄ Google Cloud Spanner sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Close and Google Cloud Spanner.
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 Close and Google Cloud Spanner 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 Close and Google Cloud Spanner 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 Close and Google Cloud Spanner: authenticate both systems, choose the objects to sync (such as Close's Custom Activities and Custom Fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
Close: REST API. Authentication: API key (sent via HTTP Basic auth). Google Cloud Spanner: GRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects). Authentication: Google Cloud IAM (service accounts). Stacksync manages authentication, retries, and rate limits on both sides.
Close: Custom fields are addressed by stable ids rather than display names, so field mappings survive renames. Google Cloud Spanner: It supports two SQL dialects: GoogleSQL and a PostgreSQL-interface dialect chosen at database creation. Stacksync's field mapping accounts for these differences between Close and Google Cloud Spanner 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 Close and Google Cloud Spanner records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Close and Google Cloud Spanner connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Close–Google Cloud Spanner integration in-house.
Yes — Stacksync ships production-grade connectors for both Close and Google Cloud Spanner. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 386 integrations available for Close and Google Cloud Spanner.