What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for El Paso, Texas. 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.
Do we own the integration code at the end?
Yes. The Connectify HubSpot adapter ships with full source escrow rights — at any point you can request a snapshot of the code, configuration, and runbooks. We prefer you stay on our managed runtime, but you are never locked in.
Does it work with our existing HubSpot licenses?
Yes — the adapter rides on top of your existing HubSpot subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
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.
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.
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 El Paso, Texas, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.