Deploying & Fixing

Nothing reaches HubSpot until you approve a card in a chat. This page explains what happens when you deploy, and what to do when something fails or someone changes an asset in HubSpot.

What’s Ready to Go Live

When Jetty sends a deploy card, each asset either goes live now or waits with a short reason. An asset that’s waiting never holds up the ones that are ready. Assets that rely on each other move together: a property, the pipeline that uses it and the workflow that uses both either deploy together or wait together.

What the card says	What it means
Waits for N other assets	Something it relies on isn’t ready yet
Something it depends on failed	Something it relies on failed, so it won’t be deployed yet
Waiting for your answer	It needs you to answer a question first
Still being built	It isn’t finished yet
Build failed	Jetty couldn’t build it. Ask Jetty to try again
Something in the portal already has this name	HubSpot already has an asset with this name
Already live	Nothing has changed since it was last deployed
Can’t be changed in place yet; remove and rebuild it	This kind of asset can’t be edited once it’s live
Deploying now	It’s already being deployed
You do this one by hand	A manual step for you

The Deploy Card

The card, for example “Deploy 12 assets to Acme Production?”, lists exactly what will go live:

Untick any asset you want to hold back.
If anything on the card changes before you approve it, the card won’t go through. Ask Jetty for a new one, so you always approve exactly what gets deployed.
If the portal’s connection to JetStack AI has expired, reconnect it under Client Accounts and try again.
When a change is for an asset that’s already live, Jetty only updates that exact asset. If it’s been deleted or replaced in HubSpot, the change isn’t made anywhere else.

Deploying Through the Chrome Extension

JetStack AI can reach most of HubSpot directly. Some areas are only available inside HubSpot itself, so those assets are deployed by the Chrome extension, which works through your HubSpot login:

Goes live right away	Needs the Chrome extension
Properties, custom objects, association labels, pipelines, lists, forms, marketing emails, workflows	HubSpot settings, permission sets, record page layouts, goals, goal templates, reports, dashboards, lead scores, CRM cards, preview views, snippets, sales templates, sequences, playbooks, task queues, deal tags

When a deploy has both kinds, the ones that go live right away are deployed first. That way, anything the extension deploys can use them.

The Extension Inbox

Open the extension on the client’s portal and go to Projects → Inbox (“Work waiting for this browser”). Each deploy you’ve approved shows up there with a Start button (Resume or Retry if it was interrupted). The inbox only shows work for the portal you have open, so you can’t deploy into the wrong portal by mistake.

The deploy card tells you in advance what to expect. If the extension isn’t open, you’ll see: “No extension is open on this portal right now. The task waits in Projects → Inbox until a HubSpot tab is open in Chrome.”

Receipts

When a deploy finishes, you get a receipt in the chat. It lists every asset and its result, gives an Open in HubSpot link for each live asset, and shows HubSpot’s exact message for anything that failed. The same results are saved in Deploy logs.

Fixing Failures

If one asset fails, the rest of the deploy carries on. Only the assets that rely on the failed one wait. Jetty then sends a fix card:

For each failure, the card shows HubSpot’s message and what Jetty will change.
Fix and deploy fixes everything and deploys it again in one click.
A new receipt shows how it went.

If an asset can’t be fixed, or it needs the Chrome extension, the receipt says so. For extension assets, ask Jetty to deploy again after the fix.

If an asset failed to build, it never reached HubSpot. Ask Jetty to try again, and it adds the asset to a new plan.

When Someone Changes an Asset in HubSpot

If someone edits a deployed asset directly in HubSpot, the asset shows Changed in HubSpot. Jetty offers a fix card that shows what changed. Keep HubSpot’s version accepts their edit. To go back to your project’s version, ask Jetty to change it back.

Changing Assets That Are Already Live

To change something that’s already live, ask Jetty. It adds a change to the plan that edits only what’s needed and never renames or recreates the asset. You can change properties, pipelines, lists that update automatically, reports, and workflows that are switched off, as long as this project built them.

Setup Remaining

Some assets go live correctly but still need a finishing step from you in HubSpot. They show a Setup remaining badge in the chat, the asset panel and the Canvas, with numbered steps: “Complete and verify these steps in HubSpot before relying on this asset.” For example:

a workflow that needs a real owner assigned, or a Slack or task step finished, before you switch it on
a record page layout that couldn’t be assigned to a team
an SLA goal that’s ready but switched off, for you to switch on

The badge stays until the steps are done.

After You Deploy

Workflows are always created switched off. Check who they’ll enroll and finish any setup steps, then switch them on in HubSpot.
Settings and SLAs are never switched on unless you asked. Jetty tells you what to switch on.
Lists that update automatically start filling with matching records straight away.
Nothing is deleted or reset when you deploy. Existing stage rules, form fields and team assignments are kept.

Next Steps

Chats & Cards: every card in detail
What Jetty Can Build: which assets need the extension
Troubleshooting & Gotchas: common deploy problems
Extension Overview: more about the Chrome extension