Custom AI chatbot integration for HubSpot
We build a custom AI chatbot that works inside HubSpot: its conversations appear in your inbox or help desk, and it reads and updates contacts and tickets in your CRM. This page covers the routes HubSpot provides and the plan each one needs.
Updated
In your inbox
Customer messages and bot replies are published into HubSpot threads, so reps see the whole conversation.
Scoped CRM access
The chatbot gets the contact and ticket scopes it needs, and nothing more.
Engineers from $45 an hour
Published rates, and a written quote after discovery for a defined project.
How does a custom chatbot appear in HubSpot's inbox and help desk?
Through the Custom Channels API. You register your chatbot's channel with HubSpot, connect it to an inbox or the help desk, and publish each customer message and bot reply into a thread. HubSpot logs them to the CRM and the inbox. When a rep replies in HubSpot, HubSpot posts that message to your webhook for delivery.
HubSpot describes custom channels as a bridge "between an external message service and HubSpot's inbox or help desk" (HubSpot Developers). For a chatbot, the external service is the chat your customers use, and the bot sits behind it. The pieces:
- Register the channel once, with your developer API key and app ID, and declare what it supports, such as rich text, attachments and quick replies.
- Connect a channel account to a specific inbox or help desk. For your own business, you can connect it directly with admin access or an app that has the conversations.read scope.
- Publish every message: customer messages as INCOMING, bot replies as OUTGOING with a sender name, so the thread reads as one conversation.
- Receive rep replies. HubSpot sends an OUTGOING_CHANNEL_MESSAGE_CREATED event to your webhook URL with the ID of the rep who sent it, so your service delivers it and the bot knows a person has stepped in.
- Link contacts. Email and phone identifiers resolve to contacts automatically; for other IDs you pass the contact ID.
With HubSpot-managed threads, an incoming message reopens a closed thread only if its last activity was under 24 hours ago. For general hand-off rules, see our AI chatbot integration page.
What does HubSpot's chatbot "Trigger a webhook" action need?
A Data Hub Professional or Enterprise subscription. The action lets HubSpot's rule-based chatbot call your endpoint mid-conversation, wait for the response, and continue. It suits a lighter build: HubSpot's chatflow runs the conversation and your AI answers specific steps, rather than your chatbot owning the whole conversation.
HubSpot's guide to bot actions says "A Data Hub Professional or Enterprise subscription is required to use the action Trigger a webhook." You set the webhook URL, choose whether to wait for the webhook to return information before the next action, and write an error message for when it fails (HubSpot).
The rule-based chatbot itself is on all HubSpot plans, though some templates, such as the knowledge base and support bot, need Service Hub Professional or Enterprise (HubSpot). We use this route when the conversation is mostly fixed steps and only one or two need an AI answer.
Our rates
Published prices in US dollars. Monthly plans are 160 hours, about 15% below the hourly rate.
Mid-level developer
3 to 5 years
$25 / hour
$3,400 a month (160 h)
Senior developer
6 or more years
$35 / hour
$4,750 a month (160 h)
AI / LLM engineer
Agents, RAG, IBM watsonx
$45 / hour
$6,100 a month (160 h)
Senior AI engineer
Leads AI architecture and delivery
$60 / hour
$8,150 a month (160 h)
Two-week trial with the developer you choose. No charge if you stop within the first five working days. US Eastern clients get 09:00 to 12:00 US Eastern time through an evening shift, at 15% extra. Full pricing and comparisons.
What HubSpot CRM data can the chatbot read and write?
Whatever its app's scopes allow. With contact and ticket scopes it can look up a customer, read their tickets, and create or update tickets linked to that contact. HubSpot lists the contact, ticket and conversations scopes as available to all accounts, so this part doesn't need a higher plan.
| Scope | What it allows |
|---|---|
| crm.objects.contacts.read and .write | View, create and change contacts (HubSpot Developers) |
| crm.objects.tickets.read and .write | View, create and change tickets |
| conversations.read and conversations.write | View inboxes, threads and messages; create and manage threads and messages |
| conversations.custom_channels.read and .write | Read and publish messages on your custom channel |
From HubSpot's scopes reference, checked 5 November 2026. We request only the scopes the chatbot needs.
To create a ticket, the bot posts its properties to the tickets endpoint using the internal IDs of the pipeline and status, not their names, and can associate it with the contact and company in the same request (HubSpot Developers).
One recent change: since September 23, 2026, the Conversations API returns an error when an integration adds a comment to a help desk thread. HubSpot is replacing help desk comments with notes, so a bot's summary for reps goes in through the Notes API (HubSpot Developers).
Which HubSpot plan and app type does a custom chatbot need?
It depends on the route. The Custom Channels API needs an app, not a legacy private app, and HubSpot lists its scopes as available only to Sales Hub or Service Hub Enterprise accounts. The chatbot webhook action needs Data Hub Professional or Enterprise. CRM scopes for contacts and tickets are available on all accounts.
| Route | App type | Subscription HubSpot lists |
|---|---|---|
| Custom Channels API | An app; legacy private apps aren't supported (HubSpot Developers) | Sales Hub or Service Hub Enterprise, for the custom channel scopes (HubSpot Developers) |
| Chatbot webhook action | None; set up in the chatflow | Data Hub Professional or Enterprise (HubSpot) |
| CRM and Conversations APIs | An app with the matching scopes | All accounts |
| Customer Agent | None; HubSpot's own agent | Professional or Enterprise, plus HubSpot Credits (HubSpot) |
As listed on HubSpot's pages on 5 November 2026. HubSpot changes plan packaging, so confirm on your account before you budget.
If your account isn't on Sales Hub or Service Hub Enterprise, check the custom channel scopes with HubSpot before choosing that route. The chatbot can still read and update the CRM, or run behind the webhook action.
When is HubSpot's Customer Agent the better buy?
When your support already runs in HubSpot's inbox or help desk on chat, email and forms, you are on a Professional or Enterprise plan, and your answers come from content HubSpot holds. Customer Agent costs $0.50 per resolution, charged in HubSpot Credits, and HubSpot maintains it. A custom chatbot is worth it when HubSpot isn't the only system involved.
HubSpot prices Customer Agent "per conversation resolved, at $0.50 per resolution," on Professional and Enterprise subscriptions, running on HubSpot Credits (HubSpot). It can be assigned to live chat, email, forms, calling (in beta) and the social messaging channels HubSpot connects (HubSpot). From HubSpot's documentation (HubSpot):
- A resolution is a conversation where the agent shared a content source or took an action, with no qualifying hand-off within 72 hours of the customer's last reply.
- Only customer-initiated hand-offs stop a resolution counting. Assigning a rep yourself, including by workflow, doesn't.
- If credits run out, the agent stops taking new conversations until credits reset or you buy more.
- Reply recommendations for reps don't use credits, and new users can opt in to 14 days of free access.
Customer Agent's per-resolution price is low, so cost alone rarely justifies a custom build. By our arithmetic, 4,000 resolutions a month is $2,000, about the top of our monthly maintenance estimate for a custom chatbot. A custom chatbot is the better choice when it must act in systems outside HubSpot, such as orders or billing, when customers write to you on a channel HubSpot doesn't connect, or when the model must run in your country or on your own servers (private AI).
What does a HubSpot chatbot integration cost?
HubSpot's own fees depend on the route: an Enterprise plan for custom channels, or Data Hub Professional for the webhook action. Then the build. By our planning estimates, a chatbot that reads your business systems takes 480 to 960 hours, and one that takes actions takes 800 to 1,600. Engineering is $45 to $60 an hour.
| What the chatbot does | Build hours | At Webify.AI rates |
|---|---|---|
| Reads HubSpot and your business systems | 480 to 960 | $22,800 to $45,600 |
| Also takes actions, such as creating tickets or updating orders | 800 to 1,600 | $42,000 to $84,000 |
Planning estimates, not quotes. Maintenance is 20 to 40 hours a month in the first months, $1,050 to $2,100. HubSpot fees and model usage come on top.
A first version scoped to one task with one or two integrations typically takes six to twelve weeks. See our AI agent cost guide and pricing page.
Frequently asked questions
Can a custom chatbot reply inside HubSpot's shared inbox?
Yes, through the Custom Channels API. The chatbot publishes each customer message and its own replies into a HubSpot thread, and reps reply from the inbox or help desk like any other channel.
Do we need HubSpot Enterprise for a custom chatbot?
For the Custom Channels API, HubSpot lists the scopes as available to Sales Hub or Service Hub Enterprise accounts. The chatbot webhook action needs Data Hub Professional or Enterprise. Contact and ticket scopes are on all accounts.
Can we build the custom channel as a legacy private app?
No. HubSpot says the custom channel endpoints aren't supported in a legacy private app, so you create an app instead.
How does a rep take over from the chatbot?
The rep replies in the HubSpot thread. HubSpot sends that reply to your webhook with the rep's ID, your service delivers it, and we build the chatbot to stop answering in that conversation.
Is Customer Agent cheaper than a custom chatbot?
Often, at modest volume. It costs $0.50 per resolution on Professional and Enterprise plans. A custom chatbot is worth it for other systems, channels, model choice or data location, not usually for price alone.
Talk to an engineer about your HubSpot chatbot
A conversation about your goals and systems, and a straight answer on whether an agent is the right tool. Paid work starts only after you have agreed a written scope.
- We sign your NDA before the first call if you need one
- You leave with a next step, even if the answer is "you don't need an agent"
- The code and IP are yours if you go ahead
Book a free first call
Pick a time, or send us the details and we will reply.