Skip to main content
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.
For a bidirectional setup that keeps HubSpot deal stages, Flex quotes, and Soundcheck gig status in lockstep, see the HubSpot ↔ Flex pipeline (coming soon). It builds on the same signed-webhook foundation.

​
Endpoint

Send sync requests to:
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: 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:
Generate the digest from the raw request body using N8N_CRM_SYNC_SECRET.
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.
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.

Customers

Synced customer records appear in the customer directory.

Venues

Synced venues can be saved and reused on gigs.

Leads

Use public lead intake for inquiries that should start as pipeline records.