Can the HubSpot adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your HubSpot tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
What happens if HubSpot changes their API after we go live?
Our SRE team monitors HubSpot change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
Is this a packaged HubSpot connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for San Francisco, California. After go-live, the HubSpot adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
How long does the HubSpot integration take to ship?
Our standard window is thirty days from signed scope to live HubSpot adapter in production, plus a one-week monitored stabilization phase. For San Francisco, California, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The HubSpot adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.