Skip to content
CRM ⇄ Business productivity

Close to Monday integration — real-time, two-way sync

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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Close and Monday

Sync what happens in Monday with the customer records in Close, in real time and in both directions.

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.

Common use cases

  • 01 Two-way sync of Items and their Column values between a monday.com board and Postgres so ops teams work in SQL while project owners stay in monday.com.
  • 02 Write closed deals or provisioning records from a CRM or ERP into monday.com Items to kick off delivery and onboarding boards.
  • 03 Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.
  • 04 Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.

Common sync patterns

Where Monday can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Close sync into Monday, so people working there have the context without switching tools.

Where Monday handles support or shared inboxes

Tickets and conversations attach to the right contact and account in Close, so sales sees open issues before the next call.

Where Monday supplies contact or company data

Enriched fields land directly on records in Close, and refreshes keep them from going stale.

What you can sync between Close and Monday

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.

How changes propagate between Close and Monday

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.

Close Monday Sub-second propagation

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.

Monday Close Sub-second propagation

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.

Rate-limit considerations

  • Close: Subject to per-endpoint rate limits communicated in response headers.
  • Monday: Complexity-budget limits: a single query caps at 5M complexity points and ~10M points/min per user token (1M on trial/free) over a sliding 60s window.
What ships with Close ⇄ Monday

Connect Close and Monday for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Monday connection.

Real-time

Two-way sync

Changes in Close or Monday instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Close or Monday data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Close or Monday record.

Observability

Monitoring

Track your Close ⇄ Monday sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Close and Monday.

How the Close and Monday connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

Monday

Integration surface
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
Change detection
Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events; polling falls back to the item updated_at field
Capabilities
read · write · webhooks
Rate limits
Complexity-budget limits: a single query caps at 5M complexity points and ~10M points/min per user token (1M on trial/free) over a sliding 60s window
Monday setup guide
How it works

How to connect Close to Monday — three steps, no code

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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Close connected
    Monday connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Close ⇄ Monday
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Close Monday
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Close and Monday integration FAQ

SECURITY

Security teams trust Stacksync

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 534 integrations available for Close and Monday.

Popular · 8 of 534
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.