Skip to content
JetStack AI Documentation

Projects Quickstart

This guide takes you from a new project to assets that are live in your client’s HubSpot portal. It all happens in one chat, and nothing changes in HubSpot until you approve it.

Before You Start

Section titled “Before You Start”

You’ll need:

  • Projects access for your organisation
  • The client’s HubSpot portal connected to JetStack AI. See Connecting a Portal
  • The JetStack AI Chrome extension, installed and signed in. Some parts of the scan and some asset types need it
  • Ideally, a build spec or other client material: field lists, pipeline stages, workflow descriptions, call notes. Jetty uses the exact names and values you give it

Step 1: Create the Project

Section titled “Step 1: Create the Project”
  1. In the dashboard, click Projects in the left sidebar.
  2. Click New project.
  3. Enter a name (for example, “Acme Corp — RevOps Build”) and choose the client’s HubSpot portal. Everything in this project is built in that portal.
  4. Click Create project. Your first chat opens straight away.

Step 2: Let the Scan Run

Section titled “Step 2: Let the Scan Run”

JetStack AI starts scanning the portal as soon as the project is created, so Jetty knows what’s already there. You’ll see “Reading the portal in the background. You can start chatting right away.”

The scan has two parts. You can follow both on the Portal data card on the Overview page:

  • HubSpot API scan: runs by itself.
  • Extension scan: covers settings and assets that JetStack AI can only reach through your browser, such as reports, dashboards and record layouts. Open the client’s portal in Chrome with the extension signed in, and it runs.

Until a part of the portal has been scanned, Jetty tells you it can’t see it yet. It won’t assume that part is empty.

Step 3: Tell Jetty What You Need

Section titled “Step 3: Tell Jetty What You Need”

Type your request (“Tell Jetty what to build or change…”), or click Upload a build spec to add a document. PDF, Word, text, CSV, JSON and Markdown files all work.

Jetty checks your documents and the portal before suggesting anything, so it won’t rebuild something that already exists. If it truly needs a decision from you, it asks with a questions card. For example, two documents might disagree, or a value might be missing everywhere. Pick an option or type your own answer.

Step 4: Approve the Plan

Section titled “Step 4: Approve the Plan”

Jetty sends a plan that lists every asset it will create or change, one line each. For example: “Revenue stream: deal dropdown with Direct, Partner, Tender.” Anything marked You do this is a step Jetty can’t do for you. It comes with instructions.

Press Build N assets to start. (The button says Change N assets if the plan only changes existing assets, and Not now declines the plan.) Assets waiting on one of your answers are built too, and Jetty updates them once you answer.

A progress card shows what’s being built. When it’s done, you get a receipt. Built means ready for review. Nothing is in HubSpot yet.

Step 5: Deploy

Section titled “Step 5: Deploy”

Ask Jetty to deploy. It sends a deploy card, for example “Deploy 12 assets to Acme Production?”, which shows:

  • which assets are ready to go live, and which have to wait and why
  • which assets go live straight away, and which need the Chrome extension
  • whether anything clashes with what’s already in the portal

You can untick assets you don’t want yet. When you approve, most assets go live right away. Assets that need the extension wait in the extension’s Projects → Inbox and go live once you have the client’s portal open in Chrome.

Step 6: Check the Receipt

Section titled “Step 6: Check the Receipt”

When the deploy finishes, you get a receipt that lists every asset and its result, with an Open in HubSpot link for each live asset. If something failed, you see HubSpot’s exact message.

For anything that failed, Jetty offers a fix card that explains what it will change. Fix and deploy fixes it and deploys it again in one click. See Deploying & Fixing.

Some assets go live but still need a finishing touch from you in HubSpot. For example, a workflow might need an owner assigned before you switch it on. Those assets show a Setup remaining badge with the steps.

What’s Next

Section titled “What’s Next”
  • Start a new chat for each new task. Everything you’ve already built can be used in later chats.
  • Overview shows everything waiting on you, across all chats.
  • Canvas shows the portal and all your project’s assets. Scan again whenever the client’s team has made changes.
  • Deploy logs keep a history of every deploy.
  • Settings is where you add teammates.

Next Steps

Section titled “Next Steps”