--- title: "Supabase + HubSpot: real-time two-way sync | Stacksync" description: "Real-time two-way sync between Supabase and HubSpot. Field mapping, row-level audit, and no backend to maintain." canonical: https://www.stacksync.com/supabase/hubspot last_modified: 2026-07-29 --- # Real-time two-way sync between Supabase and HubSpot Map fields once for two-way sync. Permitted Supabase row inserts reach HubSpot, and updates in HubSpot reach Supabase. [Sign up with Supabase](https://app.stacksync.com/) [Request a demo](https://www.stacksync.com/book-a-demo) | | | | --- | --- | | <200ms | p95 propagation | | $100 | Free credits | | SOC 2 | ISO 27001 · HIPAA | Trusted by fast-scaling teams, from YC startups to enterprise platform teams Gladia IDEXX MedPro Eko Ubicloud Vimeo Codility ACERTUS Truora Rinsed Meter Golden Pear Funding Capabilities ## Everything you need to sync HubSpot Connects over REST API (CRM v3), mapped field-by-field into Supabase, with row-level audit and no backend of your own to run. ### Two-way sync Every table maps to a HubSpot object both ways. Insert a row in Supabase and it lands in HubSpot; update a record there and Supabase reflects it back. ### Live, not batched Records: incremental near-real-time change tracking. Changes land in Supabase in milliseconds, not on the next polling cycle. | | | | --- | --- | | Contact | Two-way synced | | Company | Two-way synced | | Deal | Two-way synced | ### Every object, standard or custom Any object the API exposes can be mapped into Supabase, with schema discovery doing the field-matching for you. Use cases ## What teams ship first Patterns a two-person team can ship in a week. Any table in Supabase maps to any object in HubSpot. Real-time ### Two-way sync Changes in HubSpot instantly reflect in Supabase, and back. No stale data, no manual imports. Two-way sync of Contacts, Companies, and Deals between HubSpot and Supabase, so product and data teams work on CRM data in SQL. Push signup and usage events from your Supabase database into HubSpot contact properties to drive lifecycle marketing segmentation. Write lead and account scores computed in Supabase back onto HubSpot properties on a schedule or in near real time. Sync HubSpot Tickets into Supabase to unify service reporting with the rest of your application data. ## Why builders sync **Supabase and HubSpot** ### Ship without a backend No ETL jobs or sync scripts to maintain. Map Supabase tables to Contact and Company once, and every write stays in sync automatically. ### Every write moves both ways Changes in Supabase reach HubSpot in real time, and back. contact, company and deal stay consistent everywhere they live. ### Built to run in production Your Supabase write-ahead log is read directly, while HubSpot changes are picked up instantly, no polling delays or extra load. How it works ## Four steps, and no backend to maintain 01 ### Connect OAuth your project and the system. Schemas read automatically. 02 ### Map Tables to objects, fields to fields. Transforms run inline. 03 ### Sync Historical backfill, then continuous CDC both ways. 04 ### Monitor Row-level logs, latency and one-click replay. ## Sync Supabase with HubSpot from React One client, the same auth as your Supabase project. If you know the Supabase client, you already know this one. [Read the docs](https://docs.stacksync.com/) ``` import { createClient } from '@stacksync/client'const stacksync = createClient( process.env.SUPABASE_URL, process.env.STACKSYNC_API_KEY)export default function Deals() { const [deals, setDeals] = useState([]) useEffect(() => { stacksync.from('deals').select('*') .then(({ data }) => setDeals(data)) }, []) return } ``` ``` import { createClient } from '@stacksync/client'export async function POST(request) { const stacksync = createClient( process.env.SUPABASE_URL, process.env.STACKSYNC_API_KEY ) const { id, stage } = await request.json() // writes Supabase, propagates to HubSpot const { data } = await stacksync .from('deals') .update({ stage }) .eq('id', id) return Response.json(data)} ``` ``` from stacksync import create_clientstacksync = create_client( os.environ['SUPABASE_URL'], os.environ['STACKSYNC_API_KEY'])# one write, both systemsstacksync.table('deals').update( {'stage': 'won', 'amount': 48000}).eq('id', 'd_10427').execute()for row in stacksync.logs('deals').recent(): print(row['system'], row['latency_ms']) ``` ``` import { createClient } from '@stacksync/client'Deno.serve(async (req) => { const stacksync = createClient( Deno.env.get('SUPABASE_URL'), Deno.env.get('STACKSYNC_API_KEY') ) const { record } = await req.json() await stacksync.from('accounts').upsert({ id: record.id, owner: record.owner_email }) return new Response('ok')}) ``` ``` // claude_desktop_config.json{ "mcpServers": { "stacksync": { "command": "npx", "args": ["-y", "@stacksync/mcp"], "env": { "STACKSYNC_API_KEY": "sk_live_...", "SUPABASE_URL": "https://xyz.supabase.co" } } }}// your agent now reads and writes// every connected system of record ``` ``` -- Supabase stays the source of truthupdate deals set stage = 'won', amount = 48000 where id = 'd_10427';-- Stacksync picks up the change via CDC-- and writes it to every mapped systemselect system, object_id, latency_ms, status from stacksync.write_log where table_name = 'deals' order by created_at desc limit 10; ``` Pricing ## Free for Supabase builders Normally $1,000/mo. Yours at $0 during launch week. Launch week: 10,000 accounts only Supabase Connect $1,000 $0 / month Plus $100 in sync credits on the house. No card, no sales call, the same self-serve start you got with Supabase. 7,840 of 10,000 claimed 2,160 left [Claim my $100 in credits](https://app.stacksync.com/) [Talk to an engineer](https://www.stacksync.com/book-a-demo) Takes about 2 minutes · cancel in one click · export every mapping you build - 1 active two-way sync, real-time - AI agents and MCP servers - Workflows on any synced change - 3 collaborators - Migration review with a Stacksync engineer “We went from treating data integration as a necessary evil that consumed our best engineers to having it just work, reliably, at scale, in real-time.” Alex Marinov · VP of Technology, ACERTUS Trusted by 1,000+ teams · SOC 2 Type II · ISO 27001 Security ## Security teams trust Stacksync The integration layer is where compliance reviews stall. Row-level audit, residency and DPF certification for US, EU, UK and CH transfers, so procurement is a form, not a quarter. [Learn more about security](https://www.stacksync.com/security) | | | | --- | --- | | | SOC 2 Type II | | ISO 27001 | ISO 27001 | | HIPAA BAA | HIPAA BAA | | GDPR | GDPR | | CCPA | CCPA | | | DPF US-EU-UK-CH | → Security with benefits ### SSO & SCIM Okta, Azure and Google SSO, with SCIM provisioning. ### Alerts Sync issues to email, Slack, PagerDuty or WhatsApp, with retry and revert. ### Secure connections Connects to your systems your way. OAuth 2 SSH tunnelling SSL certificates IP whitelisting VPN gateway VPC peering FAQ ## Supabase + HubSpot FAQ ### How does Supabase sync with HubSpot? Stacksync watches your Supabase tables via CDC and HubSpot's API in real time. A permitted write on either side maps to fields on the other, with row-level logs for every change. ### Is the Supabase + HubSpot sync two-way? Yes. Changes made in Supabase propagate to HubSpot and vice versa. Field write controls preserve read-only values within the two-way sync. ### Do I need to write backend code to connect Supabase and HubSpot? No. Authenticate both systems, pick objects and fields to map, and enable the sync. Most integrations go live in minutes with no infrastructure to manage. ### Is my HubSpot and Supabase data secure in transit? Stacksync is SOC 2 Type II, ISO 27001, HIPAA, GDPR, CCPA and CSA STAR certified, and holds the EU-US, UK and Swiss Data Privacy Framework (DPF) certification. Data is encrypted in transit, with a zero-persistent-storage architecture: records aren't retained after a sync operation. ## Sync Supabase and HubSpot this afternoon [Sign up with Supabase](https://app.stacksync.com/) [Request a demo](https://www.stacksync.com/book-a-demo)