Chats & Cards
Everything in a project happens in a chat. Jetty can look at the portal, read your documents and answer questions. Whenever it wants to build, deploy, fix, remove or scan something, it sends you a card, and nothing happens until you press the card’s button.
- One chat per task. Click New chat in the sidebar whenever you start something new. You can rename a chat, archive it when you’re done, and restore it later.
- The sidebar shows how each chat is doing: Working, Waiting for you, Needs a fix, or a short summary such as Live · 12 deployed.
- Assets are shared across chats. Anything built in one chat can be used in another. Each asset shows which chat it came from.
- The panel on the right lists the assets in the chat and their status. Click one to see its details and any setup that’s still needed.
When Jetty Asks You Something
Section titled “When Jetty Asks You Something”Jetty tries not to ask more than it needs to. Before asking, it:
- Looks for the answer itself, in your documents, earlier messages, and the portal (existing stages, dropdown options, owners, teams).
- Picks a sensible default for small choices like naming, and tells you which one it picked.
- Asks you only when it can’t go ahead without a decision: two sources disagree, a business detail is missing, or an asset can’t be built without a certain value.
It doesn’t wait on you for everything. Assets that don’t depend on your answer are built straight away.
The Cards
Section titled “The Cards”| Card | When Jetty sends it | What the button does |
|---|---|---|
| Plan | It’s worked out what to build or change | Builds everything on the plan |
| Questions | It needs a decision from you | Saves your answers so the waiting assets can be finished |
| Deploy | Your assets are built and ready for HubSpot | Puts them live in HubSpot |
| Fix | A deploy failed, or someone changed an asset in HubSpot | Fixes and redeploys, or keeps HubSpot’s version |
| Remove | You asked to delete assets from HubSpot | Deletes them, once you’ve typed the confirmation |
| Rescan | Jetty needs a fresh look at the portal | Scans the portal again |
| Receipt | A build or deploy has finished | Nothing to press. It’s the record of what happened |
Each card shows where it’s at: Waiting for you, Approved, Declined, Answered, or Replaced by a newer card. Clicking twice by accident won’t do anything twice.
The plan lists every asset Jetty proposes, grouped by type, with one line on what each one does. Each line is one of three kinds:
- New: an asset Jetty will create.
- Change: an edit to something that already exists. Jetty only changes what’s needed. It never renames or recreates existing assets.
- You do this: a step Jetty can’t do for you, with instructions.
If your document spells out exact fields, options, stages or workflows, Jetty uses your exact names and values. If it leaves anything from the document off the plan, it tells you what and why.
Press Build N assets (or Change N assets) to start. The assets appear in the right-hand panel as Planned and fill in as they’re built.
Questions
Section titled “Questions”Each question says which asset it’s for and what Jetty already checked. It offers options, with Jetty’s suggestion marked. Choose one or type your own answer.
- If you answer before building, the build uses your answer.
- If you answer after building, the asset shows Answer saved · updating while Jetty updates it.
Deploy
Section titled “Deploy”The deploy card shows exactly what will go live, what has to wait and why, and which assets need the Chrome extension. Approving it deploys exactly what’s on the card. If something changes before you approve, for example because Jetty updated an asset, the card won’t go through. Ask Jetty for a new one. See Deploying & Fixing.
- When a deploy fails, the card shows HubSpot’s message for each failure and what Jetty will change. Fix and deploy (or Fix all N and deploy) fixes everything and deploys it again in one click.
- When someone changes an asset in HubSpot, the asset shows Changed in HubSpot. Keep HubSpot’s version accepts their change.
Remove
Section titled “Remove”Deleting from HubSpot can’t be undone, so it always has its own card, “Remove N assets from HubSpot?”. The card shows what will be affected. You may need to type a confirmation word before the button works. Each live asset gets its own card.
Rescan
Section titled “Rescan”Jetty offers a rescan when it can’t see part of the portal, or when what it saw last is out of date. The card says whether it will run the HubSpot API scan, the Extension scan, or both.
Receipt
Section titled “Receipt”When a build or deploy finishes, a receipt lists every asset and its result, with Open in HubSpot links for live assets. Failures show HubSpot’s own message. Jetty doesn’t write receipts, and it won’t claim anything a receipt doesn’t show.
Asset Statuses
Section titled “Asset Statuses”You’ll see these statuses in the chat, on the Canvas and on the Overview:
| Status | What it means |
|---|---|
| Failed | Something went wrong. The reason is shown |
| Needs your answer | Waiting for you to answer a question |
| Answer saved · updating | Jetty is updating it with your answer |
| Building / Deploying | In progress |
| In extension inbox | Waiting for the Chrome extension to put it live |
| Live | In HubSpot |
| Changed in HubSpot | Live, but someone has edited it in HubSpot since |
| Ready | Built and ready to deploy |
| Planned | On an approved plan, not built yet |
| Removed | Deleted from HubSpot |
| You do this / Couldn’t build · you do this | A step for you to do in HubSpot, with instructions |
When an asset shows Ready · setup needed or Live · setup needed, there’s a finishing step for you in HubSpot. See Setup remaining.
Requirements
Section titled “Requirements”When your documents list requirements, the Requirements section on the Overview tracks each one:
| Status | What it means |
|---|---|
| Not linked to a build | Nothing has been built for it yet |
| Planned | It’s on an approved plan |
| Built | The assets for it are built |
| Setup remaining | Deployed, but there’s still a step for you in HubSpot |
| Saved configuration checked | We checked HubSpot and the setup was saved correctly |
| Acceptance check pending | Not yet confirmed as working for the business |
“Saved configuration checked” means HubSpot saved what was asked for. It doesn’t mean a workflow has run yet, or that a report shows the right numbers. Check those yourself.
Credits
Section titled “Credits”Chatting with Jetty and building assets use your organisation’s Projects credits. If you run out:
- A message Jetty couldn’t answer is marked Not answered — not enough Projects credits. Your message is kept.
- A build that’s in progress pauses instead of failing. Click Add credits to resume, and it continues where it left off.
Next Steps
Section titled “Next Steps”- Deploying & Fixing: what happens when you deploy
- What Jetty Can Build: what can go on a plan
- Troubleshooting & Gotchas: common questions and fixes