How to integrate HubSpot
Follow these steps in Evonx to connect HubSpot CRM objects and events to your application repository. Use this when deals, contacts, or tickets must sync without leaving GitHub-owned code.
Step-by-step
Choose sync direction
Decide which objects are source-of-truth in HubSpot vs your app before writing mappings.
Create a private app or OAuth app
Generate HubSpot credentials with least-privilege scopes for contacts, deals, or tickets.
Store secrets server-side
Keep tokens in environment config; never expose HubSpot secrets in client bundles.
Implement idempotent sync jobs
Upsert by HubSpot ID and external ID; log failures for retry without duplicates.
Handle HubSpot webhooks
Verify signatures and process property change events into your domain tables.
Preview and monitor
Test in a HubSpot sandbox, validate field maps in preview, then merge via pull request.
Outcome
HubSpot-connected application code with scoped auth, sync jobs, and webhook handling you can ship.
Related resources
FAQ
Private app vs OAuth for HubSpot?
Private apps suit single-portal internals. OAuth fits multi-tenant products where each customer connects their HubSpot.
What usually breaks first?
Field mapping drift and rate limits. Version your property maps and batch with backoff.
Can Evonx replace HubSpot?
No. This guide wires HubSpot into your repo. For a native CRM, use the CRM template and build pages.
Build production software with Evonx
Start from a template or connect an existing repository. Evonx helps you ship real applications with preview, evolution threads, and pull-request delivery—not disposable demos.