Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Communications / Hubspot / Conversations Custom Channels
Conversations Custom Channels logo

HubSpot Conversations Custom Channels

Browse all Hubspot APIs
42
AI ReadinessFoundational (D-)42/100
See full scorecard
Official vendor OpenAPI document · agent-readyCommunicationsChat Messagingoauth2, apiKey13 EndpointsREST

For Agents

Register and operate custom messaging channels inside HubSpot conversations, including publishing messages and managing channel accounts. Useful for agents bridging an external chat platform into HubSpot.

Use for: Create a custom conversation channel for an external chat platform, Publish an inbound message from an external messenger into HubSpot, Register a channel account when a user installs the integration, Update the state of a previously published custom-channel message

Not supported: Does not read native HubSpot inbox threads, identify website visitors, or send transactional email - use for registering and operating custom messaging channels only.

The HubSpot Conversations Custom Channels API lets developers register external messaging surfaces - such as a proprietary chat platform or third-party messenger - as channels inside HubSpot's shared inbox. It supports creating and updating channels and channel accounts, publishing inbound messages, updating message state, and managing channel account staging tokens used for installation flows. With this API a custom channel can behave like native HubSpot conversations channels.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Conversations Custom Channels to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Conversations Custom Channels, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-conversations-custom-channels" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-conversations-custom-channels" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Conversations Custom Channels API.

Create a custom channel that surfaces in HubSpot's shared inbox

Register channel accounts representing connected end users or threads

Publish inbound messages from the external platform into HubSpot

Update existing custom channel records and their message metadata

Manage channel account staging tokens used during install handshakes

Archive a custom channel when the integration is removed

Query channel accounts attached to a specific custom channel

Use Cases

Patterns agents use Conversations Custom Channels API for, with concrete tasks.

★ Bridging an External Chat into HubSpot

A SaaS vendor with its own chat product surfaces conversations inside HubSpot Service Hub by registering a custom channel and publishing each new external message into HubSpot. POST /conversations/v3/custom-channels/ creates the channel; POST /conversations/v3/custom-channels/{channelId}/messages publishes inbound messages so they appear in the shared inbox.

POST /conversations/v3/custom-channels/ once at install time to create the channel, then POST /conversations/v3/custom-channels/{channelId}/messages for each new inbound message.

Per-Account Channel Provisioning

Provision a separate channel account whenever a HubSpot customer connects their workspace in the external platform. The API supports creating, updating, and querying channel accounts, plus rotating staging tokens used during the OAuth-style install handshake.

On install completion, POST /conversations/v3/custom-channels/{channelId}/channel-accounts with the connected workspace identifiers.

Sync Read and Delivered State

Mirror external read or delivered receipts back into HubSpot so the inbox view stays in sync with the source platform. PATCH /conversations/v3/custom-channels/{channelId}/messages/{messageId} updates a published message's state without re-publishing the body.

On a read-receipt event, PATCH /conversations/v3/custom-channels/{channelId}/messages/{messageId} setting the new status.

Agent-Driven External Bridge

Use Jentic to let an integration agent register channels and publish messages on behalf of customers without bespoke HubSpot client code. The HubSpot OAuth token is held in your Jentic One instance, and the agent invokes channel operations by intent rather than constructing requests by hand.

Use Jentic search 'publish a message into a HubSpot custom channel', load the POST /conversations/v3/custom-channels/{channelId}/messages schema, and execute with the channelId and message payload.

Key Endpoints

13 endpoints — the hubspot conversations custom channels api lets developers register external messaging surfaces - such as a proprietary chat platform or third-party messenger - as channels inside hubspot's shared inbox.

METHOD

PATH

DESCRIPTION

GET

/conversations/v3/custom-channels/

List all custom channels for the app

POST

/conversations/v3/custom-channels/

Create a custom channel

PATCH

/conversations/v3/custom-channels/{channelId}

Update a custom channel

POST

/conversations/v3/custom-channels/{channelId}/messages

Publish a message

PATCH

/conversations/v3/custom-channels/{channelId}/messages/{messageId}

Update a published message

POST

/conversations/v3/custom-channels/{channelId}/channel-accounts

Create a channel account

DELETE

/conversations/v3/custom-channels/{channelId}

Archive a custom channel

GET

/conversations/v3/custom-channels/

List all custom channels for the app

POST

/conversations/v3/custom-channels/

Create a custom channel

PATCH

/conversations/v3/custom-channels/{channelId}

Update a custom channel

POST

/conversations/v3/custom-channels/{channelId}/messages

Publish a message

PATCH

/conversations/v3/custom-channels/{channelId}/messages/{messageId}

Update a published message

POST

/conversations/v3/custom-channels/{channelId}/channel-accounts

Create a channel account

DELETE

/conversations/v3/custom-channels/{channelId}

Archive a custom channel

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

C

Conversations Custom Channels

- Foundational (D-)
42/100
62
Foundational Compliance
54
Developer Experience & Jentic Compatibility
20
AI-Readiness & Agent Experience
94
Agent Usability
52
Security
74
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
62

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4
89%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

54

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
3%

Example Density

How richly the API is illustrated with examples.

62%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

20

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
14%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

65%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

52

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
52%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

74

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring HubSpot Custom Channels by hand means learning its OAuth2 access token or private app token auth, targeting the api.hubapi.com host, and registering channels and channel accounts yourself. Through Jentic you install once, import HubSpot Custom Channels from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Custom Channels API puts the channel id in the URL path (/conversations/v3/custom-channels/{channelId}), so a rule can pin your agent to one channel for updating it and publishing messages. You choose the operations it may call, so deleting a channel is not included unless you add it.

Credential isolation

Your HubSpot access token or private app token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a HubSpot custom channel' or 'publish a message into HubSpot', and Jentic returns the matching Custom Channels operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot Conversations Inbox & Messages

→

Read and reply within the HubSpot inboxes that custom channels feed into.

Use Conversations-conversationsInboxMessages when the agent needs to read threads or send replies once a custom channel has delivered a message.

Complementary

HubSpot Visitor Identification

→

Identify authenticated visitors as the actor on inbound chat messages.

Pick Conversations-visitorIdentification when the agent needs to attach a verified identity to messages before publishing them via the custom channel.

Complementary

HubSpot OAuth

→

Manage OAuth tokens for the app that owns the custom channel.

Use Auth-oauth when the agent needs to refresh OAuth tokens that authorise the custom channel app.

FAQs

Specific to using Conversations Custom Channels API through Jentic.

What authentication does the HubSpot Custom Channels API use?

OAuth 2.0 authorization code flow, a private app token in the `private-app` header, or developer hapikey as a query parameter. Through Jentic, credentials are stored encrypted in the vault and the agent only sees a scoped execution token.

Can I publish a message from an external platform into HubSpot's inbox?

Yes. POST /conversations/v3/custom-channels/{channelId}/messages publishes a message into the channel so it appears in the shared inbox alongside native conversation channels.

What are the rate limits for the Custom Channels API?

Standard HubSpot API limits apply - roughly 100 requests per 10 seconds per OAuth app and daily caps on paid tiers. Spread message publication evenly to stay below the per-second ceiling.

How do I register a custom channel through Jentic?

Search Jentic for `create a HubSpot custom channel`, load the POST /conversations/v3/custom-channels/ schema, and execute with the channel name and webhook configuration. Install with `pip install jentic` and authenticate using `JENTIC_AGENT_API_KEY`.

Can I update the state of a previously published message?

Yes. PATCH /conversations/v3/custom-channels/{channelId}/messages/{messageId} updates an already-published message - useful for syncing read receipts or delivery status from the source platform.

Can I limit what my agent is allowed to do with the HubSpot Custom Channels API?

Yes. Because you run Jentic One yourself, your own rules decide which Custom Channels operations and credentials the agent may use. Since the channel id lives in the URL path (/conversations/v3/custom-channels/{channelId}), you can pin the agent to a single channel and allow only the calls you choose, such as publishing messages or updating a message's state. Destructive operations like archiving a channel with DELETE /conversations/v3/custom-channels/{channelId} are excluded unless you explicitly add them.

GET STARTED

Start building with Conversations Custom Channels API

Explore with Jentic One
View OpenAPI Document