Supported HubSpot Objects

Overview

The Rapidi HubSpot connection is built on a HubSpot app with a specific set of OAuth scopes. These scopes determine which HubSpot objects (standard and custom) the connection is technically capable of reading or writing.

Having a scope enabled on the app is not enough on its own to guarantee an object can be used. The HubSpot user who authorizes the connection also needs proper access to that object in their own HubSpot instance.

Scopes by Object

Companies

  • crm.objects.companies.read
  • crm.objects.companies.write
  • crm.schemas.companies.read

Contacts

  • crm.objects.contacts.read
  • crm.objects.contacts.write
  • crm.schemas.contacts.read

Owners

  • crm.objects.owners.read

Users

  • crm.objects.users.read
  • settings.users.read

Conversations

  • conversations.read
  • conversations.write

Lists

  • crm.lists.read
  • crm.lists.write

Deals

  • crm.objects.deals.read
  • crm.objects.deals.write
  • crm.schemas.deals.read

Leads

  • crm.objects.leads.read
  • crm.objects.leads.write

Forecasts

  • crm.objects.forecasts.read

Line Items

  • crm.objects.line_items.read
  • crm.objects.line_items.write
  • crm.schemas.line_items.read

Products

  • crm.objects.products.read
  • crm.objects.products.write

Quotes

  • crm.objects.quotes.read
  • crm.objects.quotes.write
  • crm.schemas.quotes.read

Invoices

  • crm.objects.invoices.read
  • crm.objects.invoices.write
  • crm.schemas.invoices.read
  • crm.schemas.invoices.write

Orders

  • crm.objects.orders.read
  • crm.objects.orders.write
  • crm.pipelines.orders.read
  • crm.pipelines.orders.write
  • crm.schemas.orders.read

Carts

  • crm.objects.carts.read
  • crm.objects.carts.write
  • crm.schemas.carts.read

Commerce Payments

  • crm.objects.commercepayments.read
  • crm.schemas.commercepayments.read

Subscriptions

  • crm.objects.subscriptions.read
  • crm.objects.subscriptions.write
  • crm.schemas.subscriptions.read

Currencies

  • settings.currencies.read
  • settings.currencies.write

E-commerce

  • e-commerce

Tickets

  • tickets

Feedback Submissions

  • crm.objects.feedback_submissions.read

Services

  • crm.objects.services.read
  • crm.objects.services.write
  • crm.schemas.services.read

Appointments

  • crm.objects.appointments.read
  • crm.objects.appointments.write
  • crm.schemas.appointments.read

Courses

  • crm.objects.courses.read
  • crm.objects.courses.write
  • crm.schemas.courses.read

Projects

  • crm.objects.projects.read
  • crm.objects.projects.write
  • crm.schemas.projects.read

Marketing Events

  • crm.objects.marketing_events.read
  • crm.objects.marketing_events.write

Goals

  • crm.objects.goals.read
  • crm.objects.goals.write

Custom Objects

  • crm.objects.custom.read
  • crm.objects.custom.write
  • crm.schemas.custom.read

Files

  • files

Permissions Requirement

Having a scope available on the app does not guarantee that data can be read from or written to that object.

The HubSpot user who authorized the connection must also have object-level permission for that object in their own HubSpot instance. HubSpot enforces this on top of the app's scopes: even if the connection requests, for example, crm.objects.companies.read, the integration will fail to retrieve companies if the authorizing user does not personally have access to the Companies object in HubSpot.

In short, two conditions must both be true for an object to work:

  1. The scope for that object is included in the Rapidi HubSpot app.
  2. The authorizing user has permission to that object in their HubSpot account.

Requesting a New Object

If a customer needs an object that is not currently part of the app's scope list:

  1. The customer (or the relevant HubSpot admin) must first grant the authorizing user proper access/permissions to that object in HubSpot.
  2. The customer or consultant should then reach out to Rapidi support so the corresponding scope can be added to the app's scope list and therefore made available in the Rapidi HubSpot connection.