--- title: Provisioning HubSpot with PingOne description: Provision HubSpot in PingOne. component: pingone page_id: pingone:integrations:p1_provisioning_connection_hubspot canonical_url: https://docs.pingidentity.com/pingone/integrations/p1_provisioning_connection_hubspot.html llms_txt: https://docs.pingidentity.com/pingone/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: July 8, 2026 section_ids: provisioning-capabilities: Provisioning capabilities before-you-begin: Before you begin steps: Steps validation: Validation hubspot-directory-attributes: Hubspot directory attributes --- # Provisioning HubSpot with PingOne HubSpot supports user data management through PingOne provisioning. By using the HubSpot connection in PingOne, you can synchronize users between HubSpot and PingOne. ## Provisioning capabilities The following table summarizes the inbound and outbound provisioning capabilities for each resource type: | Resource | Capability | Description | Inbound | Outbound | | ---------- | -------------- | ------------------------------------------------------------ | ------- | -------- | | User | Create | Generates a new user record in the destination. | Yes | Yes | | | Read | Retrieves or polls user attributes for synchronization. | Yes | Yes | | | Update | Modifies existing attributes, such as `first name`. | Yes | Yes | | | Delete | Deletes a user or temporarily suspends an account. | Yes | Yes | | Group | Create | Provisions a new group in the target application. | No | No | | | Rename | Updates the display name or identifier of an existing group. | No | No | | | Delete | Removes a group from the target application. | No | No | | Membership | Add and remove | Adds or removes users from groups. | No | No | ## Before you begin Make sure that you have: * A HubSpot account. Learn more in [Set up your HubSpot account](https://knowledge.hubspot.com/get-started/set-up-your-account) in the HubSpot documentation. * The following credentials from your HubSpot account: * **Client Id** * **Client Secret** * **Refresh Token** * Users created and assigned to a group specifically for HubSpot provisioning in PingOne. Learn more in [Adding a user in PingOne](../directory/p1_adduser.html) and [Managing groups](../directory/p1_managing_groups.html). ## Steps 1. Create a HubSpot connection: 1. In the PingOne admin console, go to **Integrations > Provisioning**. 2. Click **[icon: plus, set=fa]**and then click **New Connection**. 3. Click **Select** for **Identity Store**. 4. Click **Select** for the **HubSpot** connection, and click **Next**. 5. Enter a **Name** and **Description** for this provisioning connection. 6. Click **Next**. 7. In the **Configure Authentication** section, select **OAUTH** for the **Authentication Method** and enter the following:: | Field | Example | | ----------------- | -------------------------------------- | | **Client ID** | `86c4cc4f-9f9e-4db9-abc5-f8b48a0b1372` | | **Client Secret** | `2e4e176d-48b3-4fe3-b82c-e878c151e32b` | | **Refresh Token** | `na2-b10d-8b23-4daa-86ba-8d84056dc470` | 8. Click **Next**. 9. In the **User Actions** section, select the following as needed: | Field | Description | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Enable users creation** | Creates a user in the target identity store when the user is created in the source identity store. | | **Enable users updation** | Updates user attributes in the target identity store when the user is updated in the source identity store. | | **Enable users deprovision** | Deprovisions a user in the target identity store when the user is deprovisioned in the source identity store. If you select **Enable users deprovision**, the following options appear:- **Remove Action**: To remove a user in the target identity store when the user is deleted in the source identity store, select **Delete**. - **Deprovision on rule deletion**: Deprovisions users if the associated provisioning rule is deleted. | 10. Click **Save**. 11. To enable the connection, click the toggle at the top of the details panel to the right (blue). | | | | - | ------------------------------------------------------------------------- | | | You can disable the connection by clicking the toggle to the left (gray). | 2. Create an [inbound](p1_create_provisioning_rule_inbound.html) or [outbound](p1_create_provisioning_rule_outbound.html) rule and select the existing HubSpot connection as the target or source. You can optionally add [attribute mappings](#hubspot-directory-attributes). Use the following inbound mapping examples for the HubSpot rule configuration: | HubSpot | PingOne Directory | | ----------- | ----------------- | | `true` | `Enabled` | | `city` | `Locality` | | `lastname` | `Family Name` | | `firstname` | `Given Name` | | `email` | `Username` | Use the following outbound mapping examples for the HubSpot rule configuration: | PingOne Directory | HubSpot | | ----------------- | ----------- | | `Username` | `email` | | `Family Name` | `lastname` | | `Given Name` | `firstName` | ## Validation * View the [sync status](p1_view_sync_status.html) to confirm users and groups are successfully provisioned to Hubspot and to check for errors. * Review [sync summary examples](p1_outbound_group_provisioning_sync_summary_examples.html) to help interpret your results. ## Hubspot directory attributes The following table lists common Hubspot attributes that can be mapped for user provisioning: | PingOne Attribute | Description | | ----------------- | --------------------------------------------------------------- | | `emails` | The user email attribute used for synchronization and matching. | | `firstName` | The user's given name. | | `lastName` | The user's family name. | | `City` | The user's locality or city value. |