By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Muse to HubSpot is the Ryze AI connector. Connect HubSpot in a Ryze AI workspace with HubSpot's own sign-in, then ask Muse in a chat to create a custom connector for https://connector.get-ryze.ai/mcp, follow its guided setup and sign in to Ryze AI when the link arrives. Muse then has 5 HubSpot tools: 3 that read, 1 that writes and 1 that deletes. They cover CRM contacts, companies and deals, lists, owners and blog posts.
- In Ryze AI open Integrations, find HubSpot and click Connect, then choose the portal and approve the permissions
- In a Muse chat, ask Muse to create a custom connector for https://connector.get-ryze.ai/mcp
- Follow Muse's guided setup and open the sign-in link it sends
- Choose the workspace and click Allow connection
Muse to HubSpot at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, created by asking Muse in a chat. HubSpot is connected once in Ryze AI with an OAuth sign-in, with no token to paste and nothing to host |
| Server address | https://connector.get-ryze.ai/mcp |
| Where Muse is available | The US and Canada, per Meta |
| How the connector is added | Muse creates it from a chat request and runs a guided setup. Meta's pages describe no settings field for a server URL |
| Sign-in | A link Muse sends back opens the Ryze AI sign-in, where you pick workspaces and click Allow connection |
| HubSpot tools | 5 in all: 3 read, 1 write and 1 delete |
| Can Muse change HubSpot | Yes: it can create and update contacts, companies and deals, and delete records or blog posts when asked. Meta says Muse does not take many important actions without approval by default |
| Other data in the same chat | Tools for the other platforms connected to your Ryze AI workspaces list under the same address. This guide covers HubSpot only |
| Muse plan needed | Meta's help and newsroom pages reviewed name no plan for custom connectors |
| Ryze AI price | Adding the connector costs nothing. The tools need an active plan or trial: Paid Ads is $89 per month with a 7-day free trial, SEO Starter $129 per month with a 3-day free trial, Agency $279 per month |
| HubSpot's own option for Muse | The remote HubSpot MCP server at https://mcp.hubspot.com needs an MCP connector made in HubSpot, and HubSpot's pages name no Muse steps. Zapier MCP has a documented Muse setup and can run HubSpot actions |
| Last tested | 11 read-only HubSpot calls went through the connector from Claude Code on November 14, 2026. Nothing was run inside Muse |
Before you start
- A Muse account in the US or Canada. Meta says Muse is offered in those two countries only. The help and newsroom pages reviewed name no plan for custom connectors, so none is claimed here.
- A HubSpot user who can install apps. HubSpot says installing an app needs a Super Admin or a user with App Marketplace access. The portal is chosen in the HubSpot sign-in, and one connection covers one portal.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with a 3-day free trial and Agency is $279 per month. Connecting is free; the HubSpot tools need an active plan or trial. Annual billing takes 30% off the first year.
How to connect Muse to HubSpot
Ryze AI takes the first two steps, and Muse the other four. Step 2 is optional. Everyone uses the same connector URL.
Connect HubSpot in Ryze AI
Create a Ryze AI account or sign in, open Integrations and find the HubSpot card. Click Connect, sign in to HubSpot, choose the account (portal), click Choose Account and approve the requested permissions. HubSpot returns you to Ryze AI with the connection saved.
Optional: pick a blog for publishing
To publish Content Plan articles to HubSpot, click View on the HubSpot card, pick the Blog and the Author and click Save. Chat-only use of the CRM tools needs no blog.
Ask Muse to create the custom connector
In a Muse chat on the web or in the app, ask Muse to create a custom connector for https://connector.get-ryze.ai/mcp. The Ryze AI page at ryze.ai/muse has a ready-made message you can paste. Meta describes no settings field for a server URL, so the chat request is the route.
Follow Muse's guided setup
Muse walks you through setting up the connector and sends back a sign-in link. Meta says setup can involve retrieving API information from the service, and Muse keeps the credentials in its Secure Credentials Store.
Sign in to Ryze AI and allow the connection
Open the link, sign in on the Ryze AI page, choose the workspace that holds your HubSpot connection and click Allow connection.
Check approvals and ask your first question
Muse settings control how much it does without asking. Then ask: Find the contact with this email address and show the lifecycle stage. To change or remove the connector later, open Settings, then Connectors in Muse. If the connector was added before HubSpot was connected, remove and re-add it so the tool list refreshes.
The Ryze AI help article for HubSpot covers the HubSpot side of the connection and the blog and author choice, and Meta describes custom connectors in its Muse help article.
Sources: Meta help: Muse connectors, Ryze AI Muse page. Checked November 8, 2026. Ryze AI HubSpot guide. Checked November 14, 2026.
Where Muse is available
Meta introduced Muse for small businesses in a newsroom post dated September 29, 2026, and says Muse is available in the US and Canada. The post says the full list of available connectors is in the Muse app settings and that custom connectors cover services Meta does not support yet. HubSpot is not named in the post, and the in-app connector list was not opened for this guide.
Muse is a chat assistant with no code editor or command line side in the pages reviewed, so there is one place to connect: the chat on the web or in the app. If you work in a code editor, see the Claude and ChatGPT guides linked in Related guides below.
Muse and connectors: the facts in one table
| Topic | What Meta and Ryze AI say |
|---|---|
| How a connector is created | By asking Muse in a chat to create a custom connector, then following the guided setup it starts |
| Server URL field | None described. Meta's pages never mention MCP or a field for a server address |
| Where Ryze AI's connector details come from | The Ryze AI page at ryze.ai/muse, updated September 24, 2026: MCP over HTTP with an OAuth sign-in. Meta's pages do not confirm this, and it was not verified independently |
| Credentials | Muse stores them in its Secure Credentials Store, per Meta |
| Approval | By default Muse does not take many important actions without approval. Meta says the approval behavior is changed in Settings |
| Meta's newsroom on actions | Nothing publishes, sends or spends without your approval |
| Reviewing connectors | Meta does not review custom connectors or how they use data |
| Where connectors are managed | Muse Settings, then Connectors |
| Availability | The US and Canada |
| Plan | Meta's pages reviewed name none for custom connectors |
Sources: Meta help: Muse connectors, Meta newsroom: Muse for small business, Ryze AI Muse page. Checked November 8, 2026.
Claude and ChatGPT
Other MCP clients accept the same URL, and the HubSpot connection made in Ryze AI stays as it is.
Claude
Add the same URL under Customize, Connectors, Add custom connector, then pick the workspace and start a new chat. Claude caches the tool list when you add the connector, so if you connected HubSpot in Ryze AI afterwards, remove the connector, add it again and open a new chat. In Claude, write and delete tools can be set to Needs approval under Customize > Connectors > Ryze AI > Tool permissions.
ChatGPT
OpenAI lists full custom MCP support for Business and Enterprise/Edu workspaces on ChatGPT web, with Pro limited to read and fetch permissions. The steps are in the ChatGPT guide linked below.
HubSpot permissions
The HubSpot side of the connection is one OAuth sign-in inside Ryze AI. Muse adds a second sign-in for the Ryze AI connector itself and its own approval setting, and Meta says it does not review custom connectors. Four things decide what Muse can see and change.
- Who can install
- HubSpot requires a Super Admin or a user with App Marketplace access to install an app. Anyone else needs a Super Admin to do the HubSpot step.
- What the token covers
- HubSpot says an OAuth access token reflects the scopes the app requested, not the permissions of the user who installed it. HubSpot's own example: a user who can view only owned contacts but authorizes the contacts read scope gives the app a token that can view all contacts in the account.
- One portal per connection
- Each connection is one HubSpot portal. Several portals can be connected to one Ryze AI workspace; one is the primary and is used unless you name another.
- Read, write and delete
- The scopes cover both read and write for contacts, companies and deals, so there is no read-only mode for the connection in the facts. Muse's own approval setting is the lever for slowing down the write and delete tools.
The access layers between Muse and a file
Several sign-ins and settings sit between a Muse chat and a HubSpot record. Read the first table from Muse down to HubSpot, then the scopes below it.
| Layer | What it allows | Where it is set |
|---|---|---|
| Muse to the Ryze AI connector | A sign-in on the Ryze AI page that Muse's link opens. The connector offers two scopes, mcp:read and mcp:write | The sign-in link from Muse |
| Ryze AI workspace | The workspace you allow there | The Allow connection screen |
| Ryze AI to HubSpot | A HubSpot OAuth install on one portal, with the permissions shown on HubSpot's consent screen | Integrations, HubSpot, Connect |
| Which data types | Contacts, contact properties, companies, deals, deal properties, contact lists, owners and CMS blog posts, as the Ryze AI listing in the HubSpot Marketplace shows in its Shared Data table | The HubSpot Marketplace listing for Ryze AI |
| Muse approvals | By default Muse does not take many important actions without approval | Muse Settings |
HubSpot's scope reference describes crm.objects.contacts.write as permission to create, delete and change contacts, which is why the one connection can both edit and delete CRM records. The facts file lists the scopes in words, and the HubSpot consent screen is the source of truth for the exact strings.
The HubSpot scopes in the connection
| In the facts | HubSpot scope | What HubSpot says it covers |
|---|---|---|
| Contacts read and write | crm.objects.contacts.read, crm.objects.contacts.write | View properties and details; create, delete and change contacts |
| Companies read and write | crm.objects.companies.read, crm.objects.companies.write | View properties and details; create, delete and change companies |
| Deals read and write | crm.objects.deals.read, crm.objects.deals.write | View properties and details; create, delete and change deals |
| Owners read | crm.objects.owners.read | View details about users assigned to a CRM record |
| Contact schema read | crm.schemas.contacts.read | View details about property settings for contacts |
| Deal schema read and write | crm.schemas.deals.read, crm.schemas.deals.write | View, create, delete or change property settings for deals |
| Lists read | crm.lists.read | View details about contact lists |
| Content | content | Content APIs including website pages, landing pages and blog APIs. HubSpot lists it for CMS Hub or Marketing Hub Professional or Enterprise accounts only |
What the connection does not include
- Tickets. A ticket search on the default connection was refused with status not_allowed in the November 14 test.
- Custom objects. The requested scopes include no custom object scopes, so custom object records are not covered.
- List editing. Lists are read only. Adding or removing list members is not supported.
- Theme and template code. CMS source-code file endpoints return raw files and fail through the read tool.
- Sensitive Data properties. HubSpot keeps these under separate scopes that are not in the connection.
- Several portals in one call. Each connection is one portal. Name the portal in a prompt to use a non-primary one.
Sources: HubSpot scopes, HubSpot OAuth guide, HubSpot: install apps, Ryze AI in the HubSpot Marketplace, Ryze AI HubSpot guide. Checked November 14, 2026. Meta help: Muse connectors, Meta newsroom: Muse for small business. Checked November 8, 2026.
Removing access
To remove access, click View on the HubSpot card in Ryze AI Integrations and disconnect the portal with the trash icon, or in HubSpot go to Settings, Integrations, Connected Apps, open Actions on the app, choose Uninstall and type uninstall to confirm. In Muse, manage or disconnect the connector under Settings, then Connectors.
What Muse can do in HubSpot
Muse gets 5 HubSpot tools from the Ryze AI connector: 3 that read, 1 that writes and 1 that deletes. Each full name starts with hubspot__. The tool definitions seen on November 14, 2026 show that each tool also takes a workspace argument and an optional connection_id for a specific connected portal.
| Tool | Type | What it does |
|---|---|---|
| listObjects | Read | Lists CRM records of one object type page by page, with the properties you choose and the IDs of associated records. |
| search | Read | Searches CRM records through the HubSpot CRM Search API with filter groups, sorts, a text query and chosen properties. |
| read | Read | Sends a GET request to a HubSpot JSON API resource, such as a record, property definitions, owners, a list or blog posts. |
| write | Write | Creates or updates a HubSpot resource, such as a contact, company, deal or blog post, and adds associations between records. |
| delete | Delete | Deletes (archives) a HubSpot resource by ID, such as a CRM record or blog post. |
Meta says Muse does not take many important actions without approval by default, and that you change the approval behavior in Settings. Its newsroom adds that nothing publishes, sends or spends without your approval. Check that setting before you hand Muse the write and delete tools, because write can change a CRM property and delete can remove a record or a blog post. Most CRM deletes go to HubSpot's recycling bin, where records can be restored for up to 90 days, but a deleted blog post may not be recoverable. The wording of Meta's setting was not tried for this guide. In the Ryze AI chat, the Tool approvals setting starts on Skip all approvals; Approve write & delete and Manual approve can be chosen there, and scheduled tasks run without an approval step.
11 tool calls from the test, with what came back
The test sent 11 HubSpot calls through the Ryze AI connector on November 14, 2026, all read-only. They came from Claude Code, since Muse took no part. Searches used random strings that match nothing, so no record could come back from them. Nothing was written or deleted, and no record was read by ID.
| Call | Tool | Outcome |
|---|---|---|
| Contacts, email equals a random 20-letter string | search | Succeeded with an empty result, {"total":0,"results":[]} |
| Companies, domain equals a random string | search | Succeeded with the same empty shape |
| Deals, deal name equals a random string | search | Succeeded with the same empty shape |
| Contacts, one record, one property named | listObjects | Succeeded: one result plus a paging block with an after cursor. HubSpot also returned createdate and lastmodifieddate |
| Contacts, filter on a property that does not exist | search | Error 400, There was a problem with the request. |
| Contacts, limit 201 | search | Error 400, VALIDATION_ERROR, limit must be in range [0..200] |
| Tickets, a filter that cannot match | search | Refused with status not_allowed |
| Deal with ID 0 | read | status not_found, Object not found |
| Contact with a made-up 18-digit ID | read | status not_found; HubSpot answered with an HTML 404 page |
| Blog post with a made-up 18-digit ID | read | status not_found, HTML 404 again. This does not show whether blog reads work on the portal |
| Blog post with ID 1 | read | status not_found, HTML 404 again |
No response carried a rate limit or quota header. The only limit figure that came back was the search page range of 0 to 200.
Limits to know
These limits shape what comes back in prompts. They come from the Ryze AI tool definitions and HubSpot's documentation, plus Meta's description of Muse connectors.
| Limit | Detail |
|---|---|
| Reach | Contacts, companies and deals, plus lists, owners, property definitions and blog posts through the read tool. Tickets, custom objects and list edits are outside the connection. |
| Default properties | HubSpot returns a default subset of properties unless you name specific fields, so ask for the properties you want by name. |
| Search page size | 10 records per page by default and at most 200. The search tool passes the limit to HubSpot, which refused 201 in the test. |
| Listing page size | listObjects accepts a limit of up to 100 per page. |
| Search result cap | 10,000 total results for any query; paging past that returns a 400 error. |
| Fresh records | New or updated records can take a few moments to show up in search, and archived records never appear. |
| Muse approvals | Meta says Muse does not take many important actions without approval by default. The control is in Muse Settings. |
| Muse regions | US and Canada, per Meta. |
Limits in numbers
| Limit | Number | Source |
|---|---|---|
| Burst limit, OAuth apps distributed through the HubSpot Marketplace | 110 requests every 10 seconds for each HubSpot account that installs the app, not counting the CRM Search API. Ryze AI connects with OAuth and has a Marketplace listing, so this reads as the rule that applies, but no HubSpot page says it about Ryze AI and no response showed the figure | HubSpot usage guidelines |
| CRM Search API rate | 5 requests per second per account | HubSpot CRM search guide |
| Search filters | At most 5 filter groups with up to 6 filters each, 18 filters in total. Filters in a group are joined with AND and groups with OR | HubSpot CRM search guide |
| Search query length | At most 3,000 characters | HubSpot CRM search guide |
| Contacts per list request | Up to 100, paged on with the after value | HubSpot contacts guide |
| Rate limit errors | Past a limit HubSpot answers 429. Daily rate limit headers are not included in responses to OAuth requests | HubSpot usage guidelines |
| Access token lifetime | OAuth access tokens expire after 30 minutes and the app refreshes them with the refresh token | HubSpot token docs |
| Recycling bin | Deleted CRM records can be restored up to 90 days after deletion. Permanent or GDPR deletions skip the bin and may take up to 30 days to be purged | HubSpot restore deleted records |
| Blog posts API | 20 results per page by default | HubSpot blog posts guide |
| Ryze AI tool inputs | listObjects limit up to 100, search limit up to 200, path arguments up to 2,048 characters | Tool definitions, November 14, 2026 |
Sources: HubSpot usage guidelines, HubSpot CRM search guide, HubSpot contacts guide, HubSpot token docs, HubSpot restore deleted records, HubSpot blog posts guide, Ryze AI HubSpot guide. Checked November 14, 2026. Meta help: Muse connectors. Checked November 8, 2026.
First 3 prompts to run
1. Find a contact by email
Find the HubSpot contact with the email address of my last sales call and show the lifecycle stage and create date.
Tools used: search
What comes back: A search result from your own portal with the properties you named. An email that matches no contact returns an empty result.
2. List recent deals
List the HubSpot deals created in the last 30 days with the deal name, amount and stage.
Tools used: search
What comes back: The matching deals with those three properties, up to 200 per page. Properties you do not name come back only in HubSpot's default set.
3. Update a property on a deal
Set the close date of the deal named in my last message to the end of next month.
Tools used: write
What comes back: The deal changes in your portal. Check Muse's approval setting first, because this edits a live record.
Each answer comes from your own portal, so this page describes what comes back instead of showing sample data. Write calls change real records.
10 jobs to hand to Muse
Ten jobs to hand to Muse, each with the tool that does the work. In the November 14 test only empty search results and one contact listing came back, so every row follows Ryze AI's tool list, not a run on real records. Every job needs an active Ryze AI plan or trial. Meta says Muse does not take many important actions without approval by default, which covers the write and delete jobs unless you change that setting.
| Job | What to say to Muse | Tool | On the default connection |
|---|---|---|---|
| Find a contact by email | Find the contact with this email and show the properties I name. | search | Yes |
| Recent deals | List deals created in the last 30 days with name, amount and stage. | search | Yes |
| Stale open deals | Find open deals with no change in 30 days and show the owner of each. | search, then read on crm/v3/owners | Yes; the owners read was not run in the test |
| Company and its people | Find a company by domain and list its associated contacts and deals. | search, then listObjects with associations | Yes; associations were not requested in the test |
| Page through contacts | List contacts with lifecycle stage and create date, page by page. | listObjects | Yes, 100 per page at most |
| Check property names | Show which contact and deal properties exist before we build a filter. | read on crm/v3/properties/contacts or deals | Yes; not run in the test |
| Read a contact list | Read this list and its details. | read on crm/v3/lists/{listId} | Yes, read only; adding or removing members is not supported |
| Create a deal | Create a deal and associate it with a company and a contact. | write | Yes; not run, it changes the portal |
| Update a property | Update a property on a contact, company or deal. | write with the UPDATE method | Yes; not run |
| Delete a duplicate contact | Delete the duplicate contact with this ID. | delete | Yes when you ask by ID; most CRM deletes go to the recycling bin; not run |
Jobs the connection cannot do: search or update tickets (refused in the test), read or edit custom object records, add contacts to a list or edit a list, and read a theme or template code file from the CMS.
3 ways to connect Muse to HubSpot
Three ways can give Muse access to HubSpot on the pages checked for this guide. Meta describes custom connectors as something you ask Muse to create and never mentions a field for a server URL, so whether Muse accepts a server other than the Ryze AI one is not documented. The Ryze AI connector is the main way: one address, a HubSpot sign-in inside Ryze AI, no HubSpot connector to build. The vendor pages were read on November 14, 2026, and Zapier's Muse page on November 21, 2026. None of the three was tried in Muse.
| Way | Runs where | Setup in Muse | What it reaches in HubSpot | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI at one shared address | Ask Muse to create a custom connector for https://connector.get-ryze.ai/mcp, follow the guided setup and sign in from the link Muse sends. ryze.ai/muse offers a message to paste. HubSpot is connected in Ryze AI first | 5 tools covering CRM search, listing, reads of records, lists, owners and blog posts, writes to contacts, companies, deals and blog posts, and deletes. No tickets, custom objects or list edits | Free to add. Tools need an active plan or trial: Paid Ads $89 a month (7-day trial), SEO Starter $129 (3-day trial), Agency $279 |
| HubSpot remote MCP server (untried with Muse) | Hosted by HubSpot at https://mcp.hubspot.com, OAuth with PKCE, generally available since April 13, 2026 | In HubSpot, go to Development, MCP Connectors and create one with a name and a redirect URL; HubSpot gives a client ID and secret. Then point an MCP client at the server. HubSpot's pages name no Muse steps, Meta documents no field for a server URL, and the redirect URL Muse would use is not documented | 36 tools in the documented list: CRM records including tickets and leads, activities, landing pages, blog posts, campaigns, marketing email, conversations and more. No delete tool is listed. Actions follow the HubSpot user's own permissions | No price stated; HubSpot says it is available to all HubSpot accounts |
| Zapier MCP (documented for Muse) | Hosted by Zapier | In Muse go to Settings, Connectors, select Zapier and click Connect, copy the setup prompt, sign in to Zapier and click Allow. Then enable HubSpot actions in Zapier | The HubSpot actions you enable from your Zapier account, such as Create Contact, Create Company, Add Contact to List and Create CRM Object. Zapier prints no total for HubSpot | Each successful call uses 2 tasks from your Zapier plan; failed calls use none. Plans start with Free at 100 tasks a month |
Options that do not fit Muse
- HubSpot's connectors for ChatGPT, Claude, Gemini and Microsoft Copilot. Each belongs to its own assistant and is documented only there, so none can be added to Muse.
- HubSpot's Developer MCP server and the @hubspot/mcp-server npm package. The first is a local tool for app and CMS development that does not reach CRM records, and the second is a beta package that runs locally with an access token. Neither has Muse steps.
- Composio. Its HubSpot page names Claude, Cursor and ChatGPT and does not mention Muse in the pages read.
- Windsor.ai and Coupler.io. Both are reporting layers built on data you load into them. Their pages name other assistants, not Muse. Coupler.io is read only, and Windsor's page names write actions for other platforms, not HubSpot.
- baryhuang/mcp-hubspot. An open source Docker server you run with your own access token. Muse would have to reach it at a public address, and Meta documents no such route.
Which one to pick
Ryze AI is the best way to connect Muse to HubSpot when you want a chat to search contacts, companies and deals and make edits through one hosted address with a HubSpot sign-in, with four caveats: the tools exclude tickets and custom objects, they need a Ryze AI plan once the trial ends, one connection covers one portal, and Meta documents no field for a server URL. HubSpot's own remote server fits a builder who needs tickets, activities or marketing data and can make an MCP connector in HubSpot, but its pages give no Muse steps. Zapier MCP fits a team that already runs HubSpot actions through Zapier and wants the setup Zapier documents for Muse.
Sources: HubSpot remote MCP server docs, HubSpot AI tools, Zapier MCP for HubSpot, Zapier MCP usage, Composio HubSpot, Windsor MCP, Coupler.io HubSpot MCP, mcp-hubspot, Ryze AI HubSpot guide. Checked November 14, 2026. Zapier MCP for Muse. Checked November 21, 2026. Meta help: Muse connectors, Meta newsroom: Muse for small business, Ryze AI Muse page. Checked November 8, 2026.
HubSpot, Muse and MCP: dates that matter
| Date | What happened |
|---|---|
| September 1, 2025 | HubSpot's remote MCP server went into public beta across all hubs and tiers. |
| January 13, 2026 | Self-service MCP connectors for the remote server went live in public beta (announced January 20, 2026). |
| April 13, 2026 | HubSpot's remote MCP server became generally available to all accounts, with write access added and OAuth 2.1 with PKCE required. |
| August 27, 2026 | HubSpot announced that legacy private app creation is disabled on September 28, 2026 for new accounts and October 26, 2026 for older ones; existing private apps keep working. |
| September 2026 | Meta launched Muse for small businesses in the US and Canada with custom connectors (newsroom post dated September 29, 2026). |
| September 15, 2026 | HubSpot announced the end of support for API versions v1 to v3 and legacy apps, enforced in September 2027, with v4 support ending on March 30, 2027. |
| October 30, 2026 | HubSpot's AI connector access to Sensitive Data went into public beta for the ChatGPT, Claude and Copilot connectors, read only and allowed by a Super Admin. |
| December 4, 2026 | HubSpot's Pipelines API V1 stops responding after this sunset date. |
HubSpot's version dates are HubSpot's. The facts give no statement on how Ryze AI will handle them.
Sources: HubSpot remote MCP server GA, HubSpot MCP auth apps beta, Legacy private app sunset, Legacy APIs and apps, HubSpot October 2026 rollup, Pipelines API V1 sunset. Checked November 14, 2026. Meta newsroom, September 2026, Ryze AI Muse page. Checked November 8, 2026.
How this guide was tested
One round of checks stands behind this guide: on November 14, 2026 the 5 HubSpot tool definitions were loaded and 11 read-only HubSpot calls went through the connector from Claude Code. Meta's pages and the Ryze AI Muse page were read on November 8, 2026, and Zapier's Muse page on November 21, 2026.
| What was run | What came back |
|---|---|
| Tool list, November 14 | 5 hubspot tools matching the tools table: 3 read, 1 write, 1 delete. |
| Empty searches, November 14 | Contacts, companies and deals searches with a filter nothing matches succeeded and returned {"total":0,"results":[]}. |
| One contact listing, November 14 | listObjects with a limit of 1 returned one result and a paging cursor. |
| Five deliberate failures, November 14 | Each drew one of the messages in the errors table. |
| Rate limits | No quota counter or rate-limit header appeared, and no limit was hit. |
Not run for this guide: any step inside Muse. No Muse account was used, so the chat request, the guided setup, the sign-in link and Meta's approval setting follow Meta's pages and the Ryze AI Muse page as read on November 8, 2026. The write and delete tools were not called because they change the portal. No record was read by ID, and no owners, property definitions, lists or existing blog posts were read.
Errors and fixes
Exact error messages from the test
These messages came back in the test on November 14, 2026, with IDs removed. If one of them appears in a Muse tool call, here is what it means and what to ask next.
| Message | What it means | What to do |
|---|---|---|
| limit must be in range [0..200] (actual value: 201) | Error 400, category VALIDATION_ERROR. The CRM search returns at most 200 records per page. | Ask for 200 or fewer per page and page on with the after value. |
| There was a problem with the request. | Error 400. HubSpot rejected the search body and does not say which property is wrong. The test used a property name that does not exist. | Read the property definitions first (crm/v3/properties/contacts) and use the internal property name. |
| The scope needed for this API call isn't available for public use. If you have questions, contact support or post in our developer forum. | status not_allowed. The default Ryze AI connection could not search tickets. | Use contacts, companies and deals through Ryze AI. For tickets use HubSpot's own connector or MCP server. |
| Object not found. objectId is usually positive. | status not_found. No record has that ID. | Search for the record first and use the id it returns. |
| provider returned text/html;charset=iso-8859-1 (status 404) "Error 404 Not Found" | status not_found. HubSpot answered with an HTML 404 page, and the read tool only parses JSON and reports the 404. The same form came back for a contact path and two blog post paths. | Check the ID. Search for the contact by email, or list blog posts and use an ID from the list. |
Other problems
- Muse has no field for the URL
- Meta's pages describe none. Ask Muse in a chat to create a custom connector for https://connector.get-ryze.ai/mcp, or paste the message from the Ryze AI Muse page.
- The sign-in link never arrives
- Muse's guided setup was not tried for this guide. Ask Muse to send the sign-in link again, and check Settings, then Connectors, to see whether the connector was created.
- The HubSpot tools do not appear
- A tool list can be cached from before HubSpot was connected. Remove the connector in Muse under Settings, then Connectors, ask Muse to create it again, and check that the HubSpot card in Ryze AI shows Connected.
- HubSpot will not let you install
- HubSpot says installing an app needs a Super Admin or App Marketplace access. Ask a Super Admin to run the HubSpot step. The content scope is listed by HubSpot for CMS Hub or Marketing Hub Professional or Enterprise, and whether a portal on a lower tier can finish the install was not tested.
- A property comes back missing
- HubSpot returns a default subset of properties unless you name fields. Ask for the property by its internal name.
- A new record is not in the search
- New or updated records can take a few moments to appear in search. Archived records never appear.
- The tools say a subscription is required
- The HubSpot tools need an active Ryze AI plan or free trial. Start the trial, then retry.
- Muse is not available
- Meta says Muse is offered in the US and Canada only.
Terms on this page
- MCP
- The Model Context Protocol. The Ryze AI Muse page says the connector speaks it over HTTP with OAuth, a detail Meta's pages never mention.
- Custom connector
- Meta's term for a link to a service Muse lacks built in, created by asking Muse in a chat.
- Secure Credentials Store
- Where Meta says Muse keeps a connector's credentials.
- Portal
- A HubSpot account. One Ryze AI connection covers one portal.
- Scope
- A permission an app asks for at install time. Each one opens a set of HubSpot API endpoints and the data behind them.
- Filter group
- A block of filters in a CRM search. Filters inside a group are joined with AND and groups are joined with OR.
- Recycling bin
- Where deleted CRM records go. HubSpot can restore them for up to 90 days.
Sources: Meta help: Muse connectors, Meta newsroom: Muse for small business. Checked November 8, 2026. HubSpot scopes, HubSpot CRM search guide, HubSpot restore deleted records. Checked November 14, 2026.
Frequently asked questions
How do I connect Muse to HubSpot?
Connect HubSpot in a Ryze AI workspace, then ask Muse in a chat to create a custom connector for https://connector.get-ryze.ai/mcp, follow the guided setup and sign in to Ryze AI from the link Muse sends.
Is there a HubSpot connector for Muse?
Yes: ask Muse to create a custom connector for the Ryze AI address and Muse gets 5 HubSpot tools. HubSpot's own connectors are for ChatGPT, Claude, Gemini and Microsoft Copilot, and Zapier documents a Muse setup that can run HubSpot actions.
Is there a HubSpot MCP for Muse?
The Ryze AI connector is the documented route. HubSpot hosts its own remote MCP server at https://mcp.hubspot.com, but HubSpot's pages give no Muse steps and Meta does not say whether Muse accepts a server you set up yourself.
What is a HubSpot MCP server?
A server that lets an AI client such as Muse call HubSpot tools over the Model Context Protocol. The Ryze AI one has 5 tools that search and list CRM records, read lists, owners and blog posts, write contacts, companies, deals and blog posts, and delete records.
Where is Muse available, and which plan do I need?
Meta says Muse is available in the US and Canada. Its help and newsroom pages reviewed name no plan for custom connectors, so no plan requirement is stated here.
Is there a field for the server URL in Muse?
Meta's pages describe none. Custom connectors are created by asking Muse in a chat, and Muse starts a guided setup. The Ryze AI page at ryze.ai/muse has a ready-made message to paste.
Does Meta review custom connectors?
No. Meta says it does not review custom connectors or how they use data, and that Muse stores the credentials in its Secure Credentials Store. Review what the Ryze AI connection can do in HubSpot before you allow it.
Who can install the HubSpot connection?
HubSpot says installing an app needs a Super Admin or a user with App Marketplace access. If you have neither, ask a Super Admin to connect HubSpot in Ryze AI.
Can Muse edit my HubSpot records?
Yes. It can create and update contacts, companies and deals and add associations between records. Tickets, custom objects and list edits are not covered.
Can Muse delete HubSpot records?
Yes, when you ask for it. The connector has a delete tool, and most CRM deletes go to HubSpot's recycling bin, where records can be restored for up to 90 days. A deleted blog post may not be recoverable.
Does Muse ask before it changes my HubSpot data?
Meta says by default Muse does not take many important actions without approval, and its newsroom says nothing publishes, sends or spends without your approval. You change the approval behavior in Settings. This was not tried for this guide, so check the setting before you hand Muse the write and delete tools.
Can I connect more than one HubSpot portal?
Yes. Several portals can be connected to one Ryze AI workspace. One is the primary and is used unless you name another in the prompt.
How much does it cost?
Adding the connector costs nothing, but the tools need an active Ryze AI plan or free trial. Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with a 3-day free trial and Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect?
Manage or disconnect the connector in Muse under Settings, then Connectors. You can also disconnect the portal on the HubSpot card in Ryze AI, or uninstall the app in HubSpot under Settings, Integrations, Connected Apps.