HubSpot CMS API
Tools that enable LLMs to interact directly with the HubSpot CMS API.
1.0.0The HubspotCmsApi toolkit enables developers to integrate and manage content on the HubSpot CMS through a comprehensive set of API tools. It provides powerful functionalities ranging from creating and managing blog posts, pages, and database rows to handling multi-language content effortlessly.
Capabilities:
- Efficiently create, update, and delete blog posts, tags, and pages.
- Manage HubDB tables and their drafts with bulk operations.
- Support multi-language content management across various CMS objects.
OAuth:
- Provider: Unknown
- Scopes: cms.domains.read, cms.domains.write, cms.knowledge_base.settings.read, cms.knowledge_base.settings.write, content, hubdb, media_bridge.write
Available tools(175)
| Tool name | Description | Secrets | |
|---|---|---|---|
Add a new row to a HubDB draft table.
Use this tool to add a new row to the draft version of a HubDB table. To make these changes live, publish the table afterwards.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Archive multiple blog tags in HubSpot CMS.
Use this tool to delete multiple blog tag objects in HubSpot CMS by providing their identifiers. Suitable for cleaning up unused or obsolete tags in batches. | |||
Archive a HubDB table in HubSpot CMS.
Use this tool to archive (soft delete) an existing HubDB table in HubSpot CMS, affecting both published and draft versions. | |||
Attach a Blog Author to a multi-language group.
Use this tool to link a specific blog author with a multi-language group in HubSpot CMS. This action helps manage authors across different language variations of your blog. | |||
Attach a blog post to a multi-language group in HubSpot CMS.
Use this tool to attach a specific blog post to a multi-language group in HubSpot CMS, enabling content localization and management. | |||
Attach a blog to a multi-language group in HubSpot CMS.
Use this tool to attach a blog to a specified multi-language group within HubSpot CMS. It is helpful when managing blogs in different languages and ensuring they are correctly grouped. | |||
Attach a landing page to a multi-language group.
Use this tool to associate a landing page with an existing multi-language group, enabling better management of language variations within HubSpot CMS. | |||
Attach a site page to a multi-language group.
Use this tool to attach a specific site page to an existing multi-language group, enabling multi-language support for that page. | |||
Attach a blog tag to a multi-language group.
Use this tool to connect a specific blog tag to a designated multi-language group within HubSpot CMS. This is useful for managing tags across different language versions of a blog. | |||
Update multiple draft table rows in HubSpot CMS.
This tool updates up to 100 rows in the draft version of a specified HubSpot CMS table. Use it when you need to apply changes to several rows at once in a draft table.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Retrieve the current status of a source-code extraction task.
Use this tool to check the status of a specific source-code extraction by providing the `taskId`. It's useful for tracking the progress of an extraction after initiating it with the `extract/async` request. | |||
Creates a copy of an existing blog post.
This tool clones an existing blog post, creating a new copy with the same content. It should be used when you want to duplicate a post for editing or reuse. | |||
Clone rows in a draft HubDB table by row IDs.
Use this tool to clone specific rows in the draft version of a HubDB table by providing up to 100 row IDs. Useful for duplicating data entries during content management in HubSpot's CMS.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Clone a single row in a HubDB draft table.
Use this tool to clone a specific row in the draft version of a HubDB table within HubSpot CMS. This is helpful for duplicating draft content before finalizing changes. | |||
Clone an existing HubDB table as a draft.
Use this tool to create a draft clone of an existing HubDB table. The new table's name and label can be specified. | |||
Clone a landing page in HubSpot CMS.
This tool duplicates an existing landing page within HubSpot's CMS. It should be used when you need an exact replica of a landing page for further customization or testing. | |||
Clone an existing site page in HubSpot CMS.
This tool is used to clone an existing site page within the HubSpot CMS. It is useful when duplicating pages for updates or creating similar content quickly. | |||
Create a new A/B test variation in HubSpot CMS.
This tool allows you to create a new A/B test variation for a landing page using HubSpot CMS. It should be called when you need to perform A/B testing by generating different page variations to assess their performance. | |||
Log viewer's attention span details for media events.
This tool creates an event recording viewer attention span details for media, which helps in tracking engagement and interaction levels.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | |||
Create multiple blog posts in a single request.
This tool is used to create a batch of blog posts by specifying their content in the request body. It should be called when you need to publish multiple blog posts at once.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | |||
Create a new Blog Author in HubSpot CMS.
Use this tool to create a new blog author within the HubSpot CMS. It should be called when you need to add an author to your blog system.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | |||
Create a language variation for a blog author.
This tool creates a new language variation from an existing blog author in HubSpot CMS, allowing for multilingual content management.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | |||
Create multiple blog authors in a single batch request.
This tool creates multiple Blog Author objects based on the provided request details. It's useful for adding several blog authors at once to the HubSpot CMS.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | |||
Create a language variation for a blog in HubSpot CMS.
This tool allows you to create a new language variation for an existing blog using HubSpot CMS's multi-language settings. Use it when you need to support multiple languages for a blog. | |||
Create a new blog post with specified content.
Use this tool to create a new blog post by specifying its content in the request. Ideal for automating blog publishing processes.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. |
Selected tools
No tools selected.
Click "Show all tools" to add tools.
Requirements
Select tools to see requirements
HubspotCmsApi.AddHubdbTableRow
Add a new row to a HubDB draft table. Use this tool to add a new row to the draft version of a HubDB table. To make these changes live, publish the table afterwards. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
target_table_id_or_name | string | Optional | The ID or name of the target HubDB table to add the row to. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/rows_createTableRow'.HubspotCmsApi.ArchiveBlogTags
Archive multiple blog tags in HubSpot CMS. Use this tool to delete multiple blog tag objects in HubSpot CMS by providing their identifiers. Suitable for cleaning up unused or obsolete tags in batches.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_tag_identifiers | array<string> | Required | An array of strings representing the blog tag identifiers to be archived. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/tags/batch/archive_archiveBatch'.HubspotCmsApi.ArchiveHubdbTable
Archive a HubDB table in HubSpot CMS. Use this tool to archive (soft delete) an existing HubDB table in HubSpot CMS, affecting both published and draft versions.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
hubdb_table_identifier | string | Required | The ID or name of the HubDB table to archive. Provides the reference needed to identify the table within the system. |
Requirements
Output
json— Response from the API endpoint 'delete-/cms/v3/hubdb/tables/{tableIdOrName}_archiveTable'.HubspotCmsApi.AttachAuthorToMultilangGroup
Attach a Blog Author to a multi-language group. Use this tool to link a specific blog author with a multi-language group in HubSpot CMS. This action helps manage authors across different language variations of your blog.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
author_object_id | string | Required | ID of the blog author to add to a multi-language group in HubSpot CMS. |
designated_language | string | Required | The language code of the blog author to be added to a multi-language group, e.g., 'en' for English. |
primary_language_object_id | string | Required | ID of the primary language object in the multi-language group. |
primary_language | string | Optional | Specify the primary language of the multi-language group to which the author will be attached. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/authors/multi-language/attach-to-lang-group_attachToLangGroup'.HubspotCmsApi.AttachBlogPostToLanguageGroup
Attach a blog post to a multi-language group in HubSpot CMS. Use this tool to attach a specific blog post to a multi-language group in HubSpot CMS, enabling content localization and management.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
designated_language | string | Required | Specify the language code (e.g., 'en', 'fr', 'es') for the blog post to be added to the multi-language group. |
object_id | string | Required | The ID of the blog post to attach to a multi-language group. |
primary_language_object_id | string | Required | ID of the primary language object in the multi-language group. |
primary_language | string | Optional | Primary language of the multi-language group. Specify in ISO language code format (e.g., 'en', 'fr'). |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/multi-language/attach-to-lang-group_attachToLangGroup'.HubspotCmsApi.AttachBlogToLanguageGroup
Attach a blog to a multi-language group in HubSpot CMS. Use this tool to attach a blog to a specified multi-language group within HubSpot CMS. It is helpful when managing blogs in different languages and ensuring they are correctly grouped.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
designated_language | string | Required | The language code of the blog to add to a multi-language group. Use standard language codes like 'en', 'fr', etc. |
object_id_to_add | string | Required | ID of the blog object to be added to a multi-language group in HubSpot CMS. |
primary_language_object_id | string | Required | ID of the primary language object in the multi-language group to which the blog will be attached. |
primary_language | string | Optional | Primary language code for the multi-language group to which the blog should be attached (e.g., 'en', 'fr'). |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blog-settings/settings/multi-language/attach-to-lang-group'.HubspotCmsApi.AttachLandingPageToLanguageGroup
Attach a landing page to a multi-language group. Use this tool to associate a landing page with an existing multi-language group, enabling better management of language variations within HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
designated_language_to_add | string | Required | The language of the landing page to add to a multi-language group. Expect a language code. |
object_id_for_language_group | string | Required | ID of the landing page to add to the multi-language group. |
primary_language_object_id | string | Required | Provide the ID of the primary language object in the multi-language group to which the landing page will be attached. |
primary_language | string | Optional | Specifies the primary language of the multi-language group to which the landing page will be attached. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/multi-language/attach-to-lang-group_attachToLangGroup'.HubspotCmsApi.AttachPageToLanguageGroup
Attach a site page to a multi-language group. Use this tool to attach a specific site page to an existing multi-language group, enabling multi-language support for that page.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
object_id_to_add_to_language_group | string | Required | ID of the site page object to add to a multi-language group. |
page_language | string | Required | Designated language code (e.g., 'en', 'fr') of the page to add to a multi-language group. |
primary_language_object_id | string | Required | ID of the primary language object in the multi-language group to which the page will be attached. |
primary_language_of_group | string | Optional | Specify the primary language for the multi-language group. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/multi-language/attach-to-lang-group_attachToLangGroup'.HubspotCmsApi.AttachTagToLanguageGroup
Attach a blog tag to a multi-language group. Use this tool to connect a specific blog tag to a designated multi-language group within HubSpot CMS. This is useful for managing tags across different language versions of a blog.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
designated_language | string | Required | Specify the language of the blog tag to add to a multi-language group. Use a language code like 'en' for English. |
object_id_for_multilanguage_group | string | Required | ID of the blog tag to add to the multi-language group. |
primary_language_object_id | string | Required | ID of the primary language object in the multi-language group. |
primary_language | string | Optional | Specifies the primary language of the multi-language group. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/tags/multi-language/attach-to-lang-group_attachToLangGroup'.HubspotCmsApi.BatchUpdateTableRowsHubspot
Update multiple draft table rows in HubSpot CMS. This tool updates up to 100 rows in the draft version of a specified HubSpot CMS table. Use it when you need to apply changes to several rows at once in a draft table. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
table_id_or_name | string | Optional | The ID or name of the table to update rows in the draft version. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/rows/draft/batch/update_updateDraftTableRows'.HubspotCmsApi.CheckExtractionStatus
Retrieve the current status of a source-code extraction task. Use this tool to check the status of a specific source-code extraction by providing the `taskId`. It's useful for tracking the progress of an extraction after initiating it with the `extract/async` request.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
extraction_task_id | integer | Required | The unique ID of the extraction task, obtained from the initial `extract/async` request. This ID is required to check the status of the extraction. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/source-code/extract/async/tasks/{taskId}/status_getAsyncStatus'.HubspotCmsApi.CloneBlogPost
Creates a copy of an existing blog post. This tool clones an existing blog post, creating a new copy with the same content. It should be used when you want to duplicate a post for editing or reuse.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | ID of the blog post to be cloned. This identifies the specific blog post you want to duplicate. |
cloned_blog_post_name | string | Optional | The name for the newly cloned blog post. This is how the cloned post will be titled or identified. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/clone_clone'.HubspotCmsApi.CloneDraftTableRowsHubspot
Clone rows in a draft HubDB table by row IDs. Use this tool to clone specific rows in the draft version of a HubDB table by providing up to 100 row IDs. Useful for duplicating data entries during content management in HubSpot's CMS. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
hubdb_table_id_or_name | string | Optional | The ID or name of the HubDB table to clone rows from. Specify either the unique table ID or its name. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/rows/draft/batch/clone_cloneDraftTableRows'.HubspotCmsApi.CloneHubdbDraftRow
Clone a single row in a HubDB draft table. Use this tool to clone a specific row in the draft version of a HubDB table within HubSpot CMS. This is helpful for duplicating draft content before finalizing changes.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
row_id_to_clone | string | Required | The ID of the row to be cloned in the draft table. |
table_id_or_name | string | Required | The ID or name of the table to be cloned. |
new_row_name | string | Optional | The name for the cloned row. Specify a new name if required. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/rows/{rowId}/draft/clone_cloneDraftTableRow'.HubspotCmsApi.CloneHubdbTable
Clone an existing HubDB table as a draft. Use this tool to create a draft clone of an existing HubDB table. The new table's name and label can be specified.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
copy_rows | boolean | Required | Boolean indicating whether to copy the rows during the cloning process. |
is_hubspot_defined | boolean | Required | Indicate if the table is defined by HubSpot. This is a boolean value where true means the table is HubSpot-defined. |
source_table_id_or_name | string | Required | The ID or name of the HubDB table to clone. |
new_table_label | string | Optional | The label for the new cloned table. Specify a descriptive label for identification. |
new_table_name | string | Optional | The desired new name for the cloned HubDB table draft. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/draft/clone_cloneDraftTable'.HubspotCmsApi.CloneLandingPageHubspot
Clone a landing page in HubSpot CMS. This tool duplicates an existing landing page within HubSpot's CMS. It should be used when you need an exact replica of a landing page for further customization or testing.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | ID of the landing page to be cloned. Required for identifying the source page. |
cloned_landing_page_name | string | Optional | The name to assign to the newly cloned landing page in HubSpot CMS. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/clone_clone'.HubspotCmsApi.CloneSitePage
Clone an existing site page in HubSpot CMS. This tool is used to clone an existing site page within the HubSpot CMS. It is useful when duplicating pages for updates or creating similar content quickly.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
object_id_to_clone | string | Required | ID of the site page to be cloned in HubSpot CMS. |
clone_name | string | Optional | The desired name for the cloned site page object. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/clone_clone'.HubspotCmsApi.CreateAbTestVariation
Create a new A/B test variation in HubSpot CMS. This tool allows you to create a new A/B test variation for a landing page using HubSpot CMS. It should be called when you need to perform A/B testing by generating different page variations to assess their performance.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
ab_test_variation_name | string | Required | The name of the A/B test variation to be created. |
object_test_id | string | Required | The ID of the object to be tested in the A/B test variation. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/ab-test/create-variation_createABTestVariation'.HubspotCmsApi.CreateAttentionSpanEvent
Log viewer's attention span details for media events. This tool creates an event recording viewer attention span details for media, which helps in tracking engagement and interaction levels. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/media-bridge/v1/events/attention-span'.HubspotCmsApi.CreateBatchBlogPosts
Create multiple blog posts in a single request. This tool is used to create a batch of blog posts by specifying their content in the request body. It should be called when you need to publish multiple blog posts at once. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/batch/create_create'.HubspotCmsApi.CreateBlogAuthor
Create a new Blog Author in HubSpot CMS. Use this tool to create a new blog author within the HubSpot CMS. It should be called when you need to add an author to your blog system. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/authors_create'.HubspotCmsApi.CreateBlogAuthorLanguageVariation
Create a language variation for a blog author. This tool creates a new language variation from an existing blog author in HubSpot CMS, allowing for multilingual content management. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/authors/multi-language/create-language-variation_createLangVariation'.HubspotCmsApi.CreateBlogAuthorsBatch
Create multiple blog authors in a single batch request. This tool creates multiple Blog Author objects based on the provided request details. It's useful for adding several blog authors at once to the HubSpot CMS. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/authors/batch/create_createBatch'.HubspotCmsApi.CreateBlogLanguageVariation
Create a language variation for a blog in HubSpot CMS. This tool allows you to create a new language variation for an existing blog using HubSpot CMS's multi-language settings. Use it when you need to support multiple languages for a blog.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_id | string | Required | ID of the blog to clone for creating a language variation. |
blog_slug | string | Optional | Path to the blog. Used to specify the location of the language variation within the CMS. |
primary_language | string | Optional | Specify the language of the primary blog to clone. This determines the source content for the new language variation. |
target_language_for_blog_variant | string | Optional | The language code for the new blog variant, specifying the target language for translation. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blog-settings/settings/multi-language/create-language-variation'.HubspotCmsApi.CreateBlogPost
Create a new blog post with specified content. Use this tool to create a new blog post by specifying its content in the request. Ideal for automating blog publishing processes. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts_create'.HubspotCmsApi.CreateBlogTag
Create a new blog tag in HubSpot CMS. This tool creates a new tag for a blog in the HubSpot CMS. It should be called when there's a need to categorize or organize content within the blog by creating new tags.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_tag_unique_id | string | Required | The unique ID assigned to the Blog Tag. |
creation_timestamp | string | Required | The timestamp (ISO8601 format) when this Blog Tag was created. Leave empty if not applicable. |
deletion_timestamp | string | Required | The ISO8601 timestamp marking when the blog tag was deleted. |
language_code | string | Required | The explicit ISO 639 language code for the tag, such as 'en' for English or 'es' for Spanish. |
primary_tag_translation_id | integer | Required | Specify the ID of the primary tag that this tag was translated from. |
tag_name | string | Required | The name for the new blog tag to be created in HubSpot CMS. |
updated_timestamp | string | Required | The timestamp (ISO8601 format) when the Blog Tag was last updated. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/tags_create'.HubspotCmsApi.CreateBlogTagLanguageVariation
Create a new language variation from an existing blog tag. Use this tool to create a language variation for an existing blog tag on HubSpot CMS. Call this tool when you need to support multiple languages for blog tags.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_tag_id | string | Required | ID of the existing blog tag to be cloned for creating a language variation. |
new_blog_tag_name | string | Required | The name for the newly cloned blog tag language variation. |
primary_blog_tag_language | string | Optional | Specify the language code of the primary blog tag to be cloned, such as 'en', 'fr', etc. |
target_language_for_blog_tag_variation | string | Optional | Specifies the target language for the new blog tag variant. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/tags/multi-language/create-language-variation_createLangVariation'.HubspotCmsApi.CreateBlogTagsBatch
Create multiple blog tags in a single request. This tool is used to create multiple blog tag objects as specified in the request body. Call this tool when you need to add several blog tags at once to a HubSpot CMS blog. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/tags/batch/create_createBatch'.HubspotCmsApi.CreateDraftTableRows
Create draft rows in a specified HubSpot table. This tool is used to add multiple rows to the draft version of a specified HubSpot CMS table. It allows for up to 100 rows to be created in one call. Useful for updating content drafts before publication. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
table_id_or_name | string | Optional | The ID or name of the HubSpot table to which the draft rows are being added. This is required to specify which table you want to update. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/rows/draft/batch/create_createDraftTableRows'.HubspotCmsApi.CreateHubdbTable
Create a new draft HubDB table with a unique name and label. This tool creates a new draft HubDB table using a provided JSON schema. It requires that the table name and label be unique within each account. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables_createTable'.HubspotCmsApi.CreateLandingPage
Create a new landing page in HubSpot. Use this tool to create a new landing page on HubSpot. Suitable for automating marketing or content management tasks. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages_create'.HubspotCmsApi.CreateLandingPageFolder
Create a new folder in HubSpot CMS for landing pages. This tool is used to create a new folder within the landing pages section of HubSpot CMS. Call this tool when you need to organize landing pages into a new folder structure.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
deletion_timestamp | string | Required | The ISO8601 timestamp indicating when the folder was deleted. Leave this empty if the folder is active. |
folder_category | integer | Required | The type of object this folder applies to. Must be set to LANDING_PAGE. |
folder_creation_date | string | Required | The ISO8601 timestamp when this folder was created. |
folder_name | string | Required | The name of the folder to display in the app dashboard. |
folder_unique_id | string | Required | The unique identifier for the content folder. This is a string that serves as the primary key for the folder. |
parent_folder_id | integer | Required | The ID of the parent content folder under which the new folder will be nested. |
updated_timestamp | string | Required | The timestamp in ISO8601 format indicating when the folder was last updated. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/folders_createFolder'.HubspotCmsApi.CreateLandingPageFolders
Create multiple landing page folders in HubSpot CMS. Use this tool to create multiple folder objects for landing pages in HubSpot CMS as specified in the request details. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/folders/batch/create_createFolders'.HubspotCmsApi.CreateLandingPages
Create multiple landing pages in HubSpot CMS. Use this tool to create a batch of new landing pages in HubSpot CMS by providing the necessary details in the request body. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/batch/create_createBatch'.HubspotCmsApi.CreateLanguageVariation
Create a new language variation for a site page. Use this tool to create a new language variation from an existing site page in HubSpot CMS. It helps in managing multilingual content efficiently by generating a language-specific page version.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
content_id_to_clone | string | Required | ID of the site page content to clone for creating a language variation. |
primary_content_language | string | Optional | Specify the language of the primary content to clone for creating the variation. |
target_language | string | Optional | Target language code for the new site page variant, e.g., 'fr' for French. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/multi-language/create-language-variation_createLangVariation'.HubspotCmsApi.CreateMediaPlayedEvent
Log an event when media playback starts. Call this tool when you need to create an event for when a user begins playing a piece of media. It helps track media interactions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/media-bridge/v1/events/media-played'.HubspotCmsApi.CreateMultilanguageLandingPage
Create a new language variation for a landing page. This tool creates a new language variation from an existing landing page in HubSpot CMS. Use it to generate multilingual versions of your landing pages.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
content_id_to_clone | string | Required | The ID of the landing page content to be cloned for creating a new language variation. |
primary_language_of_content | string | Optional | Language code of the primary content to be cloned for creating the new language variation. |
target_language | string | Optional | Specify the target language for the new landing page variant. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/multi-language/create-language-variation_createLangVariation'.HubspotCmsApi.CreateSitePage
Create a new site page in HubSpot CMS. This tool is used to create a new site page in HubSpot CMS. It should be called when a user wants to add a new page to their website using the HubSpot platform. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages_create'.HubspotCmsApi.CreateSitePagesBatch
Create multiple site page objects in batch. Use this tool to create multiple site page objects at once based on the details provided in the request body. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/batch/create_createBatch'.HubspotCmsApi.CreateUrlRedirect
Creates and configures a new URL redirect in HubSpot CMS. Use this tool to create and set up a new URL redirect within the HubSpot CMS. Ideal for managing website redirects effectively.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
redirect_destination_url | string | Required | The target URL to which the redirect will point. This should be a valid and complete URL. |
redirect_style | integer | Required | Integer indicating the style of the redirect. Defines the behavior and type of the redirect, such as permanent (301) or temporary (302). |
route_prefix | string | Required | Defines the prefix for the URL route to be redirected. Provide the specific path without the domain, e.g., '/example-path'. |
apply_only_after_not_found | boolean | Optional | Applies the redirect only after a 404 Not Found response if true. |
enable_pattern_matching | boolean | Optional | Set to true to enable URL pattern matching for the redirect. False matches exact URLs only. |
enable_protocol_agnostic | boolean | Optional | Set to true to ignore the protocol (HTTP/HTTPS) when matching URLs. Enables protocol-agnostic redirects. |
ignore_trailing_slash | boolean | Optional | Set to true to ignore trailing slashes, allowing flexibility in URL matches. |
match_full_url | boolean | Optional | Set to true to match the entire URL exactly. False applies partial matching. |
match_query_string | boolean | Optional | Indicates whether the redirect should match the query string. Set to true to match, false to ignore. |
redirect_precedence | integer | Optional | An integer indicating the priority of the redirect if multiple rules match. Higher numbers take precedence. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/url-redirects/_create'.HubspotCmsApi.DeleteBlogAuthor
Delete a specific blog author by ID. Use this tool to delete a blog author from the HubSpot CMS by providing their ID. It should be called when you need to remove an author from the system.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_author_id | string | Required | The unique identifier of the Blog Author to be deleted. |
return_archived_only | boolean | Optional | Set to true to return only archived blog authors. Use for fetching deleted or inactive authors. |
Requirements
Output
json— Response from the API endpoint 'delete-/cms/v3/blogs/authors/{objectId}_archive'.HubspotCmsApi.DeleteBlogAuthors
Delete specified blog authors in HubSpot CMS. Use this tool to delete the Blog Author objects identified in the request body from HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_author_ids | array<string> | Required | List of blog author IDs to delete from HubSpot CMS. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/authors/batch/archive_archiveBatch'.HubspotCmsApi.DeleteBlogPost
Delete a blog post by its unique ID. Use this tool to delete a blog post using its ID. Note that this action permanently removes the post, unlike the in-app archive function. For dashboard archiving, use an update with `archivedInDashboard` set to `true`.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_ids_to_delete | array<string> | Required | An array of blog post IDs to delete. Each ID should be a string representing a unique blog post. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/batch/archive_archive'.HubspotCmsApi.DeleteBlogTag
Delete a specified Blog Tag in HubSpot CMS. Use this tool to delete a specific Blog Tag in the HubSpot CMS by providing the object's ID. This is useful for managing and organizing blog content within the CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_tag_id | string | Required | The unique identifier for the Blog Tag to be deleted. |
return_only_archived_results | boolean | Optional | Set to true to return only blog tags that have been archived. |
Requirements
Output
json— Response from the API endpoint 'delete-/cms/v3/blogs/tags/{objectId}_archive'.HubspotCmsApi.DeleteCmsSitePages
Delete specified Site Page objects in the CMS. This tool deletes the Site Page objects specified in the request body on the HubSpot CMS. It is used when you need to remove multiple site pages at once. This operation is different from archiving in the dashboard.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
page_ids_to_delete | array<string> | Required | An array of strings representing the IDs of the Site Page objects to delete. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/batch/archive_archiveBatch'.HubspotCmsApi.DeleteDraftTableRowHubspot
Permanently delete a row from a HubDB draft table. Use this tool to permanently delete a specified row from the draft version of a HubDB table in HubSpot CMS. Call this tool when you need to remove a row that is no longer needed in the draft.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
row_id | string | Required | The unique ID of the row to be permanently deleted from the draft version of the HubDB table. |
table_id_or_name | string | Required | The ID or name of the HubDB table from which the draft row will be deleted. |
Requirements
Output
json— Response from the API endpoint 'delete-/cms/v3/hubdb/tables/{tableIdOrName}/rows/{rowId}/draft_purgeDraftTableRow'.HubspotCmsApi.DeleteFileInCmsEnvironment
Deletes a file in a specified CMS environment. Use this tool to delete a file located at a specific path within a designated CMS environment. It's useful for managing and organizing source code by removing unnecessary or outdated files.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
file_environment | string | Required | Specify the environment of the file to delete. Valid values are "draft" or "published". |
file_system_location | string | Required | The file system location of the file to be deleted. |
Requirements
Output
json— Response from the API endpoint 'delete-/cms/v3/source-code/{environment}/content/{path}_archive'.HubspotCmsApi.DeleteLandingPage
Delete a specified landing page by its ID. Use this tool to delete a landing page in HubSpot CMS by providing the landing page's ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The unique identifier of the landing page to delete in HubSpot CMS. |
return_archived_results_only | boolean | Optional | Set to true to only return results that have been archived. |
Requirements
Output
json— Response from the API endpoint 'delete-/cms/v3/pages/landing-pages/{objectId}_archive'.HubspotCmsApi.DeleteLandingPageFolder
Deletes a CMS landing page folder by ID. Use this tool to delete a specific CMS landing page folder by providing its object ID. The tool sends a DELETE request to remove the folder.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
folder_id | string | Required | The ID of the folder to be deleted. Provide the specific ID of the CMS landing page folder you wish to delete. |
return_only_archived_results | boolean | Optional | Set to true to return only archived results. |
Requirements
Output
json— Response from the API endpoint 'delete-/cms/v3/pages/landing-pages/folders/{objectId}_archiveFolder'.HubspotCmsApi.DeleteLandingPageFolders
Delete specified landing page folders in HubSpot CMS. Use this tool to delete landing page folders in the HubSpot CMS as specified in the request. It should be called when you need to remove these folders from the CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
folder_identifiers | array<string> | Required | An array of strings representing the identifiers of the folders to be deleted. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/folders/batch/archive_archiveFolders'.HubspotCmsApi.DeleteLandingPages
Deletes specified HubSpot landing pages permanently. Use this tool to permanently delete landing page objects in HubSpot CMS. It's different from archiving pages via the dashboard. Ensure you provide the specific page identifiers in the request body.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_ids | array<string> | Required | An array of strings representing the IDs of landing pages to delete permanently. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/batch/archive_archiveBatch'.HubspotCmsApi.DeleteSitePage
Delete a specified site page in HubSpot CMS. Use this tool to delete a specific site page in HubSpot CMS by providing the page's object ID. This should be called when a page needs to be archived or removed permanently.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
site_page_id | string | Required | The unique identifier for the site page to be deleted in HubSpot CMS. |
return_only_archived_results | boolean | Optional | Set to true to return only the pages that have been archived. |
Requirements
Output
json— Response from the API endpoint 'delete-/cms/v3/pages/site-pages/{objectId}_archive'.HubspotCmsApi.DeleteTableVersion
Delete a specific version of a HubDB table. This tool deletes a specified version of a table in HubSpot CMS HubDB. It should be called when you need to remove an obsolete or incorrect version of a table. Make sure to specify the correct table and version identifiers.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
table_identifier | string | Required | The unique ID or name of the HubDB table whose version you want to delete. |
table_version_id | integer | Required | Specify the ID of the table version to delete. This should be an integer value that identifies a specific version in HubDB. |
Requirements
Output
json— Response from the API endpoint 'delete-/cms/v3/hubdb/tables/{tableIdOrName}/versions/{versionId}_removeTableVersion'.HubspotCmsApi.DeleteUrlRedirect
Deletes an existing URL redirect in HubSpot CMS. Utilize this tool to delete a specific URL redirect within the HubSpot CMS system. This should be called when you need to remove a redirect mapping from the system.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
url_redirect_id | string | Required | The unique identifier of the URL redirect to be deleted within the HubSpot CMS. |
Requirements
Output
json— Response from the API endpoint 'delete-/cms/v3/url-redirects/{urlRedirectId}_archive'.HubspotCmsApi.DetachBlogAuthorFromLangGroup
Detach a Blog Author from a multi-language group. Use this tool to remove a blog author from an existing multi-language group in HubSpot CMS. Call this when authors need to be unlinked from specific language variations.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
author_id_to_detach | string | Required | ID of the blog author to remove from a multi-language group in HubSpot CMS. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/authors/multi-language/detach-from-lang-group_detachFromLangGroup'.HubspotCmsApi.DetachBlogFromLanguageGroup
Detach a blog from its multi-language group. Use this tool to separate a blog from its associated multi-language group settings in HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
object_id_to_detach | string | Required | ID of the blog to remove from its multi-language group in HubSpot CMS. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blog-settings/settings/multi-language/detach-from-lang-group'.HubspotCmsApi.DetachBlogPostLanguageGroup
Detach a blog post from a multi-language group. Use this tool to detach a specific blog post from its associated multi-language group in HubSpot CMS. Useful when you need to separately manage or remove language-specific versions of a post.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
object_id_to_detach_from_language_group | string | Required | ID of the blog post to be removed from the multi-language group. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/multi-language/detach-from-lang-group_detachFromLangGroup'.HubspotCmsApi.DetachBlogTagFromLanguageGroup
Detach a Blog Tag from a multi-language group. Use this tool to remove a blog tag from its association with a multi-language group in HubSpot CMS. This can be useful when restructuring tags or changing their multi-language settings.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_tag_id | string | Required | ID of the blog tag to remove from a multi-language group in HubSpot CMS. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/tags/multi-language/detach-from-lang-group_detachFromLangGroup'.HubspotCmsApi.DetachLandingPageFromLanguageGroup
Detach a landing page from a multi-language group. Call this tool to detach a specific landing page from its multi-language group in HubSpot CMS. Useful for managing language-specific versions of pages individually.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The ID of the landing page to detach from the multi-language group in HubSpot CMS. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/multi-language/detach-from-lang-group_detachFromLangGroup'.HubspotCmsApi.DetachSitePageFromLanguageGroup
Detach a site page from a multi-language group. Use this tool to detach a site page from its current multi-language group when language-specific customization is needed.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
object_id_to_detach | string | Required | The ID of the site page to detach from the multi-language group. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/multi-language/detach-from-lang-group_detachFromLangGroup'.HubspotCmsApi.DownloadFileFromHubspotCms
Download file content from HubSpot CMS by path and environment. Use this tool to download the byte contents of a file stored in HubSpot CMS. Specify the environment and path to retrieve the desired file content.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
file_environment | string | Required | Specify the environment of the file. Options are 'draft' or 'published'. |
file_system_path | string | Required | The file system path to the file within HubSpot CMS to be downloaded. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/source-code/{environment}/content/{path}_download'.HubspotCmsApi.EndAbTestSelectWinner
End an active A/B test and designate a winner. Use this tool to end an ongoing A/B test for landing pages and select the winning variant. Ideal for finalizing tests and applying successful strategies.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
test_id_to_end | string | Required | ID of the A/B test to be ended. |
winner_object_id | string | Required | ID of the landing page variant to designate as the winner of the A/B test. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/ab-test/end_endActiveABTest'.HubspotCmsApi.EndActiveAbTest
End an active A/B test and designate a winner. Use this tool to conclude an ongoing A/B test and specify the winning variant on the HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
test_id_to_end | string | Required | The unique identifier of the A/B test that you want to conclude in the HubSpot CMS. |
winner_id | string | Required | The ID of the object to designate as the winner of the A/B test. This should match the ID used in the CMS to identify the specific variant. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/ab-test/end_endActiveABTest'.HubspotCmsApi.ExportHubdbDraftTable
Export HubDB draft table to CSV or Excel format. Use this tool to export the draft version of a HubDB table in HubSpot CMS to a CSV or Excel file. Call this tool when you need to download table data for review or offline use.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
table_id_or_name | string | Required | The ID or name of the table to export. Use this to specify the exact table you want to download. |
export_file_format | string | Optional | The file format for exporting the draft table. Choose from `CSV`, `XLSX`, or `XLS`. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/hubdb/tables/{tableIdOrName}/draft/export_exportDraftTable'.HubspotCmsApi.ExportTableFromHubdb
Exports a HubDB table in the desired format. Use this tool to export the published version of a HubDB table by specifying the table ID or name. It allows exporting in various formats.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
hubdb_table_id_or_name | string | Required | The ID or name of the HubDB table to export. |
file_format_to_export | string | Optional | The file format for exporting the table. Options are `CSV`, `XLSX`, and `XLS`. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/hubdb/tables/{tableIdOrName}/export_exportTable'.HubspotCmsApi.ExtractZipFileAsync
Initiate asynchronous extraction of a zip file on HubSpot CMS. This tool initiates the extraction of a zip file in the developer file system asynchronously. This is useful for handling large files or files that need processing without blocking operations. Use this tool when you need to start a zip file extraction and check its status later through the appropriate status endpoint.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
zip_file_path | string | Required | The path to the zip file in the developer file system that needs extraction. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/source-code/extract/async_doAsync'.HubspotCmsApi.FetchHubdbTableRows
Fetch rows from a HubDB table using filters and sorting. Use this tool to fetch rows from a specific HubDB table. You can apply filters and sorting by using query parameters, allowing retrieval of customized data sets. No authentication is needed if the table allows public access.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
table_identifier | string | Required | The ID or name of the HubDB table to query for fetching row data. |
include_archived_rows | boolean | Optional | Set to true to include archived rows in the results; false to exclude them. |
maximum_results_limit | integer | Optional | Specifies the maximum number of results to return. The default value is 1000, which can be adjusted to retrieve fewer entries. |
pagination_cursor_token | string | Optional | Cursor token to fetch the next set of results. Obtainable from the `paging.next.after` of a paged response. |
requested_columns | array<string> | Optional | Specify column names to retrieve only the required columns' data, excluding others. |
row_offset | integer | Optional | The starting point for fetching a subset of rows, useful for pagination. It's similar to specifying which row to start fetching from. |
sort_columns | array<string> | Optional | List of column names to sort the results by. Each entry is a string representing a column. Prefix with '-' for descending order. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/hubdb/tables/{tableIdOrName}/rows_getTableRows'.HubspotCmsApi.FetchUrlRedirects
Retrieve all URL redirects with optional filters. Use this tool to access a list of all existing URL redirects in the HubSpot CMS. You can apply filters based on creation or updated date to narrow down the results.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
created_after_date | string | Optional | Return redirects created after this date (format: YYYY-MM-DD). |
created_at | string | Optional | Return redirects created exactly on this date. Format: YYYY-MM-DD. |
filter_by_exact_update_date | string | Optional | Return redirects last updated on this exact date. Use a valid date format (e.g., YYYY-MM-DD). |
filter_created_before_date | string | Optional | Return redirects created before this date. Expected format: YYYY-MM-DD. |
filter_updated_after | string | Optional | Only include redirects updated after this specified date (ISO 8601 format). |
paging_cursor_token | string | Optional | Token for the last read resource to fetch additional results. |
results_per_page_limit | integer | Optional | Maximum number of URL redirects to return per page. Use to control pagination. |
return_archived_only | boolean | Optional | Set to true to return only archived URL redirects, false to exclude them. |
sort_criteria | array<string> | Optional | Specify fields to sort the URL redirects by. Can include multiple fields such as 'createdAt' or 'updatedAt'. |
updated_before_date | string | Optional | Only return redirects last updated before this date (in YYYY-MM-DD format). |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/url-redirects/_getPage'.HubspotCmsApi.GetAllDraftTablesDetails
Retrieve details of all draft HubDB tables. Returns information on all draft tables in a specified HubSpot account, including column definitions.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
content_type | string | Optional | Specify the content type filter for retrieving draft tables. Leave empty for no filter. |
created_after_date | string | Optional | Return tables created after the specified date and time. Format: YYYY-MM-DDTHH:MM:SSZ. |
created_at_exact_time | string | Optional | Return tables created at the specified exact time (ISO 8601 format). |
created_before_date | string | Optional | Return tables created before this specified time. |
filter_by_updated_before_date | string | Optional | Return tables last updated before this specified time in ISO 8601 format. |
include_archived_tables | boolean | Optional | Set to true to include archived tables in the results, false by default. |
include_localized_schema | boolean | Optional | Indicates whether to include localized schema information for draft tables. Accepts a boolean value. |
maximum_results_limit | integer | Optional | Specifies the maximum number of draft table results to return, with a default of 1000. |
pagination_cursor_token | string | Optional | Cursor token to fetch the next set of results from a paginated response. |
return_tables_updated_after | string | Optional | Only return tables that were last updated after the specified timestamp (ISO 8601 format). |
sort_fields_for_results | array<string> | Optional | Fields to sort the results by. Valid fields are `name`, `createdAt`, `updatedAt`, `createdBy`, `updatedBy`. Defaults to `createdAt`. |
updated_at_specific_time | string | Optional | Return tables last updated at the specified exact time. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/hubdb/tables/draft_getAllDraftTables'.HubspotCmsApi.GetAllHubdbTables
Retrieve details of all published HubDB tables. This tool returns the details and column definitions for all published HubDB tables in a HubSpot account. It is useful when you need an overview of the schema and data of all tables within your CMS environment.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
content_type_filter | string | Optional | Filter tables by the specified content type to return only those matching it. |
created_after | string | Optional | Return tables created after the specified time in ISO 8601 format. |
created_before_timestamp | string | Optional | Return tables created before this timestamp. Format should be in ISO 8601. |
cursor_token_for_next_results | string | Optional | The cursor token to retrieve the next set of results. Obtain this from the `paging.next.after` in a paged response. |
filter_by_creation_time | string | Optional | Return tables created at the specified time. Format: ISO 8601. |
include_archived_tables | boolean | Optional | Specifies whether to include archived tables in the results. Defaults to `false`. |
include_localized_schema | boolean | Optional | Include localized schema details in the response if true. |
last_updated_exact_time | string | Optional | Only return tables last updated at exactly the specified time, formatted as a string. |
max_table_results | integer | Optional | Maximum number of HubDB table results to return. Default is 1000. |
sort_fields | array<string> | Optional | Specify fields for sorting results: `name`, `createdAt`, `updatedAt`, `createdBy`, `updatedBy`. Defaults to `createdAt`. |
updated_after_timestamp | string | Optional | Return tables last updated after this timestamp. Format: 'YYYY-MM-DDTHH:MM:SSZ'. |
updated_before_time | string | Optional | Return tables updated before this specific time. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/hubdb/tables_getAllTables'.HubspotCmsApi.GetBlogAuthorById
Retrieve blog author details using an object ID. This tool fetches details of a blog author from HubSpot CMS using the specified object ID. It should be called when specific information about a blog author is needed.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_author_id | string | Required | The unique identifier for the blog author to retrieve their details. |
include_deleted_blog_authors | boolean | Optional | Set to true to include deleted blog authors in the results. Defaults to false. |
specific_author_property | string | Optional | Specify a property to retrieve specific details about the blog author, such as a specific attribute or field. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blogs/authors/{objectId}_getById'.HubspotCmsApi.GetBlogAuthors
Retrieve the list of blog authors. Use this tool to get a list of blog authors for integration, with support for paging and filtering. Useful for examining authors to suggest edits via external services.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
created_after | string | Optional | Return only blog authors created after this specified timestamp. |
created_at_exact_time | string | Optional | Return blog authors created at exactly the specified time. Use ISO 8601 format for timestamps. |
filter_by_creation_before_date | string | Optional | Return Blog Authors created before the specified date and time in ISO 8601 format. |
filter_by_last_updated_before | string | Optional | Only return blog authors last updated before the specified timestamp. Format: YYYY-MM-DDTHH:MM:SSZ. |
filter_by_updated_after | string | Optional | Return Blog Authors updated after a specific time. Use an ISO 8601 datetime string, e.g., '2023-01-01T00:00:00Z'. |
include_archived_authors | boolean | Optional | Specify `true` to include archived (deleted) blog authors in the results. Defaults to `false`. |
included_properties | string | Optional | Comma-separated list of specific properties to include in the response for each author. If empty, all properties will be fetched by default. |
pagination_cursor_token | string | Optional | The cursor token from `paging.next.after` to fetch the next set of results. |
result_limit | integer | Optional | Maximum number of blog authors to return. Default is 100. |
sort_fields | array<string> | Optional | Fields for sorting results. Choose from: `name`, `createdAt`, `updatedAt`, `createdBy`, `updatedBy`. Default is `createdAt`. |
updated_at_timestamp | string | Optional | Return blog authors last updated at the specified exact time (ISO 8601 format). |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blogs/authors_getPage'.HubspotCmsApi.GetBlogPostDraft
Retrieve the full draft version of a blog post. Use this tool to get the draft version of a specific blog post by providing the post's object ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The ID of the blog post to retrieve the draft version. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blogs/posts/{objectId}/draft_getDraftById'.HubspotCmsApi.GetBlogRevisionHistory
Retrieve the revision history of blog settings. This tool retrieves the historical revisions for the settings of a specified blog, providing insights into past configurations.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_id | string | Required | The unique identifier for the blog whose settings history is being retrieved. This is required for querying specific blog settings. |
retrieve_revisions_before_timestamp | string | Optional | Retrieve revisions before this timestamp in milliseconds since Unix Epoch. |
revision_limit | integer | Optional | The maximum number of blog setting revisions to retrieve. Provide an integer value to restrict the number of results. |
start_date_for_revisions | string | Optional | Specify a date to filter revisions that occurred after this date. Format: YYYY-MM-DD. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blog-settings/settings/{blogId}/revisions'.HubspotCmsApi.GetBlogSettings
Fetch blog settings using a blog ID. This tool retrieves the settings for a blog identified by the provided blog ID from the HubSpot CMS. It should be called when specific details or configurations of a blog are needed.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_id | string | Required | The unique identifier of the blog for which you want to fetch the settings. This is required to specify which blog's details to retrieve. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blog-settings/settings/{blogId}'.HubspotCmsApi.GetBlogTags
Retrieve a list of blog tags with paging and filtering options. This tool fetches the list of blog tags, supporting paging and filtering. It is useful for integrations that need to access blog tags for analysis or editing suggestions.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
additional_properties | string | Optional | Include additional fields in the response. Specify the properties you want to retrieve. |
created_after_time | string | Optional | Only return Blog Tags created after the specified time. Provide the time in ISO 8601 format. |
filter_by_creation_time | string | Optional | Filter blog tags to return only those created at the specified exact time. Use ISO 8601 format for the date-time. |
filter_tags_created_before | string | Optional | Only return blog tags created before the specified date and time in UTC, formatted as an ISO 8601 string. |
include_archived_tags | boolean | Optional | Specify whether to return deleted blog tags. Defaults to false. |
last_updated_before | string | Optional | Return blog tags updated before this date and time (in ISO 8601 format). |
maximum_results_to_return | integer | Optional | Specify the maximum number of blog tags to return. Default is 100. |
pagination_cursor_token | string | Optional | The token to retrieve the next set of results from a paginated response. Obtain this from the `paging.next.after` property in the previous response. |
sort_fields_for_results | array<string> | Optional | Fields to sort results by. Options: `name`, `createdAt`, `updatedAt`, `createdBy`, `updatedBy`. Default is `createdAt`. |
updated_after | string | Optional | Return Blog Tags last updated after the specified date and time. Provide in ISO 8601 format, e.g., '2023-10-21T15:30:00Z'. |
updated_at_exact | string | Optional | Return blog tags last updated at the specified exact time (ISO 8601 format). |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blogs/tags_getPage'.HubspotCmsApi.GetDomainById
Retrieve domain details by ID from HubSpot CMS. This tool retrieves detailed information about a specific domain using the provided domain ID from the HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
domain_id | string | Required | The unique ID of the domain to retrieve details for from HubSpot CMS. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/domains/{domainId}_getById'.HubspotCmsApi.GetDraftHubdbTableRows
Retrieve rows from a draft HubDB table with optional filtering. This tool fetches rows from the draft version of a specified HubDB table. It allows for filtering and sorting rows based on query parameters, helping to access only relevant data.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
table_id_or_name | string | Required | The ID or name of the HubDB table to query for draft rows. |
include_archived_rows | boolean | Optional | Specify whether to include archived rows in the results. Use `true` to include archived rows, `false` to exclude them. |
maximum_results_limit | integer | Optional | Specifies the maximum number of results to return from the draft table. Default is 1000. |
next_page_cursor | string | Optional | Cursor token to retrieve the next set of results, from `paging.next.after` in a paged response. |
result_offset | integer | Optional | The number of rows to skip before starting to collect the result set from the draft version of a table. |
sort_columns | array<string> | Optional | List of column names to sort the results by. Use format like ['column1', '-column2'] to specify ascending or descending order. |
specified_columns | array<string> | Optional | Specify the column names to return only these columns in the result, instead of all columns. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/hubdb/tables/{tableIdOrName}/rows/draft_readDraftTableRows'.HubspotCmsApi.GetDraftTableDetails
Retrieve details of a draft HubDB table by ID or name. Use this tool to get information about the draft version of a specific HubDB table, including column definitions and row count.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
table_id_or_name | string | Required | The ID or name of the HubDB table to retrieve draft details for. |
include_foreign_ids | boolean | Optional | Set this to `true` to populate foreign ID values in the result. |
include_localized_schema | boolean | Optional | Set to true to include the localized schema in the result. |
return_archived_table | boolean | Optional | Set to `true` to return an archived table. Defaults to `false`. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/hubdb/tables/{tableIdOrName}/draft_getDraftTableDetailsById'.HubspotCmsApi.GetDraftTableRowById
Retrieve a single draft row by ID from a HubDB table. This tool fetches a specific row's draft version from a HubDB table using the row ID. It should be called when a user needs to access draft data for a specific table row by ID or name.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
row_id | string | Required | The ID of the row in the table's draft version to retrieve. |
table_identifier | string | Required | The ID or name of the HubDB table to fetch the draft row from. |
include_archived | boolean | Optional | Set to true to include archived rows in the search result. Defaults to false. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/hubdb/tables/{tableIdOrName}/rows/{rowId}/draft_getDraftTableRowById'.HubspotCmsApi.GetExistingDomains
Retrieve all existing domains in the CMS. Fetches a list of all domains that have been created in the CMS, with optional filters by creation or update date.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
created_at_date_filter | string | Optional | Specify a date to return only domains created on this exact date. Format: YYYY-MM-DD. |
created_before_date | string | Optional | Filter to return only domains created before the specified date. Format: YYYY-MM-DD. |
filter_by_update_date | string | Optional | Only return domains updated on this specific date. Use 'YYYY-MM-DD' format. |
filter_domains_updated_after | string | Optional | Return domains updated after this specified date. Use ISO 8601 format (YYYY-MM-DD). |
filter_updated_before_date | string | Optional | Return only domains updated before this date in ISO 8601 format (e.g., '2023-10-05T00:00:00Z'). |
get_domains_created_after_date | string | Optional | Only return domains created after the specified date (in YYYY-MM-DD format). |
maximum_results_per_page | integer | Optional | Specifies the maximum number of domain results to return per page. |
paging_cursor_token | string | Optional | The paging cursor token of the last successfully read resource, used for paginated results. |
return_archived | boolean | Optional | Return only archived domains if true. Return unarchived if false. |
sort_criteria | array<string> | Optional | Defines the order of the domain results. Provide an array of strings specifying fields to sort by, such as ['createdAt', 'updatedAt']. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/domains/_getPage'.HubspotCmsApi.GetFileMetadata
Retrieve metadata for a file in a specified environment. Use this tool to obtain the metadata object for a file located at a specified path within a designated environment in the HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
file_environment | string | Required | Specify the environment of the file, either 'draft' or 'published'. |
file_path | string | Required | The file system location of the file to retrieve metadata for. |
include_properties | string | Optional | Comma-separated list of additional properties to include in the metadata response, if applicable. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/source-code/{environment}/metadata/{path}_get'.HubspotCmsApi.GetHubdbDraftRows
Fetch draft rows from a specified HubDB table. Use this tool to retrieve rows from the draft version of a specified HubDB table using a set of row IDs.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
row_ids | array<string> | Required | An array of row IDs to retrieve draft rows from the specified HubDB table. |
table_id_or_name | string | Required | ID or name of the HubDB table to retrieve draft rows from. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/rows/draft/batch/read_readDraftTableRows'.HubspotCmsApi.GetHubdbTableDetails
Get details of a HubDB table, including columns and row count. Use this tool to obtain comprehensive details about a specific HubDB table. It returns column definitions and the number of rows for the published version of the table. Accessible without authentication if the table is publicly available; requires HubSpot account ID in `portalId` query parameter.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
table_id_or_name | string | Required | The ID or name of the HubDB table to retrieve details for. |
get_localized_schema | boolean | Optional | Set to `true` to return the localized schema for the table. If `false`, returns the default schema. |
include_foreign_id_values | boolean | Optional | Set this to true to populate foreign ID values in the result. |
return_archived_table_details | boolean | Optional | Set to true to return details for an archived table. Defaults to false. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/hubdb/tables/{tableIdOrName}_getTableDetails'.HubspotCmsApi.GetLandingPageById
Retrieve details of a specific landing page by ID. Use this tool to fetch the details of a landing page from HubSpot CMS by providing the landing page's unique ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The unique identifier of the landing page to be retrieved. |
include_archived | boolean | Optional | Include deleted landing pages in the response if set to true. Defaults to false. |
landing_page_property | string | Optional | Specify which properties of the landing page to retrieve, such as 'title' or 'url'. Leave blank to fetch all. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/landing-pages/{objectId}_getById'.HubspotCmsApi.GetLandingPageDraft
Retrieve the full draft version of a landing page. Use this tool to get the complete draft version of a landing page by providing its object ID. Ideal for viewing or editing drafts before publishing.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The unique identifier for the Landing Page draft to be retrieved. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/landing-pages/{objectId}/draft_getDraftById'.HubspotCmsApi.GetLandingPageFolderById
Retrieve details of a landing page folder by its ID. Use this tool to get information about a specific landing page folder in HubSpot CMS by providing its unique ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
folder_id | string | Required | The unique identifier for the landing page folder to retrieve. |
filter_by_property | string | Optional | Specify properties to include in the response for the folder object. Leave empty to fetch all properties. |
include_archived_folders | boolean | Optional | Specifies whether to include deleted folders in the response. Use 'true' to include them; defaults to 'false'. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/landing-pages/folders/{objectId}_getFolderById'.HubspotCmsApi.GetLandingPageFolders
Retrieve the list of landing page folders from HubSpot CMS. This tool fetches the list of landing page folders in HubSpot CMS, supporting paging and filtering. Useful for integrations needing to analyze these models or suggest edits via external services.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
created_after | string | Optional | Return folders created after this specified ISO 8601 timestamp. |
created_before_time | string | Optional | Return folders created before this specific time. |
exact_update_time | string | Optional | Return folders last updated at exactly the specified time. Use a string format for the timestamp. |
filter_folders_created_at | string | Optional | Return folders created at an exact specified time. Use ISO 8601 format. |
folder_property | string | Optional | Specify properties to include in the response for each folder. Leave empty for all properties. |
include_deleted_folders | boolean | Optional | Include deleted folders in the results when set to true. Defaults to false. |
max_results_limit | integer | Optional | The maximum number of folder results to return. Default is 100. |
next_page_cursor | string | Optional | The cursor token to retrieve the next set of results from a paged response. |
sort_criteria | array<string> | Optional | Fields to use for sorting results. Valid options: `name`, `createdAt`, `updatedAt`, `createdBy`, `updatedBy`. Default: `createdAt`. |
updated_after_date | string | Optional | Only return folders last updated after the specified time. Use ISO 8601 format for the date and time. |
updated_before_timestamp | string | Optional | Return folders last updated before this specified timestamp. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/landing-pages/folders_getFoldersPage'.HubspotCmsApi.GetLandingPagePreviousVersions
Retrieve previous versions of a Landing Page for review. Use this tool to obtain all previous versions of a specified Landing Page, allowing you to track changes or restore versions if needed.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The ID of the Landing Page to retrieve previous versions for. |
cursor_token_for_next_set | string | Optional | The cursor token for retrieving the next set of results, from the `paging.next.after` JSON property. |
limit_page_fetching_before_cursor | string | Optional | A token used for fetching results before a specific cursor position in paged results. Typically used in pagination to navigate backwards. |
max_results | integer | Optional | The maximum number of previous landing page versions to return. Default is 100. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/landing-pages/{objectId}/revisions_getPreviousVersions'.HubspotCmsApi.GetLandingPages
Retrieve a list of HubSpot CMS landing pages. This tool retrieves a list of landing pages from HubSpot CMS, supporting paging and filtering. Ideal for integrations that analyze page models and suggest edits.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
created_after | string | Optional | Return landing pages created after this specified timestamp (ISO 8601 format). |
created_at_timestamp | string | Optional | Return landing pages created at the specified exact timestamp. Format: ISO 8601. |
created_before_timestamp | string | Optional | Only return landing pages created before the specified ISO 8601 timestamp. |
cursor_after_token | string | Optional | The token to get the next set of results. Obtainable from `paging.next.after` in a paged response. |
filter_by_property | string | Optional | Specify a property to filter the landing pages by. |
include_archived_pages | boolean | Optional | Specify whether to include deleted landing pages in the results. Defaults to false. |
last_updated_before | string | Optional | Return landing pages updated before this specified datetime (ISO format). |
last_updated_exact_time | string | Optional | Return Landing Pages last updated at exactly this time. Use ISO 8601 format. |
max_results | integer | Optional | Specify the maximum number of landing pages to return. Default is 100. |
sort_fields_for_results | array<string> | Optional | Specifies fields for sorting results. Valid options: `name`, `createdAt`, `updatedAt`, `createdBy`, `updatedBy`. Default is `createdAt`. |
updated_after_datetime | string | Optional | Return landing pages updated after this datetime in ISO 8601 format. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/landing-pages_getPage'.HubspotCmsApi.GetPreviousBlogPostVersions
Retrieve all previous versions of a blog post in HubSpot. Call this tool to access historical versions of a specific blog post using its 'objectId' in HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The unique ID of the blog post for retrieving its previous versions in HubSpot CMS. |
before_timestamp | string | Optional | The timestamp to retrieve versions updated before this time. |
maximum_results_limit | integer | Optional | The maximum number of blog post versions to return. Default is 100. |
next_page_cursor | string | Optional | The cursor token to retrieve the next set of blog post versions, obtained from `paging.next.after`. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blogs/posts/{objectId}/revisions_getPreviousVersions'.HubspotCmsApi.GetPreviousFolderVersions
Retrieve previous versions of a CMS folder. This tool retrieves all previous versions of a specified folder from the CMS. It should be called when there's a need to access or analyze the revision history of a folder.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
folder_id | string | Required | The unique ID of the folder to retrieve its previous versions. |
before_token | string | Optional | A cursor token to fetch items before a certain point in the result set, used for pagination. |
max_results | integer | Optional | Specifies the maximum number of folder versions to retrieve. Default is 100. |
pagination_cursor_after | string | Optional | The cursor token to retrieve the next set of results from the `paging.next.after` property in a paged response. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/landing-pages/folders/{objectId}/revisions_getFolderPreviousVersions'.HubspotCmsApi.GetPreviousSitePageVersions
Retrieve previous versions of a site page. Use this tool to access all previous versions of a specific site page in HubSpot's CMS. It's helpful for tracking changes or restoring an older version.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
site_page_id | string | Required | The unique identifier for the Site Page to retrieve its previous versions. |
max_results_limit | integer | Optional | The maximum number of previous versions to retrieve. Defaults to 100 if not specified. |
next_results_cursor | string | Optional | The cursor token to fetch the next set of site page versions. Obtain this from `paging.next.after` in the response of a previous request. |
page_version_cursor_before | string | Optional | The cursor token to get the set of results before a specific point. Useful for backward paging through results. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/site-pages/{objectId}/revisions_getPreviousVersions'.HubspotCmsApi.GetSitePageDraft
Retrieve the full draft version of the Site Page. Use this tool to get the complete draft version of a specific site page by providing the page's object ID. It should be called when you need to access or review the draft content of a site page in HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
site_page_id | string | Required | The unique identifier for the site page to retrieve its draft version. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/site-pages/{objectId}/draft_getDraftById'.HubspotCmsApi.GetSitePagesList
Retrieve a list of site pages with filtering options. Use this tool to get a list of site pages, supporting both paging and filtering. Ideal for integrations that need to examine pages or use external services to suggest edits.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
created_at_time_filter | string | Optional | Return Site Pages created at exactly the specified time. Accepts an exact timestamp in string format. |
created_before_date_time | string | Optional | Return Site Pages created before this date-time. Use ISO 8601 format. |
filter_created_after | string | Optional | Return Site Pages created after the specified time. Use an ISO 8601 timestamp format. |
filter_updated_after | string | Optional | Return site pages updated after this specific time. Use ISO 8601 format. |
include_deleted_site_pages | boolean | Optional | Set to true to include deleted Site Pages in the results. Defaults to false if not specified. |
include_property_details | string | Optional | Specify the properties to include in the Site Pages results. Leave empty to include all properties. |
last_updated_before | string | Optional | Return site pages last updated before this datetime. Format: ISO 8601 string. |
last_updated_exact_time | string | Optional | Return site pages last updated at exactly the specified time in ISO 8601 format. |
maximum_results | integer | Optional | The maximum number of site pages to return. Default is 100. |
next_page_cursor | string | Optional | Cursor token for paged results; use `paging.next.after` for the next set. |
sort_fields_for_results | array<string> | Optional | Specify fields for sorting site pages. Options: `name`, `createdAt`, `updatedAt`, `createdBy`, `updatedBy`. Default is `createdAt`. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/site-pages_getPage'.HubspotCmsApi.GetTableRow
Get a single row from a HubSpot CMS table by ID. Use this tool to retrieve a specific row from the published version of a HubSpot CMS table by providing the table ID or name and the row ID. This can be done without authentication if the table allows public access.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
row_id | string | Required | The ID of the row to retrieve from the table. |
table_id_or_name | string | Required | The ID or name of the HubSpot CMS table to retrieve the row from. |
archived | boolean | Optional | A boolean to retrieve archived rows. Set to True to include archived rows, or False to exclude them. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/hubdb/tables/{tableIdOrName}/rows/{rowId}_getTableRow'.HubspotCmsApi.GetUrlRedirectDetailsById
Retrieve details of a URL redirect by ID. Use this tool to obtain the details of a specific URL redirect by providing its ID. Ideal for managing URL redirects within HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
url_redirect_id | string | Required | The ID of the target URL redirect to fetch details for. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/url-redirects/{urlRedirectId}_getById'.HubspotCmsApi.NewAbTestVariation
Create a new A/B test variation in HubSpot CMS. This tool creates a new A/B test variation for a site page in HubSpot CMS using the provided details.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
ab_test_variation_name | string | Required | The name for the new A/B test variation to be created. |
object_id_to_test | string | Required | ID of the object to be tested in the A/B test variation. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/ab-test/create-variation_createABTestVariation'.HubspotCmsApi.NewLanguageBlogVariation
Create a new language variation from an existing blog post. Use this tool to generate a new language version of an existing blog post on HubSpot CMS. It's useful for expanding the reach of content to different language audiences.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The ID of the blog post you want to clone into a new language variation. |
target_language | string | Optional | The language code for the target language of the new blog post variation (e.g., 'fr' for French). |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/multi-language/create-language-variation_createLangVariation'.HubspotCmsApi.PermanentlyDeleteHubdbDraftRows
Permanently delete draft rows from a HubDB table. Use this tool to permanently delete rows from the draft version of a HubDB table. A maximum of 100 row IDs can be deleted per call.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
row_ids_to_delete | array<string> | Required | An array of up to 100 row IDs to permanently delete from the draft version of the table. |
table_id_or_name | string | Required | The ID or name of the HubDB table to target for deleting draft rows. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/rows/draft/batch/purge_purgeDraftTableRows'.HubspotCmsApi.PublishBlogPost
Publish a draft blog post to make it live. Use this tool to publish the draft version of a blog post, sending its content to the live page.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The unique identifier of the blog post to be published live. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/{objectId}/draft/push-live_pushLive'.HubspotCmsApi.PublishLandingPageDraft
Publish changes from a landing page draft to live. Use this tool to apply any updates made in the draft version of a HubSpot CMS landing page to its live version. Ideal for finalizing and publishing edits.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The ID of the landing page whose draft will be pushed live. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/{objectId}/draft/push-live_pushLive'.HubspotCmsApi.PublishSitePage
Publish draft changes to live site page. Use this tool to apply draft changes of a site page to its live version. It should be called when you want to make the draft content public on the HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
site_page_id | string | Required | The ID of the Site Page whose draft will be published live. Ensure it corresponds to the correct page in HubSpot CMS. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/{objectId}/draft/push-live_pushLive'.HubspotCmsApi.PublishTableDraft
Publish draft table to update website pages. This tool publishes a HubSpot CMS table by copying data and schema changes from the draft to the published version. Use it to ensure that any website pages using the table are updated with the latest draft content.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
table_identifier | string | Required | The ID or name of the HubSpot CMS table to publish. This identifies which draft table's data and schema should be copied to the published version. |
include_foreign_id_values | boolean | Optional | Set to `true` to populate foreign ID values in the response. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/draft/publish_publishDraftTable'.HubspotCmsApi.ReadHubdbTableRows
Retrieve rows from a published HubDB table. This tool fetches rows from a specified HubDB table using row IDs. It can be used when the table allows public access, so no authentication is needed.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
hubdb_table_id_or_name | string | Required | The ID or name of the HubDB table to query. Use this to specify which table's rows to retrieve. |
row_ids | array<string> | Required | An array of strings representing the row IDs to retrieve from the specified HubDB table. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/rows/batch/read_readTableRows'.HubspotCmsApi.RemoveBlogPost
Delete a blog post by its ID. This tool removes a specific blog post using its unique ID. Use it if you need to delete content from the blog.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The unique ID of the blog post to delete. This ID identifies which specific post will be removed. |
only_archived_results | boolean | Optional | Set to true to return only deleted (archived) blog posts. |
Requirements
Output
json— Response from the API endpoint 'delete-/cms/v3/blogs/posts/{objectId}_archive'.HubspotCmsApi.ReplaceDraftTableRow
Replace a row in the draft version of a HubDB table. This tool replaces a single row in the draft version of a specified HubDB table. All column values must be provided. Omitted columns will be deleted from the row. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
table_id_or_name | string | Optional | The ID or name of the HubDB table to replace the row in. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
row_id | string | Optional | The unique identifier of the row to be replaced in the draft table. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'put-/cms/v3/hubdb/tables/{tableIdOrName}/rows/{rowId}/draft_replaceDraftTableRow'.HubspotCmsApi.ReplaceDraftTableRows
Batch replace rows in HubSpot CMS draft tables. This tool replaces multiple rows in the draft version of a HubSpot CMS table, allowing up to 100 rows per call. Useful for updating entries en masse in preparation for publication. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
table_identifier | string | Optional | The ID or name of the table in which you want to replace draft rows. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/rows/draft/batch/replace_replaceDraftTableRows'.HubspotCmsApi.RerunPreviousAbTest
Rerun a previous A/B test on a landing page. Initiate the rerun of a previous A/B test for a landing page in HubSpot CMS. Use this tool when you need to repeat an A/B test to validate or compare results.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
test_id_to_rerun | string | Required | Provide the ID of the test you want to rerun on the landing page. |
variation_id | string | Required | Provide the ID of the object you wish to reactivate as a test variation. This ID is necessary to specify which variation of the landing page you intend to rerun in the A/B test. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/ab-test/rerun_rerunPreviousABTest'.HubspotCmsApi.ResetBlogPostDraft
Resets a blog post draft to the currently published content. Use this tool to discard all changes in a blog post draft and return the draft to its last published state. This can be useful when you want to undo all edits made in draft since the last publication.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The unique ID of the blog post draft that you want to reset to the published version. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/{objectId}/draft/reset_resetDraft'.HubspotCmsApi.ResetHubdbDraftToPublished
Reset HubDB draft table to match the published version. Replaces the draft version of a HubDB table with its published version, discarding any unpublished changes.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
table_identifier | string | Required | The ID or name of the HubDB table to reset to the published version. |
include_foreign_ids | boolean | Optional | Set to true to populate foreign ID values in the response. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/draft/reset_resetDraftTable'.HubspotCmsApi.ResetHubspotPageDraft
Resets HubSpot CMS draft to the live version. This tool discards any edits made to a HubSpot CMS page draft and reverts it to the last published live version. Use it to undo changes that you no longer wish to keep.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
site_page_id | string | Required | The ID of the HubSpot Site Page whose draft will be reset to the live version. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/{objectId}/draft/reset_resetDraft'.HubspotCmsApi.ResetLandingPageDraft
Reset a landing page draft to its live version. Use this tool to discard any edits made to a landing page draft and reset it to match the current live version, ensuring no changes made in the draft are preserved.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The ID of the Landing Page whose draft will be reset to the live version. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/{objectId}/draft/reset_resetDraft'.HubspotCmsApi.RestartAbTest
Rerun a previous A/B test to gain new insights. Use this tool to rerun an A/B test on your HubSpot CMS site pages. It should be called when you want to repeat a previous test for additional insights or validation of results.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
ab_test_id | string | Required | The unique ID of the A/B test you wish to rerun on your HubSpot CMS site pages. |
test_variation_id | string | Required | ID of the object to reactivate as a test variation for the A/B test. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/ab-test/rerun_rerunPreviousABTest'.HubspotCmsApi.RestoreBlogPostToDraft
Restore a previous blog post version to draft. Use this tool to revert a specified version of a blog post to the draft state in HubSpot CMS. This is useful for undoing changes or reverting to a previous version of content.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The unique identifier for the blog post to be restored to a draft version. This is the same as the blog post's current ID in the HubSpot CMS. |
version_to_restore_id | integer | Required | The ID of the blog post version to revert to the draft state. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/{objectId}/revisions/{revisionId}/restore-to-draft_restorePreviousVersionToDraft'.HubspotCmsApi.RestoreBlogPostVersion
Restore a blog post to a previous version. Use this tool to revert a blog post to an earlier saved version by providing the specific object ID and revision ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The ID of the blog post to be restored to a previous version. |
version_to_restore_id | string | Required | The unique identifier of the blog post version to which you want to revert. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/{objectId}/revisions/{revisionId}/restore_restorePreviousVersion'.HubspotCmsApi.RestoreFolderVersion
Restore a specific version of a folder in HubSpot CMS. Call this tool to restore a folder to a specified previous version using its object and revision IDs in HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
folder_id | string | Required | The unique identifier for the folder you want to restore in HubSpot CMS. |
folder_version_id_to_restore | string | Required | The ID of the folder version to be restored in HubSpot CMS. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/folders/{objectId}/revisions/{revisionId}/restore_restoreFolderPreviousVersion'.HubspotCmsApi.RestoreLandingPageDraft
Restore a specified landing page version to draft. This tool restores a specified version of a landing page as the new draft version. Use it when you need to revert changes on a landing page and set a previous version as the current draft.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The ID of the landing page to restore a specific version to draft. |
landing_page_version_id_to_restore | integer | Required | The ID of the landing page version you want to restore as the new draft. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/{objectId}/revisions/{revisionId}/restore-to-draft_restorePreviousVersionToDraft'.HubspotCmsApi.RestoreLandingPageVersion
Restore a specific version of a HubSpot landing page. This tool restores a specified version of a landing page in HubSpot CMS. Use this when you need to revert a page to a previous version, providing the necessary identifiers.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The unique identifier for the landing page you want to restore. |
landing_page_version_id | string | Required | The ID of the Landing Page version to be restored. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/{objectId}/revisions/{revisionId}/restore_restorePreviousVersion'.HubspotCmsApi.RestorePageVersion
Restore a specific version of a HubSpot site page. Use this tool to restore a specified version of a HubSpot site page. Ideal for undoing changes or reverting to a previous design or content state.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
page_version_to_restore | string | Required | The ID of the site page version to restore. Use this to revert to a previous version. |
site_page_id | string | Required | The unique identifier for the Site Page to be restored. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/{objectId}/revisions/{revisionId}/restore_restorePreviousVersion'.HubspotCmsApi.RestoreSitePageToDraft
Restore a specific site page version to draft. Use this tool to take a specified version of a HubSpot CMS site page and set it as the new draft version. This is useful when you need to revert a page to a previously saved version.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
site_page_id | string | Required | The ID of the Site Page to be restored to draft. |
site_page_version_id_to_restore | integer | Required | The ID of the Site Page version to restore as the new draft. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/{objectId}/revisions/{revisionId}/restore-to-draft_restorePreviousVersionToDraft'.HubspotCmsApi.RetrieveAuditLogs
Retrieve audit logs based on specified filters. Use this tool to obtain audit logs from HubSpot CMS, filtered according to specific criteria. This is useful for tracking changes, monitoring activity, or performing security audits.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
event_types | array<string> | Optional | A list of event types to filter by, such as CREATED, UPDATED, PUBLISHED, DELETED, UNPUBLISHED. |
filter_by_object_ids | array<string> | Optional | List of object IDs to filter the audit logs by. |
filter_by_object_type | array<string> | Optional | List the object types to filter audit logs by, such as BLOG, LANDING_PAGE, DOMAIN, etc. Use a comma-separated format. |
number_of_logs_to_return | integer | Optional | Specifies the number of audit logs to retrieve. |
sort_direction | array<string> | Optional | Specify the sort direction for audit logs by timestamp, e.g., 'asc' or 'desc'. |
timestamp_after | string | Optional | Timestamp (in ISO 8601 format) after which audit logs will be returned. |
timestamp_before | string | Optional | A timestamp to filter audit logs before the specified date and time. |
user_ids_to_filter | array<string> | Optional | Array of user IDs to filter the audit logs by. Provide as a list of strings. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/audit-logs/_getPage'.HubspotCmsApi.RetrieveBlogAuthors
Retrieve specified Blog Author objects from the CMS. Use this tool to obtain detailed information about blog authors by specifying their identifiers. This is useful for accessing author details in the HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
author_identifiers | array<string> | Required | An array of strings representing the identifiers for the blog authors to retrieve. |
include_deleted_authors | boolean | Optional | Specifies whether to include deleted Blog Authors in the results. Set to true to include them. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/authors/batch/read_readBatch'.HubspotCmsApi.RetrieveBlogPostById
Retrieve a blog post by its ID from HubSpot CMS. This tool retrieves the details of a specific blog post using its ID from the HubSpot CMS, ideal for accessing individual post content.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The unique identifier of the blog post to retrieve from HubSpot CMS. |
include_archived_posts | boolean | Optional | If true, includes deleted (archived) blog posts in the retrieval. Defaults to false. |
return_specific_properties | string | Optional | Comma-separated list of specific properties to retrieve from the blog post. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blogs/posts/{objectId}_getById'.HubspotCmsApi.RetrieveBlogPosts
Retrieve all blog posts with optional paging and filtering. Use this tool to access and browse all blog posts available, with additional options for paging and filtering. Ideal for integrating services that need to ingest blog content and suggest edits.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
created_after | string | Optional | Return blog posts created after the specified time. Use ISO 8601 format for the date-time. |
created_before | string | Optional | Only return blog posts created before the specified time in ISO 8601 format. |
filter_by_creation_time | string | Optional | Return only blog posts created at the specified time in ISO 8601 format. |
filter_by_update_after | string | Optional | Only return blog posts last updated after the specified timestamp. Use a format such as ISO 8601 for date and time. |
include_archived_posts | boolean | Optional | Specify true to include archived (deleted) blog posts in the results. Defaults to false. |
max_results | integer | Optional | The maximum number of blog post results to return. Default is 20. |
pagination_cursor_token | string | Optional | The cursor token to retrieve the next set of blog post results. Obtain from `paging.next.after` in a previous response. |
return_specific_properties | string | Optional | Comma-separated list of specific fields to return for each blog post (e.g., 'title,author,date'). Leave empty to return all fields. |
sort_fields_for_results | array<string> | Optional | An array specifying fields to sort blog posts. Use fields like `createdAt`, `name`, `updatedAt`, `createdBy`, `updatedBy`. |
updated_at_exact | string | Optional | Return blog posts last updated at the exact specified time in ISO 8601 format. |
updated_before_date | string | Optional | Return blog posts last updated before this date. Use ISO 8601 format (e.g., '2023-09-04T15:00:00Z'). |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blogs/posts_getPage'.HubspotCmsApi.RetrieveBlogPostsById
Retrieve a batch of blog posts by their IDs. This tool fetches multiple blog posts from HubSpot CMS based on the IDs provided in the request body. Use it when you need to access specific blog posts using their identifiers.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_ids | array<string> | Required | A list of blog post IDs to retrieve. Each ID should be a string. |
include_archived_posts | boolean | Optional | Include deleted blog posts if true. Defaults to `false`. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/batch/read_read'.HubspotCmsApi.RetrieveBlogRevisionDetails
Retrieve specific blog revision details by ID. Fetches details of a specific blog revision using the blog and revision IDs. Useful for obtaining historical settings or changes of a blog post.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_id | string | Required | The unique identifier for the blog post. It is required to fetch the specific revision details. |
revision_id | string | Required | A unique string identifier for a specific blog revision to be retrieved. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blog-settings/settings/{blogId}/revisions/{revisionId}'.HubspotCmsApi.RetrieveBlogSettings
Retrieve current blog settings from the HubSpot CMS. Use this tool to fetch and return the current configuration and settings of blogs within the HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
created_before | string | Optional | Retrieve blog settings created before this date. Format as 'YYYY-MM-DD'. |
created_timestamp | string | Optional | The exact timestamp when the blog settings were created, formatted as an ISO 8601 string. |
filter_created_after_date | string | Optional | Filter settings to only include blogs created after the specified date (ISO 8601 format). |
include_archived | boolean | Optional | Set to true to include archived blog settings and false to exclude them. |
max_number_of_results | integer | Optional | The maximum number of blog settings to retrieve. The value should be an integer. |
pagination_cursor | string | Optional | A token to retrieve the next set of blog settings after the current page. Use this for paginating results. |
sort_options | array<string> | Optional | An array specifying fields to sort by, in order of priority (e.g., ['createdAt', '-updatedAt'] for ascending and descending). |
updated_after_timestamp | string | Optional | Fetch settings for blogs updated after this date and time. Use ISO 8601 format. |
updated_at_exact_timestamp | string | Optional | Fetch blogs with this exact update timestamp. Use ISO 8601 format (YYYY-MM-DDTHH:MM:SSZ). |
updated_before_date | string | Optional | The latest date (inclusive) to filter blog updates. Provide in 'YYYY-MM-DD' format. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blog-settings/settings'.HubspotCmsApi.RetrieveBlogTagById
Retrieve blog tag details using its ID. Use this tool to get information about a blog tag by providing its unique ID. Call this tool when you need details about a specific blog tag in the HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_tag_id | string | Required | The unique identifier for the Blog Tag to be retrieved. |
include_archived_blog_tags | boolean | Optional | Specify whether to include archived blog tags in the response. Defaults to `false`. |
property_name | string | Optional | Specify a property of the blog tag to retrieve. Leave blank to get all details. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blogs/tags/{objectId}_getById'.HubspotCmsApi.RetrieveBlogTags
Retrieve Blog Tag objects based on specified IDs. This tool retrieves detailed information about specific Blog Tag objects in HubSpot CMS, identified by the IDs provided in the request.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_tag_ids | array<string> | Required | A list of strings representing the IDs of the Blog Tag objects to retrieve. |
include_deleted_tags | boolean | Optional | Boolean indicating if deleted Blog Tags should be included in the response. If true, deleted tags are returned. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/tags/batch/read_readBatch'.HubspotCmsApi.RetrieveFolderPreviousVersion
Retrieve a previous version of a folder in HubSpot CMS. Use this tool to obtain information about a specific previous version of a folder within HubSpot's CMS. Call this tool when you need to access historical data of a folder's version for reference or comparison.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
folder_id | string | Required | The unique identifier for the folder whose previous version you want to retrieve. |
folder_version_id | string | Required | The unique identifier for the folder version to be retrieved. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/landing-pages/folders/{objectId}/revisions/{revisionId}_getFolderPreviousVersion'.HubspotCmsApi.RetrieveIndexedDataByContentId
Retrieve all indexed data for a specific document by ID. Use this tool to obtain indexed data for a specific document in the HubSpot CMS, such as a page, blog post, or HubDB row, for debugging purposes.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
document_id | string | Required | ID of the target document when searching for indexed properties in HubSpot CMS. |
document_type | string | Optional | Specify the document type, such as `SITE_PAGE`, `BLOG_POST`, or `KNOWLEDGE_ARTICLE`. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/site-search/indexed-data/{contentId}_getById'.HubspotCmsApi.RetrieveLandingPages
Retrieve specified Landing Page objects from HubSpot CMS. Use this tool to obtain details of specific Landing Page objects identified by their IDs from the HubSpot CMS. Ideal for fetching batch data on landing pages for content management or analysis.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_ids | array<string> | Required | Array of strings, each representing a Landing Page ID to retrieve details for. |
return_archived_landing_pages | boolean | Optional | Specify whether to return deleted Landing Pages. Defaults to `false`. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/batch/read_readBatch'.HubspotCmsApi.RetrievePreviousBlogVersion
Retrieve a previous version of a blog post. This tool retrieves details of a specific previous version of a blog post. It is useful for accessing and reviewing earlier versions of content.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The unique identifier for the blog post whose previous version is to be retrieved. |
version_id | string | Required | The ID of the specific blog post version to retrieve. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/blogs/posts/{objectId}/revisions/{revisionId}_getPreviousVersion'.HubspotCmsApi.RetrievePreviousLandingPageVersion
Retrieve a previous version of a Landing Page. Use this tool to obtain a prior version of a landing page from HubSpot's CMS using specific object and revision IDs.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The unique identifier for the landing page. |
landing_page_version_id | string | Required | The ID of the landing page version to retrieve. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/landing-pages/{objectId}/revisions/{revisionId}_getPreviousVersion'.HubspotCmsApi.RetrievePreviousSitePageVersion
Retrieve a previous version of a site page. Use this tool to access details of a previous revision of a site page by specifying the object and revision IDs.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
site_page_id | string | Required | The unique identifier for the site page whose previous version is to be retrieved. |
site_page_revision_id | string | Required | The ID of the specific revision of the site page to retrieve. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/site-pages/{objectId}/revisions/{revisionId}_getPreviousVersion'.HubspotCmsApi.RetrieveSitePageById
Retrieve Site Page details by ID. This tool retrieves the details of a Site Page object identified by its ID. It should be called when you need information about a specific Site Page.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
site_page_id | string | Required | The unique identifier for the Site Page to retrieve. |
return_archived_site_pages | boolean | Optional | Boolean indicating whether to return deleted Site Pages. Defaults to 'false'. |
site_page_property | string | Optional | Specify the property of the Site Page to return. Leave empty to retrieve all properties. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/pages/site-pages/{objectId}_getById'.HubspotCmsApi.RetrieveSitePages
Retrieve Site Page objects from HubSpot CMS. Use this tool to retrieve specific Site Page objects from HubSpot CMS based on identifiers provided in the request. This is useful for accessing detailed information about multiple site pages in a batch.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
page_identifiers | array<string> | Required | An array of strings, each representing an identifier for a Site Page to be retrieved. Use these IDs to specify which Site Pages to access. |
return_deleted_site_pages | boolean | Optional | Set to true to return deleted Site Pages; false to exclude them. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/batch/read_readBatch'.HubspotCmsApi.ScheduleBlogPost
Schedule a blog post for future publication. This tool is used to schedule a HubSpot CMS blog post to be published at a specific time. It should be called when you want to set a future publication date for a blog post.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The ID of the blog post to be scheduled for future publication. |
scheduled_publish_date | string | Required | The date and time when the blog post should be published, formatted as a string (e.g., '2023-12-31T23:59:59'). |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/schedule_schedule'.HubspotCmsApi.ScheduleLandingPage
Schedule a landing page for publication. This tool schedules a landing page to be published, using HubSpot CMS. It is used when you need to set a specific time for your landing page to go live.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The unique identifier for the landing page to be scheduled for publication. |
publication_date | string | Required | The date when the landing page should be published. Use the format YYYY-MM-DD. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/schedule_schedule'.HubspotCmsApi.ScheduleSitePagePublication
Schedule a site page for publication at a specified time. Use this tool to set a future publication date for a site page within the HubSpot CMS. It can be used to automate the release time of new content on your website.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
object_id_to_schedule | string | Required | The ID of the site page to be scheduled for publication. |
publication_date | string | Required | The date and time when the site page should be published. Use ISO 8601 format (e.g., '2023-12-31T23:59:00Z'). |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/schedule_schedule'.HubspotCmsApi.SearchWebsiteContent
Search for website content on a HubSpot account. Use this tool to retrieve website content that matches specified search criteria within a HubSpot account. Filters can include content type, domain, or URL path.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_ids_to_search | array<integer> | Optional | List of blog IDs to search within. Allows searching multiple blogs by their IDs. |
boost_recent_time_window | string | Optional | A relative time window to boost scores of documents published within this period. Use '10d' for 10 days. Supported units: ms, s, m, h, d. Applicable to blog posts only. |
content_language_code | string | Optional | Specifies the language of content to be searched using a valid ISO 639-1 code (e.g. 'es' for Spanish). |
content_type_filters | array<string> | Optional | List of content types to search, such as SITE_PAGE, LANDING_PAGE, BLOG_POST, LISTING_PAGE, and KNOWLEDGE_ARTICLE. |
hubdb_query_filter | string | Optional | Specify a HubDB query to filter search results in the specified table. |
hubdb_table_id | integer | Optional | Specifies a specific HubDB table to search. Only results from this table are returned. Can be combined with 'hubdb_query' for further filtering. |
invert_path_prefix_filter | boolean | Optional | Set to 'false' to apply the normal behavior of the pathPrefix filter; 'true' to invert it. |
maximum_boost_limit | number | Optional | Specifies the maximum amount a result will be boosted based on its view count. Defaults to 5.0. |
pagination_offset | integer | Optional | Integer used to page through results. Use the offset from the previous request to access the next set of results. |
path_prefixes | array<string> | Optional | An array of strings to filter search results by URL path prefix. Only returns results with paths starting with specified prefixes. |
popularity_boost | number | Optional | Specify the boost factor for a result based on its view count. Defaults to 1.0. |
result_length | string | Optional | Specifies whether search results should be detailed (LONG) or brief (SHORT). |
results_limit | integer | Optional | The number of search results to return. Defaults to 10 and has a maximum of 100. |
search_domains | array<string> | Optional | List of domains to match search results for. Multiple domains can be included by separating them with '&'. |
search_properties | array<string> | Optional | A list of properties to include in the search. Options: `title`, `description`, `html`. By default, all properties are searched. |
search_term | string | Optional | The term to search for in the HubSpot website content. |
show_autocomplete | boolean | Optional | Specify whether autocomplete results should be shown. Defaults to false. |
Requirements
Output
json— Response from the API endpoint 'get-/cms/v3/site-search/search_search'.HubspotCmsApi.SetBlogTagPrimaryLanguage
Set a blog tag as the primary language in a multi-language group. This tool updates a blog tag to be the primary language within a multi-language group, ensuring content consistency across different languages.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
primary_language_tag_id | string | Required | ID of the blog tag to set as the primary language in a multi-language group. |
Requirements
Output
json— Response from the API endpoint 'put-/cms/v3/blogs/tags/multi-language/set-new-lang-primary_setLangPrimary'.HubspotCmsApi.SetNewBlogPrimaryLanguage
Set a new primary language for blogs. This tool is used to update the primary language for multi-language blog settings in HubSpot CMS. It should be called when there is a need to change the default language for blogs.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
primary_language_object_id | string | Required | ID of the blog object to set as primary in the multi-language group. |
Requirements
Output
json— Response from the API endpoint 'put-/cms/v3/blog-settings/settings/multi-language/set-new-lang-primary'.HubspotCmsApi.SetPrimaryLandingPageLanguage
Set a landing page as the primary language for a group. Use this tool to set a specific landing page as the primary language of a multi-language group in the HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
landing_page_id | string | Required | The ID of the landing page to set as primary in the multi-language group. |
Requirements
Output
json— Response from the API endpoint 'put-/cms/v3/pages/landing-pages/multi-language/set-new-lang-primary_setLangPrimary'.HubspotCmsApi.SetPrimaryLanguageBlogAuthor
Set a blog author as the primary language in a multilingual group. Use this tool to designate a specific blog author as the primary language author in a multi-language group within the HubSpot CMS.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
primary_language_author_id | string | Required | The ID of the blog author to be set as the primary in a multi-language group. |
Requirements
Output
json— Response from the API endpoint 'put-/cms/v3/blogs/authors/multi-language/set-new-lang-primary_setLangPrimary'.HubspotCmsApi.SetPrimaryLanguageBlogPost
Set the primary language of a blog post in a multi-language group. This tool updates the primary language of a multi-language group to match the language of the specified blog post by its ID. It is useful when managing multilingual content on HubSpot CMS blogs.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_post_id | string | Required | The ID of the blog post to set as primary in its multi-language group. |
Requirements
Output
json— Response from the API endpoint 'put-/cms/v3/blogs/posts/multi-language/set-new-lang-primary_setLangPrimary'.HubspotCmsApi.SetPrimaryLanguageForSitePage
Set a site page as the primary language of its group. This tool is used to designate a site page as the primary language page in a multi-language group within HubSpot CMS. It should be called when a user needs to configure language settings for site pages.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
page_id_to_set_primary | string | Required | The ID of the site page to set as the primary language in the multi-language group. |
Requirements
Output
json— Response from the API endpoint 'put-/cms/v3/pages/site-pages/multi-language/set-new-lang-primary_setLangPrimary'.HubspotCmsApi.TrackMediaMilestones
Log user progress milestones in media content viewing. This tool creates an event to track when a user reaches quarterly viewing milestones in a piece of media. It should be called whenever it's necessary to log this progress for analytics or tracking purposes. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/media-bridge/v1/events/media-played-percent'.HubspotCmsApi.UnpublishHubdbTable
Unpublish a HubDB table to stop rendering data on website pages. Use this tool to unpublish a HubDB table. This action will prevent any website pages from rendering data associated with the table.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
table_identifier | string | Required | The ID or name of the HubDB table to unpublish. |
include_foreign_ids | boolean | Optional | Set this to true to populate foreign ID values in the response. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/hubdb/tables/{tableIdOrName}/unpublish_unpublishTable'.HubspotCmsApi.UpdateBlogAuthor
Update specific details of a blog author. This tool updates specific details of a blog author using their unique ID. It should be called when you need to modify existing author information without changing all attributes. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
blog_author_id | string | Optional | The unique ID of the blog author to be updated. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
update_deleted_blog_authors | boolean | Optional | Set to `true` to update deleted Blog Authors. Defaults to `false`. Only used when mode is 'execute'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/blogs/authors/{objectId}_update'.HubspotCmsApi.UpdateBlogAuthorLanguages
Set new languages for each blog author in a group. Use this tool to explicitly update the languages associated with each blog author in a multi-language group. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/authors/multi-language/update-languages_updateLangs'.HubspotCmsApi.UpdateBlogAuthorsBatch
Update multiple blog author objects at once. Use this tool to update multiple blog author objects in HubSpot CMS based on identifiers provided in the request. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
update_deleted_blog_authors | boolean | Optional | Set to true to update deleted Blog Authors. Defaults to false. Only used when mode is 'execute'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/authors/batch/update_updateBatch'.HubspotCmsApi.UpdateBlogLanguages
Update the languages for blog settings. Use this tool to update the multi-language settings for blogs in HubSpot CMS. Call this tool when you need to modify the languages available for a blog. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blog-settings/settings/multi-language/update-languages'.HubspotCmsApi.UpdateBlogPost
Update specific fields of a blog post by ID. This tool updates specific fields of a blog post using its ID, requiring only the values that need to be changed. Ideal for making partial updates to existing blog content. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
blog_post_id | string | Optional | The unique identifier of the blog post to update. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
update_archived_posts | boolean | Optional | Set to true to update deleted (archived) blog posts. Defaults to false. Only used when mode is 'execute'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/blogs/posts/{objectId}_update'.HubspotCmsApi.UpdateBlogPostDraft
Update specific fields of a blog post draft. Use this tool to partially update the draft version of a blog post by specifying the blog post ID and the fields you wish to update. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
blog_post_id | string | Optional | The ID of the blog post draft to update. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/blogs/posts/{objectId}/draft_updateDraft'.HubspotCmsApi.UpdateBlogPostLanguages
Set new languages for multi-language blog posts. Use this tool to explicitly set or update the languages for each post in a multi-language group within HubSpot's CMS. Ideal for managing content across different languages. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/multi-language/update-languages_updateLangs'.HubspotCmsApi.UpdateBlogPostsBatch
Update a batch of blog posts in the CMS. Use this tool to update multiple blog posts simultaneously in the HubSpot CMS. Ideal for making bulk edits to post content or metadata. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
update_archived_posts | boolean | Optional | Indicates whether to update deleted blog posts. Defaults to `false`. Only used when mode is 'execute'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/posts/batch/update_update'.HubspotCmsApi.UpdateBlogTag
Update specific fields of a blog tag by its ID. This tool updates specific fields of a single blog tag identified by its object ID. It enables partial updates, allowing changes to only the specified fields.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
blog_tag_id | string | Required | The unique identifier for the blog tag to be updated. |
blog_tag_unique_id | string | Required | The unique ID of the Blog Tag to be updated. |
created_timestamp | string | Required | The timestamp (ISO8601 format) when the blog tag was created. This field is optional and can be used if the creation time needs to be updated. |
deleted_timestamp | string | Required | The ISO8601 timestamp indicating when the blog tag was deleted. |
language | string | Required | The ISO 639 language code for the tag. Select from the available options. |
last_updated_timestamp | string | Required | The ISO8601 timestamp when the blog tag was last updated. |
primary_tag_translated_from_id | integer | Required | ID of the primary tag from which this tag was translated. |
tag_name | string | Required | The new name for the blog tag to be updated. This is a required field when changing the tag's name. |
update_deleted_blog_tags | boolean | Optional | Set to `true` to update deleted Blog Tags. Defaults to `false`. |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/blogs/tags/{objectId}_update'.HubspotCmsApi.UpdateBlogTagLanguages
Update languages for blog tags in a multi-language group. Use this tool to set new languages for each blog tag within a multi-language group in the HubSpot CMS. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/tags/multi-language/update-languages_updateLangs'.HubspotCmsApi.UpdateBlogTags
Update multiple blog tags in HubSpot CMS. Use this tool to update blog tag objects identified in the request body within the HubSpot CMS. It is useful for bulk modifications of blog tags. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
update_deleted_blog_tags | boolean | Optional | Specifies whether to update deleted blog tags. Defaults to false. Only used when mode is 'execute'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/blogs/tags/batch/update_updateBatch'.HubspotCmsApi.UpdateFolderObjects
Update specified folder objects in HubSpot CMS. Use this tool to update the folder objects identified in the request body within the HubSpot CMS platform. Useful for batch modifications of landing page folder metadata.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
folder_identifiers | array<string> | Required | An array of strings identifying folder objects to update in HubSpot CMS. |
include_archived_folders | boolean | Optional | Indicate whether to include archived folders in the results. Defaults to `false`. |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/folders/batch/read_readFolders'.HubspotCmsApi.UpdateHubdbDraftTable
Update or modify a HubDB table draft in HubSpot CMS. Use this tool to update an existing HubDB table by adding or removing columns, or restoring an archived table. Changes apply only to the draft version until published. Ensure all columns are included in the request to avoid deletion. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
table_id_or_name | string | Optional | The ID or name of the HubDB table to update. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
return_archived_tables | boolean | Optional | Set to true to return archived tables. Defaults to false. Only used when mode is 'execute'. |
populate_foreign_ids | boolean | Optional | Set to true to populate foreign ID values in the table result. Only used when mode is 'execute'. |
retrieve_localized_schema | boolean | Optional | Set to true to retrieve the localized schema of the HubDB table, if available. Only used when mode is 'execute'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/hubdb/tables/{tableIdOrName}/draft_updateDraftTable'.HubspotCmsApi.UpdateHubdbRowDraft
Update specific fields in a HubDB table's draft row. This tool updates specific fields in a HubDB table's draft row. It should be called when you need to modify only certain columns of a row in the draft version of a HubDB table. You don't have to specify all fields, only those you intend to update. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
table_identifier | string | Optional | The ID or name of the HubDB table to update the draft row in. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
row_id | string | Optional | The unique ID of the row to be updated in the draft table. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/hubdb/tables/{tableIdOrName}/rows/{rowId}/draft_updateDraftTableRow'.HubspotCmsApi.UpdateLandingPage
Update specific fields of a landing page by ID. This tool updates a landing page in HubSpot CMS by specifying only the fields you wish to modify, identified by the page's ID. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
landing_page_id | string | Optional | The unique ID of the landing page to update. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
update_archived_pages | boolean | Optional | Set to true to update archived (deleted) Landing Pages. Defaults to false. Only used when mode is 'execute'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/pages/landing-pages/{objectId}_update'.HubspotCmsApi.UpdateLandingPageDraft
Update draft of a specific landing page by ID. This tool updates the draft version of a landing page in HubSpot CMS. Use it when you need to make changes to an existing draft. Only the fields specified will be updated, based on the landing page ID provided. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
landing_page_id | string | Optional | The ID of the landing page to be updated. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/pages/landing-pages/{objectId}/draft_updateDraft'.HubspotCmsApi.UpdateLandingPageFolder
Update specific attributes of a landing page folder. Use this tool to update specific attributes of a HubSpot CMS landing page folder, identified by its object ID. Only the column values that need modification should be specified.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
content_folder_unique_id | string | Required | The unique ID of the landing page content folder to be updated. |
creation_timestamp | string | Required | The creation timestamp of the folder in ISO8601 format. Used for reference only, typically not updated. |
deletion_timestamp_iso8601 | string | Required | The timestamp in ISO8601 format indicating when the content folder was deleted. Required for specifying deletion time. |
folder_category | integer | Required | Specify the object type for the folder. Must be LANDING_PAGE. |
folder_id | string | Required | The unique ID of the landing page folder to be updated. |
folder_name | string | Required | Specify the new name of the landing page folder to display in the app dashboard. |
parent_folder_id | integer | Required | The ID of the content folder this folder is nested under. Specify this to set a new parent folder. |
update_timestamp | string | Required | The timestamp when the folder was last updated, in ISO8601 format. This indicates when changes were made. |
update_deleted_folders | boolean | Optional | Set to true to update folders marked as deleted. Defaults to false. |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/pages/landing-pages/folders/{objectId}_updateFolder'.HubspotCmsApi.UpdateLandingPageFolders
Update multiple HubSpot CMS landing page folders. Use this tool to update the Folder objects for landing pages in HubSpot CMS as identified in the request body. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
only_include_archived_results | boolean | Optional | Set to true to return only archived folder results; false to return all folders. Only used when mode is 'execute'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/folders/batch/update_updateFolders'.HubspotCmsApi.UpdateLandingPageLanguages
Update languages for landing pages in a multi-language group. This tool explicitly sets new languages for each landing page within a specified multi-language group. Use it when you need to modify the language settings of your HubSpot CMS landing pages. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/multi-language/update-languages_updateLangs'.HubspotCmsApi.UpdateLandingPagesBatch
Batch update landing pages in HubSpot CMS. Use this tool to update multiple landing page objects in HubSpot CMS by providing their identifiers and new data in the request body. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
update_deleted_landing_pages | boolean | Optional | Set to true to update deleted (archived) Landing Pages. Defaults to false. Only used when mode is 'execute'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/landing-pages/batch/update_updateBatch'.HubspotCmsApi.UpdateSitePage
Update specific fields of a HubSpot site page. This tool performs a sparse update on a single site page in HubSpot CMS, modifying only the specified fields of the page identified by its ID. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
site_page_id | string | Optional | The unique identifier for the Site Page to be updated. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
update_deleted_site_pages | boolean | Optional | Boolean to specify whether to update deleted Site Pages. Defaults to `false`. Only used when mode is 'execute'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/pages/site-pages/{objectId}_update'.HubspotCmsApi.UpdateSitePageDraft
Update the draft version of a specific site page. This tool updates the draft version of a single Site Page object in HubSpot CMS. Use it to modify specific fields of the draft by providing the new values. It is called when there's a need to edit an existing draft page based on its unique identifier. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
site_page_id | string | Optional | The unique identifier for the Site Page to update the draft. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/pages/site-pages/{objectId}/draft_updateDraft'.HubspotCmsApi.UpdateSitePageLanguages
Set new languages for site pages in a multi-language group. Use this tool to explicitly set new languages for each site page within a multi-language group. Ideal for updating or managing different language versions of your website's pages. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/multi-language/update-languages_updateLangs'.HubspotCmsApi.UpdateSitePagesBatch
Batch update specified site pages in HubSpot CMS. Use this tool to update multiple site pages in HubSpot CMS based on identifiers provided in the request body. It should be called when you need to make bulk updates to site page objects. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
update_deleted_site_pages | boolean | Optional | Specify true to update deleted Site Pages. Defaults to false. Only used when mode is 'execute'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'post-/cms/v3/pages/site-pages/batch/update_updateBatch'.HubspotCmsApi.UpdateUrlRedirectSettings
Update settings for an existing URL redirect in HubSpot CMS. This tool updates the configuration of a specified URL redirect in HubSpot CMS. Use it when you need to change the destination or other settings of an existing URL redirect. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
mode | string | Required | Operation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operationget_request_schemaexecute |
url_redirect_id | string | Optional | The unique identifier for the URL redirect to be updated. This ID specifies which redirect's settings will be modified. Required when mode is 'execute', ignored when mode is 'get_request_schema'. |
request_body | string | Optional | Stringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema' |
Requirements
Output
json— Response from the API endpoint 'patch-/cms/v3/url-redirects/{urlRedirectId}_update'.