Skip to main content
Coming soon: The HubSpot and Flex Rental Solutions connection isn’t generally available yet. We’ll announce it in the changelog when it launches.
Once available, the HubSpot ↔ Flex pipeline will keep three systems aligned: a deal in HubSpot, a quote in Flex, and a gig in Soundcheck. As a deal advances in HubSpot, a matching quote will move in Flex and the gig’s status will move in Soundcheck. When the show happens and gets paid, Soundcheck’s closeout status will feed back the other way. Like n8n CRM sync, the status sync will run through n8n, which owns every external API call. Soundcheck will never call HubSpot or Flex directly for the status mapping below. It will record state through signed webhooks and expose its own state for n8n to read.
This pipeline will be configured per organization as part of an n8n integration. Contact support to ask about early access.

​
Connect HubSpot and Flex

Separately from the n8n sync, an owner or admin will be able to connect HubSpot and Flex directly from Settings → Connected apps → Integrations: click the HubSpot or Flex Rental Solutions card, enter an API key (and, optionally, your HubSpot Portal ID or Flex Account ID), and click Save Connection. Organizations with the pipeline set up will also get a Sync section on Settings → Connected apps → Integrations. Its Sync now button will trigger the HubSpot ↔ Flex quote sync on demand, and a table below it will list the matched HubSpot deal / Flex quote pairs the pipeline has created.

​
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 puts integration logic (auth, rate limits, retries, field mapping) 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.