Skip to main content
The HubSpot ↔ Flex pipeline keeps three systems in lockstep: a deal in HubSpot, a quote in Flex, and a gig in Soundcheck. As a deal advances in HubSpot, a matching quote moves in Flex and the gig’s status moves in Soundcheck — and when the show happens and gets paid, Soundcheck’s closeout status feeds back the other way. Like n8n CRM sync, this runs through n8n, which owns every external API call. Soundcheck never calls HubSpot or Flex directly — it records state through signed webhooks and exposes its own state for n8n to read.
This pipeline is configured per organization as part of an n8n integration. Contact support to set it up.

​
Status mapping

The three systems share one canonical status map. A representative slice: A new inquiry in HubSpot opens a draft gig and a Flex quote; when the client commits, the gig goes Active. After the show, Soundcheck drives the back half — Active → Completed → Settled — and the pipeline propagates the close back to HubSpot.

​
Direction of flow

Inbound (CRM → Soundcheck)

A deal-stage or quote-status change in HubSpot/Flex is normalized by n8n and posted to Soundcheck through a signed webhook, which advances the gig’s status.

Outbound (Soundcheck → CRM)

Soundcheck-driven transitions — confirming, completing, and settling a gig — are read by n8n and pushed to Flex and HubSpot so the deal and quote close.

​
Why n8n owns the external calls

Keeping HubSpot and Flex behind n8n means the integration logic — auth, rate limits, retries, field mapping — lives in one place you can change without touching Soundcheck. Soundcheck stays the system of record for the gig itself and trusts only signed requests for the right organization.

n8n CRM sync

The signed-webhook foundation this builds on.

Event lifecycle

How a gig’s status moves.

Closeout

Completed and settled, the back half of the map.