Sprocket Rocket AI

Sprocket Rocket AI works beside whatever you have open: pages in Page Builder, module code, emails, blogs, and templates. Ask for a change in the chat and Sprocket Rocket makes it on a HubSpot draft while you watch. You can keep editing by hand at the same time.

Where it works

Select Chat in the rail on any installation screen. It's one chat: from anywhere, it can find, open, and create pages, modules, emails, blogs, and templates, and the conversation moves with them. See One chat, wherever you work.

• On a page, the chat works on the page on the canvas. See Work with Sprocket Rocket AI.
• With a module's code open, the chat edits that module. See Module view and code.
• On an email, blog, or template, the chat edits what's open, and can create new ones. See Emails, Blogs, and Templates.

What it can do

• Build a page from Sprocket Rocket modules, your theme's modules, and the portal's own custom modules. It adds, removes, moves, and arranges them in sections and columns, and fills in their content. See Work with Sprocket Rocket AI.
• Rebuild or borrow from any public web page you link, and test the page in a real browser to check that tabs, sliders, hover effects, and video work.
• Change the page title, meta description, URL, domain, and social sharing image, and move a page between website pages and landing pages. See Page settings and SEO.
• Find images on Unsplash or in your File Manager, and write alt text after looking at each image. See Images and alt text.
• Create URL redirects, set up A/B tests, and add translations. See Domains and redirects, A/B tests, and Translations.
• Read and edit HubDB tables. See HubDB tables.
• Build a new module, or change an existing one, when no module can do what you asked. See Build and change modules.
• Create and change marketing emails, blog templates, and page and system templates. It never sends an email: you send it from HubSpot.
• Propose a new brand for the theme. See Change the theme brand.
• Run PageSpeed Insights on a published page and fix what it finds.

Cards you confirm

Most of the AI's work happens on a draft, where you can undo it or leave it unpublished. Some changes reach further: they go live across the site, change other pages, or build a module in the background. Sprocket Rocket never makes those on its own. It shows a card in the chat, and nothing happens until you confirm it:

• URL redirects, confirmed with Create redirects
• A/B test, with Create variant
• Translation, with Create translation
• Publish HubDB table, with Publish table
• Module cards, with Build it, Make the copy, or Update module
• Copy a module, with Copy module
• Script to allow, with Allow script. See Scripts and embed code.
• Custom code for this page, with Add to draft
• Theme brand change, with Review, then Apply to theme

Each card also has Discard, or Cancel for a module card that hasn't started. A card applies once: if someone applies it in another tab first, your tab says it was already decided. When a card leaves work for Sprocket Rocket, such as filling in a new module's fields, it picks it up by itself once the card is done. Each card's page explains its statuses and who can apply it.

Scripts and embed code

An SR HTML module holds code: embeds, frames, styles, and scripts. Sprocket Rocket AI can add these to its HTML field, with a check on scripts:

• A script from an approved site goes straight in. The approved sites are HubSpot (forms, meetings, CTAs, and the portal's own tracking code), Calendly, Google Maps, YouTube, and Vimeo. HubSpot's standard form embed needs no card either.
• A script from any other site, or JavaScript Sprocket Rocket wrote itself, waits on a Script to allow card. The card names each site the code loads from, and Show the code shows any JavaScript it wrote. Nothing is on the page until you select Allow script. Only allow sites you trust: once the page is published, the script runs for everyone who visits it. If the field changed after the card was made, the card asks you to ask again rather than overwrite it.

Code you paste into an SR HTML field yourself in the app is saved the way HubSpot's editor would save it. AI apps connected over MCP can't add a script that needs a card. They tell you to add it in Sprocket Rocket instead.

The subscription

Sprocket Rocket AI is also the name of the organization's AI subscription. AI usage comes out of the organization's shared monthly AI budget. The Free plan includes a small one-time allowance for trying it. Warp and Agency Power also let you work on your portals from your own AI app, such as Claude or ChatGPT. See MCP. On any paid plan, a Breeze agent in HubSpot can read your pages and edit drafts. See HubSpot Breeze agents. See Pricing for what the subscription includes and Billing for how usage is shown.

What it can't do

• Change a Marketplace theme's files. HubSpot locks them. Sprocket Rocket builds your own version in an asset folder beside the theme instead. See Build modules with a Marketplace theme.
• Send an email. You pick recipients and send it from HubSpot.
• Edit your head and footer HTML. Set those in Page settings yourself. As a last resort for a look modules can't get, it can add a block of its own CSS or JavaScript to the page on a Custom code for this page card.
• Read or end an A/B test. HubSpot runs the test. You compare the results and choose the winner in HubSpot. See A/B tests.

Features that depend on the HubSpot plan

Some of Sprocket Rocket AI's tools use HubSpot features that only some HubSpot plans include. When the portal's plan doesn't include one, Sprocket Rocket says so instead of failing silently.

Two more tools have a requirement that isn't the plan. PageSpeed Insights only tests a published page. File Manager search and uploads need the File Manager permission on the portal's connection. When a permission is missing, Sprocket Rocket shows a card that explains what to do. See Images and alt text and HubDB tables.