---
title: "HubSpot integration"
description: "Which objects, actions and permissions, and where approval applies when a workflow uses HubSpot."
source_name: "Gen8"
source_url: "https://gen8.app/en/integraties/hubspot/"
site_home: "https://gen8.app/"
source_description: "Managed AI service for SMEs. We set up, connect and manage; you stay in control."
locale: "en"
copyright: "© 2026 Gen8 VOF · Dutch Chamber of Commerce 92978789 · Delft"
published_at: "2026-09-20T16:40:03.976Z"
modified_at: "2026-10-21T18:16:47.281Z"
---

# HubSpot integration

## HubSpot as source and destination, with approval in between

Gen8 has its own HubSpot integration. A workflow reads contacts, deals, activities and tickets for context, and proposes changes a person approves before they reach the CRM.

[Book an introduction](<https://gen8.app/en/contact/>)

- Permissions stay in force
- EU hosting
- Visible approval

September 20, 2026 · Sales

**Route:** native  
**Components:** HubSpot CRM: contacts, deals, activities \(notes, tasks\), tickets, owners, object associations

## What the integration can do

As a **source**: a workflow retrieves contact or deal context before assessing email, summarizing a meeting or answering a customer question. Who is this, what is underway, who owns it?

As a **destination**: a workflow proposes a note, task, deal stage or contact field. The proposal shows the difference from the current value; it is written only after approval.

- Read, create and update contacts
- Read and update deals, including stage
- Read and create activities \(notes and tasks\)
- Read and create tickets
- Look up owners and associate objects

## What you can *automate* with this

A few examples of work you can hand over through this integration. We work out what fits your organisation together during scoping.

### Context before replying

Before assessing an email or answering a customer question, the workflow retrieves the contact, current deals and owner.

### Notes and tasks after customer contact

After a conversation or email, a note and task are prepared as proposals. The owner approves, edits or rejects.

### A deal stage that stays current

If a deal lags behind events, the workflow proposes a new stage with the difference visible.

### New contacts without retyping

Someone not yet in HubSpot is proposed as a new contact and linked to the right deal.

### Customer questions as tickets

A customer question is prepared as a ticket for the right owner.

### An overview from your CRM

Current deals and open tasks listed from HubSpot without changing anything.

## Does this work look familiar? Or does your process run on another system?

Tell us which work you want to hand over. We help you think through the integration and route, even if your system is not listed here yet.

[Book an introduction](<https://gen8.app/en/contact/>)

## What access is needed

The integration uses a connection configured by an administrator in Gen8. The workflow receives only permissions needed for the selected actions: a read-only workflow requests no write permissions.

## Where approval is required

By default, every write is a proposal. The record owner sees the proposed difference and approves, edits or rejects. Read-only workflows \(reporting, enrichment for context\) need no approval step. We configure automatic writing without intervention only for fields where an error is minor and reversible, always with logging.

## What we can demonstrate

The HubSpot integration is Gen8's own, with tools for contacts, deals, activities, tickets, owners and associations.

gen8 · hubspotdone

Update a deal after customer contact

Plan01Sender matched to a contact and related deal

Action02Deal, owner and open activities read for context

Action03Note drafted and linked to the deal

Action04Deal stage change prepared with visible difference

Reflect05Stage change affects the forecast: presented to the owner

Proposal ready · awaiting deal owner approval

## Frequently asked questions

Can the workflow clean up duplicate contacts?

It can expose duplicates and missing fields and propose a merge. Merging itself is an approved action, never automatic.

Does this work with Salesforce or Pipedrive too?

Both have their own Gen8 integration with the same structure: reading for context, writing as a proposal with approval.

## Which systems do you use?

Tell us which process you want to connect. We explain which route fits, which permissions are needed and where people keep making decisions.

[Book an introduction](<https://gen8.app/en/contact/>)

- Reply within one business day
- No obligation