Set-Up Guide: How to install DoQuotes Modules for Revenue Hub Quotes

INDEX

About DoQuotes Modules

• Part A: One-time computer setup

  • 1. Install Node.js and the HubSpot CLI (on your Mac or PC)

• Part B: Set up DoQuotes Modules

  • 2. Create your HubSpot quote project and add DoQuotes' modules
  • 3. Deploy the DoQuotes project to your HubSpot portal

• Part C: Using DoQuotes Modules

  • 4. Add a DoQuotes module to a quote template or draft quote

What's next

Appendix: How to delete DoQuotes Modules

 

About DoQuotes Modules

This guide covers DoQuotes Modules — the custom, buyer-facing quote modules that add to a HubSpot Revenue Hub quote template: form fields (text, number, date, dropdown, radio, checkbox) that save a buyer's answer back to a HubSpot property, plus a flexible column layout module. It walks through installing DoQuotes Modules into a brand-new HubSpot portal for the first time, from your computer's prerequisites through adding your first module to a quote.

This guide has three parts. Part A (step 1) sets up your computer once — you won't need to repeat it for future portals. Part B (steps 2-3) sets up DoQuotes Modules once per portal. Part C (step 4) is what you'll come back to any time you want to use a module — it's not a one-time setup step like Parts A and B.

↑ Back to top

Part A: One-time computer setup

 

1. Install Node.js and the HubSpot CLI (on your Mac or PC)

DoQuotes modules are installed using two small developer tools: Node.js (runs the install scripts) and the HubSpot CLI — CLI stands for Command Line Interface, HubSpot's own tool for uploading your quote project to HubSpot. Both are installed once per computer, not once per portal.

1. Open the Terminal app on your Mac, or Command Prompt on Windows:

   1. Press Cmd + Space to open Spotlight, then type Terminal. Once it appears in the results, press Return, or double-click it, to open it.

      

   2. You'll see a plain window with a line ending in a $, waiting for you to type — that's the prompt. Everything below gets typed after it, followed by Return.

      

2. Check whether Node.js is already installed. Type node -v and press Enter.

   That's a hyphen, then a lowercase v — not the number 1. It's an easy mistake to make; if Terminal says it can't find what you typed, just try again.

   If you see a version number of v20 or newer (e.g. v22.23.2), you're set — skip straight to installing the HubSpot CLI below. If you see "command not found," or a version below 20, install it:

   1. Go to nodejs.org and click the green Get Node.js button.

   2. The page that opens defaults to showing a command-line install method first (a block of text starting with curl) — you can skip past that. Scroll down to the direct-download section and click the green button labelled macOS Installer (.pkg) (or Windows Installer (.msi) on Windows).

      

   3. Run the downloaded installer, accepting all of its default options. Partway through, macOS will ask for your fingerprint or password to allow the install — this is normal for any installer, not a sign of a problem.

   4. Come back to Terminal and repeat this check (node -v) to confirm it worked.

3. Install the HubSpot CLI. Type:

   sudo npm install -g @hubspot/cli

   You'll be asked for your Mac password again, the same as during the Node.js install above. This adds a new command, hs, that you'll use throughout the rest of this guide.

   

↑ Back to top

Part B: Set up DoQuotes Modules

 

2. Create your HubSpot quote project and add DoQuotes' modules

You'll do this once per HubSpot portal you set up DoQuotes on. One command now creates the project, adds DoQuotes' modules, and installs everything it needs — you'll end this step ready to deploy.

What's a "project" here? Just a folder on your computer — the command below creates one (named doquotes) and fills it with the files HubSpot needs to build and upload your modules. It's a technical term borrowed from HubSpot's own developer tools, not a "project" in the everyday work-task sense.

1. In Terminal, go to the folder on your computer where you'd like the doquotes project folder to be created — for example your Desktop:

   cd ~/Desktop

2. Type npx @hubdo/doquotes and press Enter. This downloads DoQuotes' setup script and runs it, which creates a new doquotes project folder inside the folder you just navigated to, and fills it with the files HubSpot needs to build and upload your modules.

1. The first time you run this, npm hasn't downloaded DoQuotes yet, so it will ask something like:

   Need to install the following packages:
   @hubdo/doquotes@1.1.0
   Ok to proceed? (y)

   Type y and press Enter (or just press Enter on its own — this prompt defaults to y either way).

1. It then confirms where it's about to create the project folder, and asks before doing anything:

   This will create a new HubSpot quote project at:
     /Users/yourname/Desktop/doquotes
   
   Create it? (y/N)

   Type y and press Enter — this prompt defaults to No, so you must type y yourself for it to proceed.

    

2. You'll then see the project folder created, followed by a confirmation listing everything DoQuotes added to it — a set of shared files followed by one entry per module:

   ✔ Created the project (11 files).
   
   ✔ Installed:
     - shared/ConditionalVisibility.tsx
     - shared/CrmPropertyTargetFields.tsx
     ... (26 shared files in total)
     - modules/FieldDatePicker
     - modules/FieldDropdownSelect
     - modules/FieldMultiLineText
     - modules/FieldNumber
     - modules/FieldRadioSelect
     - modules/FieldSingleCheckbox
     - modules/FieldSingleLineText
     - modules/LayoutColumns

   That's seven Field modules and one Layout module — this matches everything DoQuotes currently ships, so this list is the same every time you run this command fresh. (The exact file counts may differ slightly from what you see, as DoQuotes adds new files over time.)

    

3. It then installs everything the project needs, which takes a minute or two and prints a lot of text. You don't need to read or act on any of it — just wait for the ✔ Ready. message below.

1. You'll know it worked when you see: ✔ Ready.

Move into your new project folder:

cd doquotes

Then continue to the next step below to deploy it — don't run hs project upload yet. You need to make sure you're authenticated to the correct HubSpot portal first, which the next step covers.

↑ Back to top

 

3. Deploy the DoQuotes project to your HubSpot portal

You should still be in your new doquotes project folder from the end of step 2 — if you're not sure, or opened a new Terminal window, run cd doquotes again first (from wherever you created it on your computer). Before running hs project upload, first make sure you're authenticated to the correct HubSpot portal and that it's set as your default — here's how:

1. In Terminal, type hs account use and press Enter. This lists every HubSpot portal you've already connected the CLI to — if more than one is listed, use the up and down arrow keys to highlight the correct one for this project, then press Enter to select it.

2. If your portal isn't listed at all, you haven't connected the CLI to it yet. Type hs account auth and press Enter, then use the arrow keys to choose Authenticate a new account from the list and press Enter — then follow these sub-steps:

   1. Your browser opens automatically to a HubSpot page for generating a CLI Personal Access Key — nothing else to type in Terminal yet.

      

   2. In the browser: choose which HubSpot portal to connect, and confirm the permission scopes shown. Leave all scopes selected — these control what the CLI itself can do (like hs project upload), not DoQuotes' own permissions, and deselecting one can cause project uploads to fail later for no obvious reason.

   3. Once confirmed, the key is sent straight back to the CLI automatically — there's nothing to copy or paste. Terminal shows ✔ Personal access key received.

      

   4. Terminal then suggests a name for this connection, based on your own portal's name — for example, ✔ Enter a unique name to reference this account in the CLI: acme-inc if your portal is called "Acme Inc." (yours will be based on your own portal's name, not this example). Press Enter to accept the suggested name, or type your own (no spaces).

   5. Terminal then asks you to confirm that name as your default account, e.g. ? Set acme-inc as your default account? [--default] (y/N). Type y and press Enter — this prompt defaults to No, so you must type y yourself for it to proceed. Setting it as default means the commands below will automatically target this portal without you needing to specify it each time.
   6. Once you're authenticated, type:

   hs project upload

3. You'll likely see two warnings before anything else happens:

   ⚠ WARNING Project lint: lint packages not installed for src/cms-assets/my-react-assets. Run `hs project lint` to install them.
   ⚠ WARNING npm audit: security issues found for src/cms-assets/my-react-assets: 20 total (4 high, 14 moderate, 2 low)

   Both are safe to ignore — the same underlying "vulnerabilities" you saw during step 2, and an optional linting step you don't need for this setup.

    

4. Since this project doesn't exist in your portal yet, you'll be asked:

   ? [--forceCreate] The project doquotes does not exist in acme-inc [test account] (123456789). Would 
   you like to create it? (Y/n)

   Type Y and press Enter (or just press Enter on its own — this prompt defaults to Yes since the Y is capitalized). (The account name and number shown here are your own — acme-inc and 123456789 above are just an example, taken from one of HubDo's own test portals, not values to expect literally.)
5. HubSpot then creates the project, uploads your files, and automatically builds and deploys it, all in one go, with no further prompts:

   ✔ SUCCESS New project doquotes successfully created in acme-inc [test account] (123456789).
   ✔ Uploaded doquotes project files to acme-inc [test account] (123456789)
   View build #1 in HubSpot: https://app.hubspot.com/developer-projects/123456789/project/doquotes/activity/build/1
   ✔ Built doquotes #1
   --------------------------------------------------
   Build #1 succeeded. Automatically deploying to acme-inc [test account] (123456789)
   View deploy of build #1 in HubSpot: https://app.hubspot.com/developer-projects/123456789/project/doquotes/activity/deploy/1
   ✔ Deployed build #1 in doquotes

6. Once you see "Deployed build #1 in doquotes," your DoQuotes modules are live in the portal and ready to add to a quote. You're finished with Terminal at this point — it's safe to close the window.

↑ Back to top

Part C: Using DoQuotes Modules

Parts A and B above are one-time setup. Everything below is what you'll come back to whenever you want to add a module to a new template, or to a single quote — as often as you like, on any portal Part B has already been run on.

 

4. Add a DoQuotes module to a quote template or draft quote

Decide first whether you want the module on a template (every future quote made from it will include it) or on a single draft quote (a one-off change, without touching the shared template).

To add it to a template:

1. In your portal, go to Settings → Objects → Quotes → Quote Templates → Open template library.
2. Create a new quote template, or open an existing one to edit it — if it's already published, unpublish it first so you can make changes.
3. Decide where in the template you'd like to add a module.

4. Use the + (plus) icon at the top-left of the editor to add a module to the template.

   

5. Choose one of DoQuotes' modules in the picker — e.g. Field: Single-text or Layout: Columns — and drag and drop it onto the template.

6. Configure the module using the panel on the left side of the editor.
7. When you're done, publish the template to make it available for new quotes.

To add it to a single draft quote instead:

1. Open the quote — it needs to still be in Draft status — in the quote editor.
2. The same + (plus) icon and module picker work directly inside an individual quote, the same way as on a template.
3. Configure the module using the panel on the left side of the editor.
4. Publish the quote when you're done, to make it available to the buyer.

↑ Back to top

 

What's next

If you haven't already, install the main DoQuotes app and make sure it has an active free trial or subscription — that's the only back-end step Field modules need in order to save a buyer's answer. See Set-Up Guide: How to install DoQuotes.

Any problems at all, contact support@hubdo.com.

↑ Back to top

 

Appendix: How to delete DoQuotes Modules

1. Go to Developer Projects in your portal, open the doquotes project (or whatever you named it — see step 2), go to its Settings tab, then click Delete Project.
2. This removes all DoQuotes modules from the "add to quote template" drag-and-drop panel in the template and quote editor. HubSpot also removes DoQuotes modules already placed on templates and on draft quotes.
3. Published quotes keep working exactly as before — the one exception is if a published quote is later recalled back to draft mode for editing: since the modules project no longer exists at that point, its DoQuotes modules are no longer available in that draft.
4. No data is lost that was already captured via a DoQuotes module on a published quote. All module data is saved to ordinary HubSpot properties on the quote, the deal, and the buyer and billing companies — deleting the project doesn't touch any of it.

↑ Back to top