--- title: "HubSpot Supabase sync for construction customer portals" description: "Build construction customer portals around stable company, site and request records without confusing sync with user authorization." canonical: https://www.stacksync.com/blog/hubspot-supabase-for-construction-service-portals-customers-sites-and-request-status last_modified: 2026-09-18 --- # HubSpot–Supabase for Construction Service Portals: Customers, Sites, and Request Status > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Build construction customer portals around stable company, site and request records without confusing sync with user authorization. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 4 min read DATA ENGINEERING ## The operating decision HubSpot–Supabase two-way sync can keep CRM context and a construction service portal aligned. Model customers, physical sites and service requests separately, then decide which fields the portal may propose and which HubSpot fields it may display. The portal also needs its own authorization model: syncing a company record does not grant a logged-in user access to that company's jobs. Apply database grants and row policies for the actual customer-to-site relationships. Explore the complete [construction services and installation integration and automation hub](https://www.stacksync.com/industry/construction) for the systems and processes around this guide. ![Summary card: HubSpot Supabase sync for construction customer portals](https://www.stacksync.com/images/blog-highlights/icp-hubspot-supabase-for-construction-service-portals-customers-sites-and-request-status.webp) ## What this looks like in construction services and installation A maintenance contractor offers a portal for facility managers to submit requests and see progress. One manager oversees three buildings, while another may see only one. HubSpot stores the relationship and account owner; Supabase stores portal requests and memberships. A customer changes a contact phone number, then asks for after-hours access. The phone update may be permitted to synchronize, but an access instruction should remain attached to the specific site and request. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Customer cross-reference | CRM administration | Join HubSpot company IDs to stable portal customer IDs. | | Site membership | Portal administrator | Authorize each user for explicit sites; do not infer access from a shared email domain. | | Service request | Customer service | Retain request ID, originating user, site and received time. | | Customer-visible status | Operations | Publish a controlled status rather than exposing internal dispatch or finance notes. | ![Record ownership diagram: Customer cross-reference, Site membership, Service request](https://www.stacksync.com/images/blog-diagrams/icp-hubspot-supabase-for-construction-service-portals-customers-sites-and-request-status.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Design the customer and site relationships Create a model that can express one customer with many sites and one user with access to selected sites. Keep the CRM association and portal membership separate. The former describes a business relationship; the latter determines what an authenticated person can read or change. 2. 02 Use a narrow write surface Decide which portal inputs may update mapped CRM fields. A phone correction and a new service request have different validation needs from a billing-address change. Store requested changes separately when a customer-facing edit needs staff approval, and keep the approved value visible until that review finishes. 3. 03 Connect with supported database settings Follow Stacksync's current Supabase connection instructions, including its documented IPv4-compatible pooler requirement. Select the intended tables and verify their identifiers. Keep connection credentials on the server side; the browser should use the portal's normal authenticated access rather than the integration account. 4. 04 Define status translation Map internal request states to customer-friendly language. Scheduled, awaiting customer access, completed by technician, and approved for billing should remain distinguishable. A status should include its update time and, where useful, the customer's next action. Do not publish internal cost, margin, or dispatch commentary by default. 5. 05 Test access and replay together Sign in as users from two unrelated customers and try reading and editing each other's requests. Separately replay a portal submission and a CRM status change to check for duplicate requests and loops. Successful synchronization and successful authorization are two independent acceptance checks. ![5-step operating sequence: HubSpot Supabase sync for construction customer portals](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-hubspot-supabase-for-construction-service-portals-customers-sites-and-request-status.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Customer belongs to multiple properties Use explicit site memberships and test each assignment; a company-level association alone may be too broad. ### HubSpot record merges Update the cross-reference through a reviewed merge path and preserve the existing portal request history. ### Portal displays a delayed update Show the last verified status time and avoid announcing a schedule change before operations confirms it. ## What to verify before expanding - A user can access only their approved customers and sites. - A repeated submission keeps one service request identifier. - Internal margin and dispatch notes never appear in the portal. - A membership removal prevents further access under the tested session policy. ## Connect this process to the rest of your operation [Explore Stacksync two-way sync](https://www.stacksync.com/two-way-sync) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real customer cross-reference example and the exception your team handles most often, for example customer belongs to multiple properties. - [Construction Company Acquisitions: Unify Customer and Job IDs Across Branch Systems](https://www.stacksync.com/blog/construction-company-acquisitions-unify-customer-and-job-ids-across-branch-systems) - [Construction Job-Cost Visibility: Define Ownership Across CRM, ERP, and Field Records](https://www.stacksync.com/blog/construction-job-cost-visibility-define-ownership-across-crm-erp-and-field-records) - [Approved Change Order to Billing Queue: Automating Construction Service Handoffs](https://www.stacksync.com/blog/approved-change-order-to-billing-queue-automating-construction-service-handoffs) - [How to Sync HubSpot and Supabase in minutes with Stacksync](https://www.stacksync.com/blog/how-to-sync-hubspot-and-supabase-in-minutes-with-stacksync) - [Real-Time HubSpot Database Integration and Salesforce Sync with Stacksync](https://www.stacksync.com/blog/real-time-hubspot-database-integration-and-salesforce-sync-with-stacksync) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync HubSpot connector and object support](https://docs.stacksync.com/two-way-sync/connectors/hubspot) - [Stacksync Supabase connection setup](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/supabase) - [Supabase row level security](https://supabase.com/docs/guides/database/postgres/row-level-security) FAQ ## Frequently asked questions Does syncing HubSpot contacts create portal users? No. CRM records and authentication identities serve different purposes. Create and authorize portal users through the portal's own access process, then link them to approved business records. Can customers update job status? Usually they should submit a response or request, while operations owns the official job status. Map the exact customer action you intend to allow instead of granting broad edit access. What makes this more than a nightly export? The portal and CRM can exchange permitted record changes through an ongoing connection. The scope still needs stable identifiers, ownership rules, and a tested way to handle delayed or rejected updates. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [integration HubSpot and Supabase integration](https://www.stacksync.com/integrations/hubspot-and-supabase) - [connector HubSpot integrations](https://www.stacksync.com/connectors/hubspot) - [connector Supabase integrations](https://www.stacksync.com/connectors/supabase) - [platform Two-way sync](https://www.stacksync.com/two-way-sync) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Prefab Dealer and Contractor Portals: Align HubSpot Buyer Records With Supabase Project Access 5 min read read](https://www.stacksync.com/blog/prefab-dealer-and-contractor-portals-align-hubspot-buyer-records-with-supabase-project-access) [Data engineering Solar Customer Portals: Connect HubSpot Milestones With Supabase Customer Access 5 min read read](https://www.stacksync.com/blog/solar-customer-portals-connect-hubspot-milestones-with-supabase-customer-access) [App tips How to Sync HubSpot and Supabase in minutes with Stacksync 3 min read read](https://www.stacksync.com/blog/how-to-sync-hubspot-and-supabase-in-minutes-with-stacksync) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)