> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# n8n CRM sync

> Sync external CRM data into Soundcheck through a signed n8n webhook

n8n CRM sync lets an automation workflow push external CRM data into Soundcheck. Use it for organization-specific imports from HubSpot, Flex, or a custom booking system.

![Sync section with the HubSpot ↔ Flex pipeline card, its last run and the Sync now button, above the Pipeline cross-links table](https://mintcdn.com/soundchecklive/65-EmLPt4EBexIaJ/images/integrations/pipeline-sync-light.png?fit=max\&auto=format\&n=65-EmLPt4EBexIaJ\&q=85\&s=c3d4d31c8cd466e9056f0b5ff91c29f9)

> [!NOTE]
>
> For a bidirectional setup that keeps HubSpot deal stages, Flex quotes, and Soundcheck gig status in lockstep, see the [HubSpot ↔ Flex pipeline](https://docs.soundchecklive.io/integrations/hubspot-flex-pipeline.md), part of Sync Engine on Enterprise. It builds on the same signed-webhook foundation.

## Endpoint

Send sync requests to:

```http theme={null}
POST /webhooks/n8n/crm-sync
```

The webhook can ingest customers, contacts, venues, events, and external ID mappings in one signed request.

## Required configuration

Configure these environment variables before enabling the workflow:

| Variable | Purpose |
| - | - |
| `N8N_CRM_SYNC_SECRET` | Shared secret used to sign webhook requests |
| `N8N_CRM_SYNC_ORGANIZATION_ID` | The Soundcheck organization allowed to receive this feed |

The request body must include `soundcheck_organization_id`, and it must match the configured organization ID.

## Request signing

Every request must include an HMAC-SHA256 signature:

```http theme={null}
X-Soundcheck-N8N-Signature: sha256=<hex-digest>
```

Generate the digest from the raw request body using `N8N_CRM_SYNC_SECRET`.

> [!WARNING]
>
> Unsigned requests, incorrectly signed requests, or requests for the wrong organization are rejected.

## What the request can include

The sync request body can include:

* Customer identity and contact details
* Additional contacts
* Venue records
* Event records
* External IDs for deduping and future updates

Use stable external IDs from the source CRM whenever possible. They let you run the sync again without creating duplicate records.

## Recommended n8n flow

**1. Trigger from source CRM**

Start when a customer, booking, contact, or event changes in the external system.

**2. Normalize data**

Map the source fields into Soundcheck's sync request shape.

**3. Sign the request**

Compute the HMAC signature from the raw JSON body.

**4. POST to Soundcheck**

Send the request to `/webhooks/n8n/crm-sync` with the signature header.

## Related CRM pages

> [card] [Customers](https://docs.soundchecklive.io/crm/customers.md)
>
> Synced customer records appear in the customer directory.

> [card] [Venues](https://docs.soundchecklive.io/features/gigs/venue.md)
>
> Synced venues can be saved and reused on gigs.

> [card] [Leads](https://docs.soundchecklive.io/crm/leads/overview.md)
>
> Use public lead intake for inquiries that should start as pipeline records.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.