HubSpot CMS RedirectsInstall

Summary

Create a HubSpot CMS URL redirect from a source route to a destination. Choose the redirect status and optionally configure URL matching rules and priority; the API response is returned as one n8n item.

Inputs

• Route Prefix (required) — Source path to redirect, such as /old-page; the UI says it must start with /. When Match Full URL is enabled, the UI says to provide a full URL.
• Destination (required) — Redirect target as an absolute URL or relative path.
• Redirect Style (required) — HTTP status: 301 (permanent), 302 (temporary), or 305 (proxy). Defaults to 301.
• Match Full URL — Match the entire URL, including its domain; defaults to false.
• Match Query String — Include query parameters when matching; defaults to false.
• Only After 404 — Apply the redirect only when the source URL returns a 404; defaults to false.
• Is Pattern (Regex) — Treat the route prefix as a regular expression; defaults to false.
• Protocol Relative — Ignore whether the matched URL uses HTTP or HTTPS; defaults to false.
• Trailing Slash Optional — Match the source URL with or without a trailing slash; defaults to false.
• Precedence — Priority when multiple redirects match; lower numbers have higher priority. Defaults to 0.

Output shape

A single item containing the HubSpot API response for the created redirect in its json field.

Uses the required HubSpot App Token credential. The operation sends the configured fields in a POST request to HubSpot’s CMS URL redirects endpoint. API errors fail the operation unless Continue On Fail is enabled.

Links

• n8n community nodes installation guide