@koda-sl/baker-cli 0.469.0-dev.42f26270e → 0.470.0-dev.fb31086c9

package/dist/hubspot-3FGLZWCQ.js

@@ -1,779 +0,0 @@
-import "./chunk-MH74GWNI.js";
-import {
-  failNotConnected
-} from "./chunk-NGB4ZYZV.js";
-import "./chunk-EDLZGTGN.js";
-import "./chunk-LAYWOVXE.js";
-import {
-  HUBSPOT_OPERATORS
-} from "./chunk-RPJYEJDQ.js";
-import "./chunk-GXDLWBOY.js";
-import "./chunk-GIWHHCD6.js";
-import "./chunk-XQIOCIDO.js";
-import "./chunk-I2DNBEV6.js";
-import {
-  ApiError,
-  apiPost
-} from "./chunk-L3EIZ7OV.js";
-import "./chunk-C4A5UGTT.js";
-import "./chunk-MSCFMNJP.js";
-import {
-  registerSchema,
-  writeJson
-} from "./chunk-KCA5CDCU.js";
-import "./chunk-YQSBHWOI.js";
-
-// src/commands/hubspot/index.ts
-import { defineCommand } from "citty";
-var EMBED_TYPES = ["legacy", "v4", "unknown"];
-function assertEmbedType(value) {
-  if (value === void 0) {
-    return void 0;
-  }
-  if (!EMBED_TYPES.includes(value)) {
-    throw new Error(`--embed-type must be one of: ${EMBED_TYPES.join("|")}`);
-  }
-  return value;
-}
-registerSchema({
-  command: "hubspot.forms.list",
-  description: "Start here for HubSpot forms: every form on the connected account, with just enough to choose one \u2014 embed type (legacy vs v4), field count, its post-submit action (inline thank-you vs redirect to a URL), and whether spam prevention (captcha) is on. A form with captcha on can be embedded on a page but can never receive a submission from a Form, so check it before wiring one as a destination. Answers 'which of my forms redirect after submit?' and 'is this form legacy or v4?'. portalId is returned once on data, not per row. Next step is usually `hubspot forms view <id> --as-node`, which gives you the blob to write straight into a Form step \u2014 you do not need request_flow_input for HubSpot.",
-  args: {
-    search: { type: "string", description: "Case-insensitive substring match on the form name", required: false },
-    "redirecting-only": {
-      type: "boolean",
-      description: "Only forms whose post-submit action redirects away",
-      required: false,
-      default: false
-    },
-    "embed-type": { type: "string", description: "Filter: legacy|v4|unknown", required: false, enum: [...EMBED_TYPES] }
-  }
-});
-registerSchema({
-  command: "hubspot.forms.view",
-  description: "One HubSpot form in detail: every field (name, label, type, required, hidden, options), the legal-consent mode, the post-submit action, captcha, and language. Read it before wiring a form into a Form (flow) so you know what fields exist to autofill. Add --full for the untouched HubSpot payload, or --as-node to get the object to write into the step's form.external instead.",
-  args: {
-    formId: { type: "positional", description: "HubSpot form id (from `baker hubspot forms list`)", required: true },
-    full: { type: "boolean", description: "Include the raw HubSpot payload", required: false, default: false },
-    "as-node": {
-      type: "boolean",
-      description: "Emit the resource blob to write into a flow node's form.external, instead of the readable view. Write it into the node yourself; no need for request_flow_input when the account is connected and the form is unambiguous.",
-      required: false,
-      default: false
-    }
-  }
-});
-registerSchema({
-  command: "hubspot.forms.submissions",
-  description: "How many leads a form actually received over a window, and on which days \u2014 the difference between 'this form is live' and 'this form is working'. Start here when asked whether a form or a campaign is producing leads. Returns counts and dates only; the leads' own answers need --full and are personal data, so do not put them in a report. Pair with `hubspot pipelines list` to see whether those leads were then worked.",
-  args: {
-    formId: { type: "positional", description: "HubSpot form id (from `baker hubspot forms list`)", required: true },
-    days: { type: "string", description: "Window in days, 1-365 (default 30)", required: false },
-    full: {
-      type: "boolean",
-      description: "Include each submission's field values \u2014 personal data, request only when actually needed",
-      required: false,
-      default: false
-    }
-  }
-});
-registerSchema({
-  command: "hubspot.contacts.summary",
-  description: "Whether the leads that arrived recently are actually being worked, as counts: how many contacts were created in the window, how many have someone assigned, and how they split across lifecycle stages. This is the 'have these leads been treated?' answer. Returns no names or emails \u2014 use `hubspot contacts lookup` for one specific person.",
-  args: {
-    days: { type: "string", description: "Window in days, 1-365 (default 30)", required: false }
-  }
-});
-registerSchema({
-  command: "hubspot.contacts.properties",
-  description: "Every contact property a HubSpot event can watch, with its `kind` (select, string, number, date, boolean) \u2014 which decides the operators the trigger takes \u2014 and, for a select, the `options` its values come from. Start here to make a HubSpot event: pick the property and condition that mean the outcome (a deal won is usually `lifecyclestage` is `customer`, a custom property the client's team sets, or a number crossing a threshold), then `baker analytics sources --create-hubspot --property <name> [--operator <op>] --value <value>\u2026` reads it every five minutes. Names are HubSpot's internal ones; use them as printed.",
-  args: {}
-});
-registerSchema({
-  command: "hubspot.contacts.fields",
-  description: "Every contact property on the connected HubSpot account \u2014 name, label, group and HubSpot's type \u2014 which is what a HubSpot event's rows can read: `baker analytics sources --create-hubspot \u2026 --field email={{work_email}} --field value={{deal_value}} --field currency=EUR`, or `--map` on an existing one. Names are HubSpot's internal ones; use them as printed, and `{{id}}` for the contact's own id. No personal data.",
-  args: {}
-});
-registerSchema({
-  command: "hubspot.contacts.lookup",
-  description: "One contact by email: its lifecycle stage, whether anyone is assigned, the account (company) it was filed under, and any deals it is attached to with their stage. Use it to settle whether a specific lead was picked up. `found: false` means the lead never reached the CRM at all \u2014 that is a finding, not an error. `dealsReadable: false` / `companyReadable: false` mean deals or account details were not readable on this connection, so an empty deals list or a null company is unknown rather than absent.",
-  args: {
-    email: { type: "positional", description: "The contact's email address", required: true }
-  }
-});
-registerSchema({
-  command: "hubspot.workflows.list",
-  description: "Every workflow on the connected account, with whether it is switched on. Read it when auditing what happens to a lead after it is captured \u2014 a form wired to a workflow that is off looks connected and does nothing.",
-  args: {
-    search: { type: "string", description: "Case-insensitive substring match on the workflow name", required: false },
-    "enabled-only": { type: "boolean", description: "Only workflows that are on", required: false, default: false }
-  }
-});
-registerSchema({
-  command: "hubspot.workflows.view",
-  description: "One workflow's actual configuration: what enrols a record, whether it re-enrols, and every step with the property it writes. Read it before saying a workflow is correct \u2014 `workflows list` only tells you it exists and whether it is on. Branches come back in HubSpot's order, and on a LIST_BRANCH step that is evaluation order (`order: 1` wins over `order: 2`) \u2014 which is where this kind of setup silently breaks: a broad branch placed above a narrow one swallows the records the narrow one was written for, and nothing reports it. A STATIC_BRANCH matches on a value instead, so its order carries no precedence. Steps are NOT in execution order \u2014 follow `nextActionId` from step to step. Add --full for the branch filter criteria (which property is compared to which value).",
-  args: {
-    workflowId: {
-      type: "positional",
-      description: "Workflow id (from `baker hubspot workflows list`)",
-      required: true
-    },
-    full: {
-      type: "boolean",
-      description: "Include the raw HubSpot payload \u2014 the only place the branch filter criteria can be read",
-      required: false,
-      default: false
-    }
-  }
-});
-registerSchema({
-  command: "hubspot.pipelines.list",
-  description: "The account's deal pipelines and their stages, in the order they run, each stage with `isClosed` / `isWon` (HubSpot's closed-won is closed with probability 1). Use it to answer where a lead lands once captured and whether it moved \u2014 the 'have these leads been worked?' half of a form audit \u2014 and to pick the pipeline ids for `hubspot deals list --pipeline`.",
-  args: {}
-});
-registerSchema({
-  command: "hubspot.meetings.list",
-  description: "Every HubSpot meeting link (calendar) on the connected account, with just enough to choose one: name, slug, link type (personal / group / round-robin), whether booking redirects somewhere, and how many booking fields it asks for (null = unknown, read it with `meetings view`). Next step is usually `hubspot meetings view <slug> --as-node`, which gives you the blob to write straight into a hubspotMeeting step.",
-  args: {
-    search: { type: "string", description: "Case-insensitive substring match on the meeting name", required: false },
-    "redirecting-only": {
-      type: "boolean",
-      description: "Only meeting links that redirect after booking",
-      required: false,
-      default: false
-    }
-  }
-});
-registerSchema({
-  command: "hubspot.meetings.view",
-  description: "One HubSpot meeting link in detail: its booking-form fields (name, label, type, required, custom), link, and redirect URL. This is the source of truth for a calendar's fields \u2014 the list command cannot see them reliably. Add --as-node to get the object to write into the step's form.external instead.",
-  args: {
-    slug: { type: "positional", description: "Meeting slug (from `baker hubspot meetings list`)", required: true },
-    "as-node": {
-      type: "boolean",
-      description: "Emit the resource blob to write into a flow node's form.external, instead of the readable view.",
-      required: false,
-      default: false
-    }
-  }
-});
-var formsListCommand = defineCommand({
-  meta: {
-    name: "list",
-    description: "List HubSpot forms with embed type and post-submit action. Example: baker hubspot forms list --redirecting-only"
-  },
-  args: {
-    search: { type: "string", description: "Match on form name", required: false },
-    "redirecting-only": { type: "boolean", description: "Only forms that redirect on submit", required: false },
-    "embed-type": { type: "string", description: "Filter: legacy|v4|unknown", required: false }
-  },
-  run: async ({ args }) => {
-    try {
-      const body = {};
-      if (args.search) {
-        body.search = args.search;
-      }
-      if (args["redirecting-only"]) {
-        body.redirectingOnly = true;
-      }
-      const embedType = assertEmbedType(args["embed-type"]);
-      if (embedType) {
-        body.embedType = embedType;
-      }
-      const response = await apiPost("/api/hubspot/forms/list", body);
-      const { forms } = response.data;
-      const redirecting = forms.filter((form) => form.postSubmitAction?.type === "redirect_url");
-      const hints = [];
-      if (forms.length === 0) {
-        hints.push("No forms matched. Drop --search/--embed-type, or check the connected HubSpot account.");
-      } else {
-        hints.push(
-          "To put one on a page: `baker hubspot forms view <id> --as-node` returns the object to write into the step's form.external. No request_flow_input needed for HubSpot."
-        );
-      }
-      if (redirecting.length > 0) {
-        hints.push(
-          `${redirecting.length} form(s) redirect after submit. That is fine mid-Form: the renderer suppresses the redirect whenever a step follows the form, and honors it when the form is the last step.`
-        );
-      }
-      const blocked = forms.filter((form) => form.captchaEnabled);
-      if (blocked.length > 0) {
-        const shown = blocked.slice(0, 3).map((form) => form.name);
-        const rest = blocked.length - shown.length;
-        hints.push(
-          `${blocked.length} form(s) have spam prevention (captcha) on: ${shown.join(", ")}${rest > 0 ? `, and ${rest} more` : ""}. HubSpot refuses every submission sent to those, so they can be embedded on a page but never wired as a Form's destination. Only the user can switch it off, on the form in HubSpot.`
-        );
-      }
-      writeJson({ ...response, meta: { count: forms.length }, ...hints.length > 0 ? { hints } : {} });
-    } catch (err) {
-      failNotConnected(err);
-    }
-  }
-});
-var CAPTCHA_VIEW_HINT = "This form has spam prevention (captcha) on. HubSpot refuses every submission sent to it, so it cannot be a Form's destination \u2014 embedding it on a page still works, because the visitor solves the captcha in the browser. Only the user can switch it off, on the form in HubSpot; do not wire a delivery to it, and tell them what has to change.";
-var CAPTCHA_NODE_HINT = "This form has spam prevention (captcha) on. That is fine for embedding it on a page \u2014 the visitor solves it in the browser \u2014 but it can never be a Form's delivery destination, so do not also wire a hubspotForm side effect to this form.";
-function formViewHints(form) {
-  const hints = [];
-  if (form.postSubmitAction?.type === "redirect_url") {
-    hints.push(
-      `This form redirects to ${form.postSubmitAction.value} on submit. Placed anywhere but the last step of a Form, that redirect is suppressed so the next step can render.`
-    );
-  }
-  if (form.captchaEnabled) {
-    hints.push(CAPTCHA_VIEW_HINT);
-  }
-  if (form.embedType === "unknown") {
-    hints.push("Embed type could not be determined from HubSpot's response; the renderer treats it as legacy.");
-  }
-  return hints;
-}
-function formNodeHints(external) {
-  return [
-    "Write this object into the node's `form.external` in the flow's _data.json, keeping the rest of the node as-is. No request_flow_input needed \u2014 the account is already connected.",
-    ...external?.captchaEnabled ? [CAPTCHA_NODE_HINT] : [],
-    ...external?.configuration?.postSubmitAction.type === "redirect_url" ? [
-      "This form redirects on submit. Safe unless it is the last step: the renderer suppresses the redirect whenever a step follows it."
-    ] : [],
-    ...external?.embedType === "v4" && !external.region ? [
-      "WARNING: this is a v4 form and the connected account has no region recorded, so the step will load HubSpot's na1 script host. That is correct for US portals and breaks the form on eu1/ap1 ones. If it renders blank, have the user reconnect HubSpot from Brain -> Integrations -> Tools, then re-run this command."
-    ] : []
-  ];
-}
-var formsViewCommand = defineCommand({
-  meta: {
-    name: "view",
-    description: "Show one HubSpot form's fields and configuration. Example: baker hubspot forms view 1a2b3c"
-  },
-  args: {
-    formId: { type: "positional", description: "HubSpot form id", required: true },
-    full: { type: "boolean", description: "Include the raw HubSpot payload", required: false },
-    "as-node": { type: "boolean", description: "Emit the node-ready form.external blob", required: false }
-  },
-  run: async ({ args }) => {
-    try {
-      const response = await apiPost("/api/hubspot/forms/view", {
-        formId: args.formId,
-        ...args.full ? { full: true } : {},
-        ...args["as-node"] ? { asNode: true } : {}
-      });
-      if (args["as-node"]) {
-        writeJson({ ...response, hints: formNodeHints(response.data.external) });
-        return;
-      }
-      const form = response.data.form;
-      if (!form) {
-        throw new Error("Response did not include the form view");
-      }
-      const hints = formViewHints(form);
-      writeJson({ ...response, meta: { count: form.fields.length }, ...hints.length > 0 ? { hints } : {} });
-    } catch (err) {
-      failNotConnected(err);
-    }
-  }
-});
-var meetingsListCommand = defineCommand({
-  meta: {
-    name: "list",
-    description: "List HubSpot meeting links (calendars). Example: baker hubspot meetings list"
-  },
-  args: {
-    search: { type: "string", description: "Match on meeting name", required: false },
-    "redirecting-only": { type: "boolean", description: "Only links that redirect after booking", required: false }
-  },
-  run: async ({ args }) => {
-    try {
-      const body = {};
-      if (args.search) {
-        body.search = args.search;
-      }
-      if (args["redirecting-only"]) {
-        body.redirectingOnly = true;
-      }
-      const response = await apiPost("/api/hubspot/meetings/list", body);
-      const { meetings } = response.data;
-      const hints = [];
-      if (meetings.length === 0) {
-        hints.push("No meeting links matched. Drop --search, or check the connected HubSpot account.");
-      } else {
-        hints.push(
-          "To put one on a page: `baker hubspot meetings view <slug> --as-node` returns the object to write into the step's form.external."
-        );
-      }
-      const unknown = meetings.filter((meeting) => !meeting.redirectKnown);
-      if (unknown.length > 0) {
-        hints.push(
-          `HubSpot did not report booking settings for ${unknown.length} of these (${unknown.map((meeting) => meeting.slug).join(
-            ", "
-          )}), so their redirect and field count are UNKNOWN, not absent. Run \`baker hubspot meetings view <slug>\` before concluding one does not redirect.`
-        );
-      }
-      writeJson({ ...response, meta: { count: meetings.length }, ...hints.length > 0 ? { hints } : {} });
-    } catch (err) {
-      failNotConnected(err);
-    }
-  }
-});
-var meetingsViewCommand = defineCommand({
-  meta: {
-    name: "view",
-    description: "Show one HubSpot meeting link's booking fields. Example: baker hubspot meetings view discovery-call"
-  },
-  args: {
-    slug: { type: "positional", description: "Meeting slug", required: true },
-    "as-node": { type: "boolean", description: "Emit the node-ready form.external blob", required: false }
-  },
-  run: async ({ args }) => {
-    try {
-      const response = await apiPost("/api/hubspot/meetings/view", {
-        slug: args.slug,
-        ...args["as-node"] ? { asNode: true } : {}
-      });
-      if (args["as-node"]) {
-        const { external } = response.data;
-        writeJson({
-          ...response,
-          hints: [
-            "Write this object into the node's `form.external` in the flow's _data.json, keeping the rest of the node as-is. No request_flow_input needed \u2014 the account is already connected.",
-            ...external?.customParams.redirectUrl ? [
-              `This calendar redirects to ${external.customParams.redirectUrl} after booking, and that redirect is NOT suppressed \u2014 any step placed after it is unreachable. Keep it as the last step, or ask the user to clear the redirect in HubSpot.`
-            ] : []
-          ]
-        });
-        return;
-      }
-      const meeting = response.data.meeting;
-      if (!meeting) {
-        throw new Error("Response did not include the meeting view");
-      }
-      const hints = [];
-      if (meeting.redirectUrl) {
-        hints.push(
-          `This calendar redirects to ${meeting.redirectUrl} after booking. A step placed after it will not be reached \u2014 keep it as the last step, or clear the redirect in HubSpot.`
-        );
-      }
-      writeJson({ ...response, meta: { count: meeting.fields.length }, ...hints.length > 0 ? { hints } : {} });
-    } catch (err) {
-      failNotConnected(err);
-    }
-  }
-});
-var formsSubmissionsCommand = defineCommand({
-  meta: {
-    name: "submissions",
-    description: "How many leads a form received, and when. Example: baker hubspot forms submissions <formId> --days 30"
-  },
-  args: {
-    formId: { type: "positional", description: "HubSpot form id", required: true },
-    days: { type: "string", description: "Window in days (default 30)", required: false },
-    full: { type: "boolean", description: "Include each lead's answers", required: false }
-  },
-  run: async ({ args }) => {
-    try {
-      const days = args.days === void 0 ? 30 : Number(args.days);
-      if (!Number.isInteger(days) || days < 1 || days > 365) {
-        throw new ApiError("VALIDATION_ERROR", "--days must be a whole number between 1 and 365.");
-      }
-      const response = await apiPost("/api/hubspot/forms/submissions", {
-        formId: args.formId,
-        days,
-        ...args.full ? { full: true } : {}
-      });
-      const { inWindow, total, truncated, lastSubmittedAt } = response.data;
-      const hints = [];
-      if (inWindow === 0) {
-        hints.push(
-          total === 0 ? "This form has received nothing at all \u2014 check it is the form actually embedded on the page before concluding the campaign is at fault." : `No leads in the last ${days} days, though the form has ${total} older submission(s). It worked once and has gone quiet.`
-        );
-      }
-      if (truncated) {
-        hints.push(
-          "Stopped before reaching the end of the window, so `inWindow` is a floor, not a count. Say so rather than reporting it as exact."
-        );
-      }
-      if (!args.full && inWindow > 0) {
-        hints.push(
-          "Counts only \u2014 the leads' own answers are not included. Add --full if you genuinely need the field values; it returns personal data, so do not paste it into a report or a chat message."
-        );
-      }
-      if (lastSubmittedAt !== null) {
-        hints.push(
-          "To find out whether these leads were worked, cross-check the deal pipeline: `baker hubspot pipelines list`."
-        );
-      }
-      writeJson({ ...response, meta: { count: inWindow }, ...hints.length > 0 ? { hints } : {} });
-    } catch (err) {
-      failNotConnected(err);
-    }
-  }
-});
-var workflowsListCommand = defineCommand({
-  meta: {
-    name: "list",
-    description: "List HubSpot workflows. Example: baker hubspot workflows list --enabled-only"
-  },
-  args: {
-    search: { type: "string", description: "Match on workflow name", required: false },
-    "enabled-only": { type: "boolean", description: "Only workflows that are on", required: false }
-  },
-  run: async ({ args }) => {
-    try {
-      const body = {};
-      if (args.search) {
-        body.search = args.search;
-      }
-      if (args["enabled-only"]) {
-        body.enabledOnly = true;
-      }
-      const response = await apiPost("/api/hubspot/workflows/list", body);
-      const { workflows } = response.data;
-      const off = workflows.filter((workflow) => !workflow.enabled);
-      const hints = [];
-      if (workflows.length === 0) {
-        hints.push("No workflows matched. Drop --search/--enabled-only, or the account genuinely has none.");
-      }
-      if (off.length > 0) {
-        hints.push(
-          `${off.length} of these are switched off. A form wired to a workflow that is off looks connected and does nothing \u2014 worth flagging to the user.`
-        );
-      }
-      writeJson({ ...response, meta: { count: workflows.length }, ...hints.length > 0 ? { hints } : {} });
-    } catch (err) {
-      failNotConnected(err);
-    }
-  }
-});
-function workflowViewHints(workflow) {
-  const hints = [];
-  if (!workflow.enabled) {
-    hints.push(
-      "This workflow is switched off, so nothing below it is running now \u2014 it may still have run while it was on. Say so before reporting on what it does."
-    );
-  }
-  const ordered = workflow.steps.filter((step) => step.type === "LIST_BRANCH" && (step.branches?.length ?? 0) > 1);
-  if (ordered.length > 0) {
-    hints.push(
-      "Branches are listed in evaluation order and the first match wins. Check that no broad branch sits above a narrower one \u2014 if it does, the narrow branch never runs and nothing in HubSpot reports it."
-    );
-  }
-  if (workflow.raw === void 0 && ordered.length > 0) {
-    hints.push(
-      "This view names the branches but not what they compare. Re-run with --full to read the filter criteria before judging whether a branch matches what it was meant to match."
-    );
-  }
-  if (workflow.enrollment.reEnrollment === false) {
-    hints.push(
-      "Re-enrolment is off: a record that meets the criteria a second time will not run through this again. That is a real choice, not necessarily a fault \u2014 but confirm it is the intended one."
-    );
-  } else if (workflow.enrollment.reEnrollment === null) {
-    hints.push(
-      "Whether this re-enrols is not reported for this kind of enrolment, so do not state it either way \u2014 read it in HubSpot if it matters."
-    );
-  }
-  return hints;
-}
-var workflowsViewCommand = defineCommand({
-  meta: {
-    name: "view",
-    description: "Read one workflow's real configuration \u2014 enrolment, branches in order, and what each step writes. Example: baker hubspot workflows view 121183594 --full"
-  },
-  args: {
-    workflowId: {
-      type: "positional",
-      description: "Workflow id (from `baker hubspot workflows list`)",
-      required: true
-    },
-    full: { type: "boolean", description: "Include the raw HubSpot payload with the filter criteria", required: false }
-  },
-  run: async ({ args }) => {
-    try {
-      const response = await apiPost("/api/hubspot/workflows/view", {
-        workflowId: args.workflowId,
-        ...args.full ? { full: true } : {}
-      });
-      const { workflow } = response.data;
-      const hints = workflowViewHints(workflow);
-      writeJson({ ...response, meta: { count: workflow.steps.length }, ...hints.length > 0 ? { hints } : {} });
-    } catch (err) {
-      failNotConnected(err);
-    }
-  }
-});
-var pipelinesListCommand = defineCommand({
-  meta: {
-    name: "list",
-    description: "List HubSpot deal pipelines and their stages. Example: baker hubspot pipelines list"
-  },
-  args: {},
-  run: async () => {
-    try {
-      const response = await apiPost("/api/hubspot/pipelines/list", {});
-      const { pipelines } = response.data;
-      const hints = pipelines.length === 0 ? ["This account has no deal pipelines, so there is nowhere for a lead to be worked."] : ["Stages are listed in the order they run in HubSpot, so the first stage is where a new lead lands."];
-      writeJson({ ...response, meta: { count: pipelines.length }, hints });
-    } catch (err) {
-      failNotConnected(err);
-    }
-  }
-});
-var OBJECT_WORDS = {
-  contact: {
-    plural: "contacts",
-    command: "baker hubspot contacts",
-    rows: '`--field email={{work_email}}`, `--field currency=EUR`, `--field first_name="{{firstname}} {{lastname}}"`; `{{id}}` is the contact\'s own id'
-  },
-  deal: {
-    plural: "deals",
-    command: "baker hubspot deals",
-    rows: "`--field value={{amount}}`, `--field currency={{deal_currency_code}}`, `--field email={{contact.email}}` \u2014 a deal's own properties bare, its contact's as `contact.<name>`; `{{id}}` is the deal's own id, `{{contact.id}}` the contact's"
-  },
-  lead: {
-    plural: "leads",
-    command: "baker hubspot leads",
-    rows: "`--field email={{contact.email}}`, `--field properties.stage={{hs_pipeline_stage}}` \u2014 a lead's own properties bare, its contact's as `contact.<name>`; `{{id}}` is the lead's own id, `{{contact.id}}` the contact's. A lead carries no amount of its own, so `value` is empty unless you point it at a property"
-  }
-};
-function propertiesCommand(object) {
-  const words = OBJECT_WORDS[object];
-  return defineCommand({
-    meta: {
-      name: "properties",
-      description: `List every ${object} property a HubSpot event can watch, with its kind, the operators that kind takes, and a select's values. Example: ${words.command} properties`
-    },
-    args: {},
-    run: async () => {
-      try {
-        const response = await apiPost("/api/hubspot/contacts/properties", {
-          object
-        });
-        const { properties } = response.data;
-        const operators = Object.entries(HUBSPOT_OPERATORS).map(([kind, list]) => `${kind}: ${list.map((operator) => operator.value).join(", ")}`).join(" \xB7 ");
-        const objectFlag = object === "contact" ? "" : ` --object ${object}`;
-        const hints = properties.length === 0 ? [`This account has no visible ${object} property, so there is nothing an event could watch.`] : [
-          `Pick the property and the condition that mean the outcome, then \`baker analytics sources --create-hubspot${objectFlag} --property <name> [--operator <op>] --value <value>\u2026\` (\`--value\` repeats for a list). Operators by kind \u2014 ${operators}. Counting starts from creation: a ${object} already satisfying it is not counted until it leaves and comes back.`
-        ];
-        writeJson({ ...response, meta: { count: properties.length }, hints });
-      } catch (err) {
-        failNotConnected(err);
-      }
-    }
-  });
-}
-var contactsPropertiesCommand = propertiesCommand("contact");
-var contactsSummaryCommand = defineCommand({
-  meta: {
-    name: "summary",
-    description: "Whether recent leads are being worked, as counts. Example: baker hubspot contacts summary --days 30"
-  },
-  args: {
-    days: { type: "string", description: "Window in days (default 30)", required: false }
-  },
-  run: async ({ args }) => {
-    try {
-      const days = args.days === void 0 ? 30 : Number(args.days);
-      if (!Number.isInteger(days) || days < 1 || days > 365) {
-        throw new ApiError("VALIDATION_ERROR", "--days must be a whole number between 1 and 365.");
-      }
-      const response = await apiPost("/api/hubspot/contacts/summary", { days });
-      const { total, withOwner, withoutOwner, byStage, truncated } = response.data;
-      const hints = [];
-      if (total === 0) {
-        hints.push(`No contacts were created in the last ${days} days \u2014 nothing reached the CRM in that window.`);
-      } else if (withOwner === 0) {
-        hints.push(
-          `None of these ${total} contacts has anyone assigned. That is the strongest available signal that the leads are arriving and nobody is picking them up \u2014 worth raising with the user.`
-        );
-      } else if (withoutOwner > withOwner) {
-        hints.push(`${withoutOwner} of ${total} contacts have nobody assigned \u2014 more unworked than worked.`);
-      }
-      const unset = byStage.find((entry) => entry.stage === "unset");
-      if (unset && unset.count > 0) {
-        hints.push(
-          `${unset.count} contact(s) have no lifecycle stage set at all, so they were created and never staged.`
-        );
-      }
-      if (truncated) {
-        hints.push("Stopped before reading every contact in the window, so these counts are floors, not totals.");
-      }
-      writeJson({ ...response, meta: { count: total }, ...hints.length > 0 ? { hints } : {} });
-    } catch (err) {
-      failNotConnected(err);
-    }
-  }
-});
-function contactLookupHints(data) {
-  const { found, contact, deals, dealsReadable, company, companyReadable } = data;
-  if (!found) {
-    return [
-      "No contact with that email. The lead never reached the CRM \u2014 check the form's submissions before assuming the CRM lost it."
-    ];
-  }
-  const hints = [];
-  if (contact?.ownerId === null) {
-    hints.push("Nobody is assigned to this contact.");
-  }
-  if (!dealsReadable) {
-    hints.push(
-      "Deals were not read: this HubSpot connection does not cover them. Do not report the lead as having no deal \u2014 you cannot tell. The user can enable it by reconnecting HubSpot."
-    );
-  } else if (deals.length === 0) {
-    hints.push("No deal is associated, so this contact was never taken into the pipeline.");
-  }
-  if (!companyReadable) {
-    hints.push(
-      "Account details were not read: this HubSpot connection does not cover them. Do not report the lead as having no account \u2014 you cannot tell. The user can enable it by reconnecting HubSpot."
-    );
-  } else if (company === null) {
-    hints.push(
-      "No account is associated either. Most B2B setups create one automatically when a contact arrives, so this usually means the lead was never processed at all \u2014 not that the account is missing."
-    );
-  }
-  return hints;
-}
-var contactsLookupCommand = defineCommand({
-  meta: {
-    name: "lookup",
-    description: "Find one contact by email and see whether it was worked. Example: baker hubspot contacts lookup a@b.com"
-  },
-  args: {
-    email: { type: "positional", description: "The contact's email address", required: true }
-  },
-  run: async ({ args }) => {
-    try {
-      const response = await apiPost("/api/hubspot/contacts/lookup", {
-        email: args.email
-      });
-      const hints = contactLookupHints(response.data);
-      writeJson({
-        ...response,
-        meta: { count: response.data.found ? 1 : 0 },
-        ...hints.length > 0 ? { hints } : {}
-      });
-    } catch (err) {
-      failNotConnected(err);
-    }
-  }
-});
-function fieldsCommand(object) {
-  const words = OBJECT_WORDS[object];
-  return defineCommand({
-    meta: {
-      name: "fields",
-      description: `List every property a HubSpot event on a ${object} can read into its rows, with HubSpot's type${object === "contact" ? "" : ` \u2014 the ${object}'s own, and its contact's as contact.<name>`}. Example: ${words.command} fields`
-    },
-    args: {},
-    run: async () => {
-      try {
-        const response = await apiPost("/api/hubspot/contacts/fields", { object });
-        const { fields } = response.data;
-        writeJson({
-          ...response,
-          meta: { count: fields.length },
-          hints: [
-            `A row of a HubSpot event is a template over these names: ${words.rows}. \`baker analytics sources --preview${object === "contact" ? "" : ` --object ${object}`} --property <p> --value <v> --field <row>\u2026\` reads one real ${object} to check the rows against.`
-          ]
-        });
-      } catch (err) {
-        failNotConnected(err);
-      }
-    }
-  });
-}
-var contactsFieldsCommand = fieldsCommand("contact");
-var dealsCommand = defineCommand({
-  meta: {
-    name: "deals",
-    description: "Deals on the connected HubSpot account: the deals themselves with amount and stage (`list`), and what a HubSpot event on a deal can watch (`properties`) and read (`fields`)."
-  },
-  subCommands: {
-    list: () => import("./crm-MJ2JTVJ4.js").then((m) => m.dealsListCommand),
-    properties: propertiesCommand("deal"),
-    fields: fieldsCommand("deal")
-  }
-});
-var leadsCommand = defineCommand({
-  meta: {
-    name: "leads",
-    description: "Leads on the connected HubSpot account: what a HubSpot event on a lead can watch (`properties`) and read (`fields`). Start here for qualification and disqualification \u2014 a lead's stage is where HubSpot records both, and `hs_pipeline_stage` lists the account's own stages with their labels. Needs Sales Hub Professional or Enterprise; on any other plan the account has no leads to read."
-  },
-  subCommands: { properties: propertiesCommand("lead"), fields: fieldsCommand("lead") }
-});
-var contactsCommand = defineCommand({
-  meta: { name: "contacts", description: "Contacts on the connected HubSpot account." },
-  subCommands: {
-    summary: contactsSummaryCommand,
-    lookup: contactsLookupCommand,
-    properties: contactsPropertiesCommand,
-    fields: contactsFieldsCommand
-  }
-});
-var companiesCommand = defineCommand({
-  meta: { name: "companies", description: "Companies (accounts) in the connected HubSpot CRM." },
-  subCommands: { search: () => import("./crm-MJ2JTVJ4.js").then((m) => m.companiesSearchCommand) }
-});
-var formsCommand = defineCommand({
-  meta: { name: "forms", description: "HubSpot forms on the connected account." },
-  subCommands: { list: formsListCommand, view: formsViewCommand, submissions: formsSubmissionsCommand }
-});
-var workflowsCommand = defineCommand({
-  meta: { name: "workflows", description: "HubSpot workflows on the connected account." },
-  subCommands: { list: workflowsListCommand, view: workflowsViewCommand }
-});
-var pipelinesCommand = defineCommand({
-  meta: { name: "pipelines", description: "HubSpot deal pipelines on the connected account." },
-  subCommands: { list: pipelinesListCommand }
-});
-var meetingsCommand = defineCommand({
-  meta: { name: "meetings", description: "HubSpot meeting links (calendars) on the connected account." },
-  subCommands: { list: meetingsListCommand, view: meetingsViewCommand }
-});
-var hubspotCommand = defineCommand({
-  meta: {
-    name: "hubspot",
-    description: `Read the connected HubSpot account \u2014 forms, the leads they received, workflows, deal pipelines, CRM
-companies and deals, and meeting links (calendars) \u2014 and get the blob to wire a form into a Form step yourself.
-
-Examples:
-  baker hubspot forms list                        # every form: embed type + post-submit action
-  baker hubspot forms list --redirecting-only     # which forms redirect away on submit
-  baker hubspot forms view <formId>               # fields, consent mode, full configuration
-  baker hubspot forms view <formId> --as-node     # the form.external blob -> write into the step
-  baker hubspot forms submissions <formId>        # how many leads it got, and when
-  baker hubspot workflows list --enabled-only     # what runs after a lead is captured
-  baker hubspot workflows view <workflowId>       # its real branches, in order, and what each step writes
-  baker hubspot pipelines list                    # where a lead lands, and the stages after it
-  baker hubspot contacts summary --days 30        # are recent leads being worked? (counts only)
-  baker hubspot contacts lookup a@b.com           # was this one lead picked up?
-  baker hubspot companies search --domains acme.com,globex.io --with-deals   # which are accounts, with deals
-  baker hubspot deals list --modified-since 2026-01-01                       # deals: amount, stage, closed won
-  baker hubspot deals properties                  # what a HubSpot event on a deal can watch (dealstage, amount\u2026)
-  baker hubspot deals fields                      # what its rows can read: the deal's own, its contact's as contact.<name>
-  baker hubspot meetings list                     # every calendar + whether booking redirects
-  baker hubspot meetings view <slug> --as-node    # same, for a hubspotMeeting step
-
-An account connected before one of these existed cannot serve it \u2014 you get HUBSPOT_RECONNECT_REQUIRED, which
-means HubSpot IS connected and the user has to reconnect it to widen what Baker may read. Report that and
-carry on with the rest; never call it broken and never retry.
-
-Nothing here is secret, so HubSpot steps do not need request_flow_input: take --as-node and edit the
-flow's _data.json. Use the approval form only when no account is connected or the right form is unclear.
-Full guide: __tooling__/docs/tools/baker/hubspot.md`
-  },
-  subCommands: {
-    forms: formsCommand,
-    workflows: workflowsCommand,
-    pipelines: pipelinesCommand,
-    contacts: contactsCommand,
-    companies: companiesCommand,
-    deals: dealsCommand,
-    leads: leadsCommand,
-    meetings: meetingsCommand
-  }
-});
-export {
-  contactLookupHints,
-  formNodeHints,
-  formViewHints,
-  hubspotCommand,
-  workflowViewHints
-};
-//# sourceMappingURL=hubspot-3FGLZWCQ.js.map