Kommo + Squarespace: Synchronising Orders and Leads from an Online Store to CRM

Squarespace is used as a storefront and online shop; Kommo is used as the CRM for managing clients. There is no native connector between them: new orders do not create leads in Kommo, buyer data does not enter the pipeline, and managers learn about new orders only from Squarespace notifications. As sales volume grows, this becomes a systemic problem: some clients fall out of sight, repeat sales are not followed up, and sales analytics are maintained in two separate systems.

Why No Native Integration Exists

Squarespace is completely absent from the Kommo marketplace. Third-party platforms — Integrately, Albato — offer a basic trigger of “new order → new contact,” but this scenario covers only a small fraction of real business needs:

• ✅ Creating a contact in Kommo on a new Squarespace order
• ❌ No deal (lead) creation with order data — only a contact
• ❌ No transfer of order line items to deal fields
• ❌ No synchronisation of order status (Fulfilled, Refunded, Cancelled)
• ❌ No transfer of data from Squarespace forms — only Commerce orders
• ❌ No deduplication — a repeat order from an existing client creates a duplicate contact
• ❌ No multi-pipeline logic — new and repeat buyers cannot be separated

Important: Squarespace API Limitations

The Squarespace API is at version 1.0 with a minimal feature set compared to Shopify or WooCommerce. It is important to understand this when designing the integration:

• The Commerce API is only available on Commerce Basic and Advanced plans — on Personal and Business plans, order data is not accessible via the API
• Webhooks only work for Commerce events: order.create, order.update, order.fulfill — no webhooks exist for forms
• Rate limit: 300 requests per minute
• No API for blog subscribers, galleries, or pages

If the site uses only Squarespace forms without Commerce — form data is sent via email notifications rather than the API. In this case, the integration is built on email parsing or Kommo embed forms placed directly in Squarespace pages.

What the Custom Integration from Exceltic.dev Delivers

• Automatic lead creation — every new Squarespace order creates a deal in the correct Kommo pipeline with the order amount, line items, and buyer data
• Line item transfer — each order item (name, quantity, price, SKU) is written to custom deal fields or to the card note
• Contact deduplication — before creating a contact, the system checks for an existing one by email; a repeat order updates the existing contact and creates a new deal without a duplicate
• Status synchronisation — when an order status changes in Squarespace (Fulfilled, Refunded, Cancelled), the corresponding deal field in Kommo is automatically updated
• New vs returning buyer separation — new buyers go into the “New Clients” pipeline; returning buyers go into the “Repeat Sales” pipeline with a different handling logic
• Forms via embed — if the site does not use Commerce, Kommo forms are embedded in Squarespace pages via embed code; form submissions automatically create leads in the correct pipeline
• Tags and segmentation — based on the purchased product category or order amount, tags are automatically assigned to the contact in Kommo for subsequent segmentation

How the Integration Works — Technical Process

Connection Architecture

The integration is built on the stack Squarespace Webhooks → Exceltic middleware → Kommo API. Squarespace sends events when orders are created and updated. Authentication with Squarespace is implemented via an API Key from the site settings. Verification of incoming webhook events is performed via an HMAC-SHA256 signature in the request header.

For sites without Commerce or on plans below Commerce Basic, an alternative architecture is used: Kommo embed forms are inserted into Squarespace pages via the standard Code Block. Form data goes directly to Kommo without an intermediary API call.

Step-by-Step Scenario: New Order in Squarespace Commerce

1. Buyer places an order — Squarespace sends the order.create webhook
2. Middleware verifies the HMAC signature and extracts data: customerEmail, billingAddress, lineItems, grandTotal
3. System looks up the existing contact in Kommo: GET /api/v4/contacts?query={email}
4. If the contact is found — the existing contact_id is used; if not — a new one is created: POST /api/v4/contacts
5. The correct pipeline is determined: new buyer → “New Clients” pipeline; returning → “Repeat Sales”
6. A deal is created with the order amount and custom fields: POST /api/v4/leads
7. Order line items are written to a deal note via POST /api/v4/leads/{id}/notes
8. Deal is linked to the contact via the Association API
9. When the order status changes in Squarespace — the order.update webhook updates the deal field in Kommo

Scenario for Sites Without Commerce: Embed Forms

For Squarespace sites on Personal or Business plans where the Commerce API is unavailable, a different approach is used:

1. A Kommo form is created in the CRM’s form builder
2. The form embed code is inserted into the required Squarespace page via a Code Block
3. When the form is submitted, data directly creates a lead in Kommo — with no intermediary systems
4. The form is styled to match the site design via CSS in Squarespace Custom CSS

What Happens on Error

Squarespace retries webhook delivery on errors up to 3 times. The middleware uses idempotency keys based on Squarespace orderId — a repeat delivery does not create a duplicate deal. If the Kommo API is unavailable, the event is saved to a queue with exponential backoff.

Real-World Case

Event agency, 3 managers, ~30 deals per month, clients in the EU.

The agency used Squarespace as its main site with event booking forms and a small branded merchandise shop. Form submissions arrived by email and were manually entered into Kommo — a manager spent 20–30 minutes per day just transferring data. Some submissions were lost during high-load periods.

The integration resolved both issues: Kommo forms are embedded in Squarespace pages via embed code; event booking submissions automatically create leads in the “Events” pipeline. Shop orders go into a separate “Merch” pipeline with automatic tagging by product category.

Result: 0 lost submissions, 8 hours per month returned to the team, full visibility of all enquiries in a single CRM.

Which Businesses This Suits

The integration is most relevant for small businesses on Squarespace that have grown to a point where manually transferring data from forms and orders to a CRM takes significant time: photographers, event agencies, consultants, designers, and small e-commerce projects.

For companies on Commerce Basic and Advanced plans with a real online shop, the custom integration via the Squarespace Orders API provides full order synchronisation with the Kommo pipeline — including repeat sales and segmentation by product category.

Frequently Asked Questions

Is a Commerce plan in Squarespace required for Kommo integration? For order synchronisation via the Orders API — yes, Commerce Basic or Advanced is required. For form integration via the Kommo embed code, no plan is required — this works on any Squarespace plan, including Personal.

What happens if one client places multiple orders? The middleware checks for the contact in Kommo by email before creating a new one. On a repeat order from an existing client, the contact is updated, a new deal is created, and the contact is automatically moved to the “Repeat Sales” pipeline. Duplicates are excluded.

Can product category data from Squarespace be passed to Kommo? Yes. The product category from Squarespace is passed to a custom deal field and used for automatic contact tagging. This allows segmenting the database by interest and launching personalised follow-up campaigns via Salesbot.

Does the integration support multiple Squarespace sites? Yes. The middleware supports multiple sites with different API Keys — each site is identified by a separate source. Leads from different sites go into different Kommo pipelines or are tagged by source.

How long does the Kommo and Squarespace integration take to develop? Integration via embed forms — 1–2 business days. Full integration via the Squarespace Orders API with deduplication, status synchronisation, and multi-pipeline logic — 3–5 business days. Exceltic.dev determines the exact timeline after the technical briefing.

If you want to connect Squarespace with Kommo and stop transferring data manually — describe your task to the Exceltic.dev team. We will analyse the scenario for your site type and Squarespace plan.