HubSpot Conversations Inbox & Messages

Name: Conversations Inbox & Messages API
Brand: Conversations Inbox & Messages
Availability: InStock

✓ Official Vendor SpecCommunicationsChat Messagingoauth2, apiKey16 Endpoints

Install Jentic One Beta

Connect the Conversations Inbox & Messages to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Conversations Inbox & Messages, 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Inbox & Messages API.

List conversations inboxes connected to the HubSpot account

Retrieve a thread, its message history, and original message content

Send a reply message into an existing thread

GET STARTED

Start building with Conversations Inbox & Messages API

Explore with Jentic

View OpenAPI Document

For Agents

Read HubSpot conversation threads, send messages into existing threads, and manage inbox metadata across email and chat channels. Useful for agents triaging or responding to support conversations.

Use for: List all HubSpot conversation inboxes on this account, Retrieve the message history of a specific support thread, Send a reply into an existing conversation thread, Archive a closed support thread

Not supported: Does not configure custom channels, identify anonymous web visitors, or manage CRM contact records - use for HubSpot inbox thread and message operations only.

Use Cases

Patterns agents use Conversations Inbox & Messages API for, with concrete tasks.

★ AI Triage of Support Threads

Pull recent threads from a HubSpot Service Hub inbox, summarise each, and assign them to the right team member or send a templated first response. The Inbox & Messages API exposes thread listings, full message history, and a send-message endpoint, which is the full read-and-respond loop a triage agent needs.

GET /conversations/v3/conversations/threads, then for each unassigned thread GET its messages and POST /conversations/v3/conversations/threads/{threadId}/messages with a triage reply.

Conversation Archival and Audit

Export thread history for compliance or analytics by paging through threads and pulling original message content. The API returns each message's raw content via GET /conversations/v3/conversations/threads/{threadId}/messages/{messageId}/original-content, suitable for archival into a data warehouse.

Iterate threads via GET /conversations/v3/conversations/threads, fetch each thread's messages, and store the original-content payload to S3.

Multi-Channel Reply Bot

Build a reply bot that responds across the channels connected to a HubSpot inbox. The API exposes channels and channel accounts, and POST to a thread's messages endpoint sends a reply on the appropriate channel automatically based on the thread's origin.

On a webhook for a new thread, GET /conversations/v3/conversations/threads/{threadId}, generate a reply, and POST /conversations/v3/conversations/threads/{threadId}/messages.

Agent-Driven Inbox Operations

Wire a HubSpot inbox into an AI agent through Jentic so the agent can read threads, send replies, and archive resolved conversations. Jentic isolates the HubSpot OAuth token from the agent's reasoning context and exposes each operation by intent rather than by URL.

Use Jentic search 'send a reply into a HubSpot conversation thread', load the schema for POST /conversations/v3/conversations/threads/{threadId}/messages, and execute with the threadId and reply text.

Key Endpoints

16 endpoints — the hubspot conversations inbox & messages api exposes the shared inbox model that backs hubspot service hub conversations.

METHOD

PATH

DESCRIPTION

GET

/conversations/v3/conversations/inboxes

List conversations inboxes

GET

/conversations/v3/conversations/threads

List threads

GET

/conversations/v3/conversations/threads/{threadId}

Get a single thread

PATCH

/conversations/v3/conversations/threads/{threadId}

Update a thread

GET

/conversations/v3/conversations/threads/{threadId}/messages

Get message history for a thread

POST

/conversations/v3/conversations/threads/{threadId}/messages

Send a message to a thread

DELETE

/conversations/v3/conversations/threads/{threadId}

Archive a thread

GET

/conversations/v3/conversations/inboxes

List conversations inboxes

GET

/conversations/v3/conversations/threads

List threads

GET

/conversations/v3/conversations/threads/{threadId}

Get a single thread

PATCH

/conversations/v3/conversations/threads/{threadId}

Update a thread

GET

/conversations/v3/conversations/threads/{threadId}/messages

Get message history for a thread

Why Jentic?

Three things that make agents converge on Jentic-routed access.

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 'send a HubSpot message' or 'list HubSpot inbox threads', and Jentic returns the matching Conversations operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Conversations Inbox & Messages API through Jentic.

What authentication does the HubSpot Conversations Inbox & Messages API use?

OAuth 2.0 authorization code flow or a private app token in the `private-app-legacy` header. Jentic stores the credential encrypted and exposes only a scoped execution token to the agent.

Can I send a reply into an existing thread with this API?

Yes. POST /conversations/v3/conversations/threads/{threadId}/messages sends a message into the thread, routed automatically through the channel the thread originated on.

What are the rate limits for the Conversations API?

Standard HubSpot API limits apply - roughly 100 requests per 10 seconds per OAuth app and daily caps on paid tiers. For high-volume inbox polling, prefer webhooks and pull thread detail only when an event arrives.

How do I summarise a thread through Jentic?

Search Jentic for `get HubSpot thread messages`, load the schema for GET /conversations/v3/conversations/threads/{threadId}/messages, execute, and feed the message bodies into your LLM. Install with `pip install jentic` and authenticate using `JENTIC_AGENT_API_KEY`.

Does the API expose the original content of an email message in a thread?

Yes. GET /conversations/v3/conversations/threads/{threadId}/messages/{messageId}/original-content returns the raw original message content, useful for archival or for showing full email source to a reviewer.

Can I limit what my agent is allowed to do with the HubSpot Conversations Inbox & Messages API?

Yes. Because you run Jentic One yourself, your own rules decide which Conversations operations the agent may call and which HubSpot credential it uses, so you can allow reading threads and posting a reply while excluding archiving a thread via DELETE /conversations/v3/conversations/threads/{threadId}. Since the thread id sits in the URL path, a rule can also pin the agent to a single thread for getting messages, updating the thread, and sending a reply. The HubSpot token stays with your instance and is added only at execution time, never reaching the agent's prompt or context.

HubSpot Conversations Inbox & Messages

Connect the Conversations Inbox & Messages to your agent

Capabilities

Start building with Conversations Inbox & Messages API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs