Two-way sync
Changes in Close or Monday instantly reflect in both systems. No stale data, no manual imports.
Keep Close and Monday in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Monday holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.
Stacksync connects Boards, Items, Subitems, Column values in Monday to Contacts, Opportunities, Activities, Tasks in Close with bi-directional, real-time sync. Activity and record changes in Monday update the matching contact or account in Close, and CRM data flows the other way wherever Monday can store and use it.
Owner, lifecycle stage, or account details from Close sync into Monday, so people working there have the context without switching tools.
Tickets and conversations attach to the right contact and account in Close, so sales sees open issues before the next call.
Enriched fields land directly on records in Close, and refreshes keep them from going stale.
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 | Monday objects | How this pairing syncs | |
|---|---|---|---|
| Users Sales reps referenced as owners on leads, opportunities, and activities. | Users Account members referenced by people columns; read to resolve owner and assignee IDs to names and emails. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Boards Table-like containers that hold items; each board maps to a synced table, and its columns define the field mapping. | Contacts is specific to Close and Boards to Monday — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. | Items Rows within a board and the primary record; synced two-way and created, updated, archived, or deleted via GraphQL mutations. | Opportunities is specific to Close and Items to Monday — each maps to any object or custom field on the other side. | |
| Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. | Subitems Nested rows under items, stored on a separate hidden board; synced as a child table linked to the parent item. | Activities is specific to Close and Subitems to Monday — each maps to any object or custom field on the other side. | |
| Tasks Follow-up items assigned to users; synced for workload and SLA reporting. | Column values Typed fields (status, date, people, numbers, connect-boards); polymorphic JSON usually written together via change_multiple_column_values. | Tasks is specific to Close and Column values to Monday — each maps to any object or custom field on the other side. | |
| Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. | Groups Named sections that group items inside a board; synced as a grouping attribute or category field on the row. | Custom Activities is specific to Close and Groups to Monday — 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.
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
DeliveryEach detected change is written to Monday through its API, with automatic retries and rate-limit backoff.
DetectionMonday notifies Stacksync of record changes through webhook events. Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events.
DeliveryEach detected change is written to Close through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Monday connection.
Changes in Close or Monday instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Close or Monday 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 Monday record.
Track your Close ⇄ Monday sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Close and Monday.
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 Monday 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 Monday 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 Monday: authenticate both systems, choose the objects to sync (such as Close's Users and Contacts), 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 Close and Monday: Where Monday can store CRM context: fields kept current; Where Monday handles support or shared inboxes; Where Monday supplies contact or company data. Owner, lifecycle stage, or account details from Close sync into Monday, so people working there have the context without switching tools.
Close: REST API. Authentication: API key (sent via HTTP Basic auth). Monday: GraphQL API (single endpoint, api.monday.com/v2). Authentication: OAuth 2.0 for installed apps, or a per-user personal API token (admin/member scope); a date-based API version is sent via request header. Stacksync manages authentication, retries, and rate limits on both sides.
Monday: Column values are polymorphic JSON that differ by column type; writes must send correctly shaped values, typically batched via change_multiple_column_values. Close: Custom fields are addressed by stable ids rather than display names, so field mappings survive renames. Stacksync's field mapping accounts for these differences between Close and Monday 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 Monday 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 534 integrations available for Close and Monday.