HubSpot
A HubSpot account where you can authorize CRM contact and list access
Ownership and availability
You retain control of the HubSpot account and CRM records. Obelo manages the OAuth app and encrypts the resulting refresh credential server-side.
Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.
Before you connect
- A HubSpot user who can install or authorize connected apps for the target account
- The contacts and lists Obelo should use are available in that HubSpot account
- An Obelo workspace owner or admin completes authorization
Connect an existing account
- Open the provider in Settings → Integrations for the intended website.
- Choose the HubSpot account that belongs to this company
- Review and approve Obelo's contact and list permissions on HubSpot
- Return to Obelo; the account identity is verified before CRM workflows are enabled
If you need a new resource
- Create a free HubSpot CRM account for the company
- Import or add the contacts and lists your marketing workflow should use
- Invite the teammate who will authorize the Obelo connection
Permissions to check
- Contact read/write lets approved Obelo workflows synchronize CRM contacts
- List read/write lets Obelo read, create, and maintain the contact segments used by those workflows
Verify and troubleshoot
Once the HubSpot account and contact data are ready, return and connect it to this website.
HubSpot did not return an eligible account. Switch to a HubSpot user with app-install access or ask an account administrator to authorize Obelo.
Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.
Disconnect or change access
Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.
Something unclear or out of date?
Suggest a correction