1. Connect & scan
Create the project on the client’s portal. JetStack AI scans the portal so Jetty knows what’s already there. You can start chatting straight away.
Projects Overview
Projects lets you build a client’s HubSpot portal by chatting with Jetty, JetStack AI’s assistant. Connect the client’s portal, open a chat, and tell Jetty what you need, or upload a build spec. Jetty replies with a plan. When you approve it, Jetty builds everything on it. When you approve the deploy, it goes live in HubSpot. Then Jetty tells you exactly what HubSpot accepted and what it didn’t.
One Chat per Task
Section titled “One Chat per Task”A project is your workspace for one client. The work happens in chats, and each chat is one task: “Set up the renewals pipeline”, “Build the lead-routing workflows”, “Fix the onboarding emails”. Start a new chat whenever you start something new. Old chats stay in the sidebar with their full history.
A few things are always true:
- Nothing changes without your click. Jetty can look at the portal, read your documents and suggest changes. Anything that changes HubSpot shows up as a card in the chat, and nothing happens until you press its button.
- Everything you build is shared across the project. A property built in one chat can be used by a workflow in another chat.
- One problem doesn’t hold everything up. If one asset fails or needs an answer from you, only the assets that rely on it wait. Everything else goes ahead.
- You get a receipt for every change. Jetty only says something is live once a receipt in the chat confirms it, and the receipt shows what HubSpot actually said.
The Workspace at a Glance
Section titled “The Workspace at a Glance”| Page | What you’ll find |
|---|---|
| Overview | What needs you across all your chats: cards waiting for you, assets that failed or were changed in HubSpot, and parts of the portal that haven’t been scanned yet. It also shows your requirements and your chats |
| Documents | The files you’ve uploaded, and What Jetty knows about the client from them |
| Canvas | A picture of the client’s portal and everything this project has built |
| Deploy logs | A record of every deploy, with the result for each asset |
| Settings | The portal this project works on, and who’s on the project |
| Chats | One entry for each task. A dot shows which chats are working, waiting for you, or need a fix |
The Overview, Documents and Canvas pages are for looking around. When you want something changed, use Ask Jetty. It opens a chat with your question ready to send.
How It Works
Section titled “How It Works”2. Ask & plan
Tell Jetty what you need, or upload a build spec. Jetty asks only the questions it really needs answered, then sends a plan listing every asset it will build.
3. Build
Press Build on the plan. Jetty builds each asset for you to review. Nothing is in HubSpot yet.
4. Deploy & fix
Approve the deploy and your assets go live in HubSpot. If anything fails, Jetty tells you why and offers a one-click fix.
One Project, One Portal
Section titled “One Project, One Portal”Each project works on one HubSpot portal, the one you choose when you create it. Every chat in the project builds and deploys to that portal. To work on a client’s sandbox and production portals separately, create a project for each one.
What Jetty Can Build
Section titled “What Jetty Can Build”Jetty builds properties, pipelines, workflows, lists, forms, emails, reports, dashboards, and a range of HubSpot settings. Some of these need the Chrome extension to deploy. When Jetty can’t do something for you, it adds a You do this step with clear instructions, so nothing gets lost.
See What Jetty Can Build for the full list.
Web App and Chrome Extension
Section titled “Web App and Chrome Extension”- Web app: where you chat with Jetty, approve cards, and see your project.
- Chrome extension: helps scan the parts of HubSpot that JetStack AI can’t reach directly, and deploys certain asset types. When a deploy needs the extension, it waits in the extension’s Projects → Inbox until you have the client’s portal open in Chrome.
Both show the same project, so you can follow progress in either one.
Projects vs Implementations
Section titled “Projects vs Implementations”| Projects | Implementations | |
|---|---|---|
| You start with | A client’s portal, plus what you tell Jetty or upload | A portal you want to copy from |
| How it works | Jetty suggests; you approve each step | You pick the assets to copy |
| Best for | New builds and ongoing client work | Copying, migrating and cloning portals |
To copy a working portal’s setup onto another portal, use Implementations.
Next Steps
Section titled “Next Steps”- Getting Access: check that your organisation can use Projects
- Quickstart: go from a new project to live assets
- Chats & Cards: what each card does
- Deploying & Fixing: getting assets live and fixing problems
- What Jetty Can Build: the full list, and what stays manual
- Troubleshooting & Gotchas: common questions and fixes