Reference · built on requestConnectorCRM & sales

HubSpot

Contacts, companies, deals, tickets, and activities from a HubSpot account, with webhooks when records change.

Request accessPricing ↗

About

HubSpot keeps marketing, sales, and service records in one account: contacts, companies, deals, tickets, and the calls, emails, meetings, and tasks logged against them. The CRM API exposes each as an object under /crm/v3/objects/, with batch, search, and association endpoints, and webhook subscriptions deliver CREATE, UPDATE, DELETE, and MERGE events per installed account.

An operator on Fibric reads those objects, notices what changed, and proposes a deal stage move, a ticket handoff, or a task. A person approves it in HubSpot's own terms, and the write happens once.

This is a reference listing. It documents what Fibric would read from HubSpot and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Contacts through GET /crm/v3/objects/contacts, by id or by email with idProperty=email, and batch read up to 100 per request
  • Deals through GET /crm/v3/objects/deals with dealname, dealstage, pipeline, amount, closedate, and hubspot_owner_id
  • Tickets through /crm/v3/objects/tickets with subject, hs_pipeline, and hs_pipeline_stage
  • Tasks through /crm/v3/objects/tasks with hs_timestamp, hs_task_subject, hs_task_status, and hubspot_owner_id
  • Webhook events CREATE, UPDATE, DELETE, MERGE, RESTORE, ASSOCIATION_ADDED, and ASSOCIATION_REMOVED for contacts, companies, deals, and tickets
  • Property history on a record through propertiesWithHistory, and associations between deals, contacts, and companies

Proposed actions

  • Target capability: propose a dealstage or closedate change through PATCH /crm/v3/objects/deals/{dealId}
  • Target capability: propose a contact property update, such as lifecyclestage, through PATCH /crm/v3/objects/contacts/{contactId}
  • Target capability: propose a task through POST /crm/v3/objects/tasks with a due date and hubspot_owner_id, associated to the deal
  • Target capability: propose a ticket stage change through PATCH /crm/v3/objects/tickets/{ticketId} once a person signs off

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hand a closed deal to onboarding

    When a deal reaches a closed-won stage, the operator assembles the handoff: contact, company, amount, and notes. A person approves the packet before it leaves sales.

    With Deal Handoff

  • Follow up on a proposal that went quiet

    Deals sitting in a proposal stage past a date you set are surfaced with the last email or call. The operator drafts the follow-up and a task for the owner.

    With Quote Follow-up

  • Route tickets with the deal in view

    Tickets are read alongside the contact and company they belong to. The operator proposes a priority and owner, using open deal value and lifecycle stage as context.

    With Ticket Triage

  • Spot accounts drifting toward churn

    Companies with falling engagement across tickets, emails, and meetings are listed with their open deals. The operator proposes a check-in for the account owner.

    With Churn Watch

Requirements

  • A HubSpot account and a user allowed to create a private app and grant its scopes
  • Scopes matched to the objects in use: crm.objects.contacts.read, crm.objects.deals.read, crm.objects.tickets.read, and write scopes for anything proposed
  • A reachable endpoint for webhook deliveries if you want events rather than scheduled reads
  • For an OAuth app distributed privately, an allowlist of at most 10 accounts
Authentication
A private app access token when one HubSpot account is involved, or OAuth 2.0 when the same app is installed on several accounts; scopes such as crm.objects.contacts.read and crm.objects.deals.write are declared up front.

Limits

  • Private apps: 100 requests per 10 seconds and 250,000 per day on Free and Starter; 190 per 10 seconds on Professional and Enterprise
  • Public OAuth apps: 110 requests per 10 seconds per installed account; the API limit increase add-on does not apply to them
  • Batch endpoints take at most 100 records per call, and the CRM Search API has its own stricter limits
  • Daily limits reset at midnight in the account's time zone setting

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request HubSpot ↗

Questions and answers

Does HubSpot push changes, or does the connector poll?
Webhook subscriptions deliver CREATE, UPDATE, DELETE, MERGE, and association events per installed account. Where no subscription is in place, the connector reads through the object endpoints on a schedule and uses propertiesWithHistory to see what moved.
Which authentication does the connector use?
A private app access token when one HubSpot account is involved. HubSpot requires OAuth for an app installed on more than one account. Scopes are named per object, for example crm.objects.deals.write or crm.objects.tickets.read.
How many requests can the connector make?
Private apps get 100 requests per 10 seconds on Free and Starter and 190 on Professional and Enterprise, with daily caps from 250,000 to 1,000,000. A 429 response signals the limit, and the connector backs off before retrying.
Ask about HubSpot

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with HubSpot through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy