@dench.com/cli 2.2.0 → 2.2.1

package/crm.ts

@@ -509,6 +509,23 @@ const api = {
   members: {
     list: makeFunctionReference<"query">("functions/crm/members:list"),
   },
+  automations: {
+    list: makeFunctionReference<"query">("functions/crm/automations:list"),
+    setEnabled: makeFunctionReference<"mutation">(
+      "functions/crm/automations:setEnabled",
+    ),
+  },
+  templates: {
+    listAvailable: makeFunctionReference<"query">(
+      "functions/crm/templates:listAvailable",
+    ),
+    install: makeFunctionReference<"mutation">(
+      "functions/crm/templates:install",
+    ),
+    removeSampleData: makeFunctionReference<"mutation">(
+      "functions/crm/templates:removeSampleData",
+    ),
+  },
 };
 
 export async function runCrmCommand(opts: {
@@ -573,6 +590,10 @@ export async function runCrmCommand(opts: {
       return await runDocsCommand(ctx);
     case "actions":
       return await runActionsCommand(ctx);
+    case "automations":
+      return await runAutomationsCommand(ctx);
+    case "templates":
+      return await runTemplatesCommand(ctx);
     case "members":
       // Alias for `dench members` so the AI agent finds the roster
       // surface from inside the `dench crm` namespace it's primed
@@ -584,6 +605,81 @@ export async function runCrmCommand(opts: {
   }
 }
 
+/**
+ * `dench crm automations …` — deterministic CRM rules (installed by
+ * templates, e.g. "qualified prospect → opportunity"). These fire inside
+ * entry writes automatically; this surface is for visibility and the
+ * enable/disable kill switch. There is no create verb here — rules are
+ * installed by `crm templates install` (or programmatically).
+ */
+async function runAutomationsCommand(ctx: CrmCliContext): Promise<void> {
+  const verb = ctx.args.shift();
+  switch (verb) {
+    case "list": {
+      assertNoUnknownFlags(ctx.args, "crm automations list");
+      out(ctx, await callQuery(ctx, api.automations.list, {}));
+      return;
+    }
+    case "enable":
+    case "disable": {
+      const automationId = shift(ctx.args, "automation id");
+      assertNoUnknownFlags(ctx.args, `crm automations ${verb}`);
+      out(
+        ctx,
+        await callMutation(ctx, api.automations.setEnabled, {
+          automationId,
+          enabled: verb === "enable",
+        }),
+      );
+      return;
+    }
+    default:
+      throw new CrmCliError(
+        `Unknown automations verb: ${verb ?? "(none)"}. Use list | enable <id> | disable <id>.`,
+      );
+  }
+}
+
+/**
+ * `dench crm templates …` — one-click CRM setups (objects + fields +
+ * kanban statuses + pinned views + automations + sample rows tagged
+ * "Sample"). Installs are idempotent and compose across templates.
+ */
+async function runTemplatesCommand(ctx: CrmCliContext): Promise<void> {
+  const verb = ctx.args.shift();
+  switch (verb) {
+    case "list": {
+      assertNoUnknownFlags(ctx.args, "crm templates list");
+      out(ctx, await callQuery(ctx, api.templates.listAvailable, {}));
+      return;
+    }
+    case "install": {
+      const templateId = shift(ctx.args, "template id");
+      assertNoUnknownFlags(ctx.args, "crm templates install");
+      out(
+        ctx,
+        await callMutation(ctx, api.templates.install, { templateId }),
+      );
+      return;
+    }
+    case "remove-sample-data": {
+      const templateId = shift(ctx.args, "template id");
+      assertNoUnknownFlags(ctx.args, "crm templates remove-sample-data");
+      out(
+        ctx,
+        await callMutation(ctx, api.templates.removeSampleData, {
+          templateId,
+        }),
+      );
+      return;
+    }
+    default:
+      throw new CrmCliError(
+        `Unknown templates verb: ${verb ?? "(none)"}. Use list | install <id> | remove-sample-data <id>.`,
+      );
+  }
+}
+
 async function runCrmMembersCommand(ctx: CrmCliContext): Promise<void> {
   const { runMembersCommand } = await import("./members");
   // Re-prepend `--json` so the members dispatcher's own `hasFlag`
@@ -634,6 +730,11 @@ async function runObjectsCommand(ctx: CrmCliContext): Promise<void> {
       const description = getFlag(ctx.args, "--description");
       const defaultView = getFlag(ctx.args, "--default-view") as any;
       const icon = getFlag(ctx.args, "--icon");
+      // Cosmetic relabels (UI only; canonical `name` is unchanged, so
+      // protected objects like `people` can be shown as e.g. "Clients").
+      // Pass an empty string to clear back to the default label.
+      const displayName = getFlag(ctx.args, "--display-name");
+      const displayNameSingular = getFlag(ctx.args, "--display-name-singular");
       assertNoUnknownFlags(ctx.args, "crm objects update");
       out(
         ctx,
@@ -642,6 +743,8 @@ async function runObjectsCommand(ctx: CrmCliContext): Promise<void> {
           description,
           defaultView,
           icon,
+          displayName,
+          displayNameSingular,
         }),
       );
       return;
@@ -2618,7 +2721,9 @@ Objects (CRM tables):
   dench crm objects list [--json]
   dench crm objects get <name>
   dench crm objects create <name> [--description ...] [--default-view kanban] [--icon ...]
-  dench crm objects update <name> [--default-view ...] [--icon ...]
+  dench crm objects update <name> [--default-view ...] [--icon ...] [--display-name "Clients"] [--display-name-singular "Client"]
+      --display-name relabels the UI only; the canonical <name> stays the
+      command/API identifier (works on protected objects too).
   dench crm objects rename <from> <to>
   dench crm objects delete <name>
 
@@ -2743,10 +2848,32 @@ Docs:
   dench crm docs create <path> [--title ...] [--icon ...] [--link-entry <id>]
   dench crm docs link <path> --object <name> --entry <id>
 
+Templates (one-click CRM setups: objects + automations + sample rows):
+  dench crm templates list [--json]
+      Catalog with per-org installed flags. Installs are idempotent and
+      compose (e.g. sales + fundraising share the company Type enum).
+  dench crm templates install <templateId>
+  dench crm templates remove-sample-data <templateId>
+      Deletes only the template's sample rows (tagged "Sample"); schema,
+      views, and automations stay.
+
+Automations (deterministic rules, fire inside entry writes):
+  dench crm automations list [--json]
+      e.g. "prospect Status -> Qualified creates an opportunity". Writes
+      that trigger one return an automationEffects array describing what
+      was created/updated — expected behavior, not an error.
+  dench crm automations enable <automationId>
+  dench crm automations disable <automationId>
+
 Actions:
   dench crm actions list <entryId>
   dench crm actions run <actionId> --field-id <id> --entry-id <id>
 
+Object names: commands take the canonical object name (singular lowercase,
+e.g. people, company, prospect). Display labels shown in the UI (a template
+may relabel people as "Clients") and plural forms also resolve when
+unambiguous, but prefer canonical names from 'crm objects list'.
+
 Global flags:
   --json    Output raw JSON instead of pretty-printed text.
 `);

package/email.ts

@@ -194,6 +194,8 @@ Usage:
   dench email identity dns --identity <identityId|domain|email> [--json]
   dench email identity status --identity founder@example.com [--json]
   dench email identity status --identity-id <identityId> [--json]
+  dench email identity disable --identity <identityId|email|domain> [--json]
+  dench email identity restore --identity <identityId|email|domain> [--json]
   dench email send --from founder@example.com --to "Ada <ada@x.com>,bob@y.com" --subject "Hi" (--html-file body.html | --text "...") [--cc ...] [--bcc ...] [--from-name "Ada"] [--reply-to support@x.com] [--reply-message-id <messageId|rfc-id>] [--json]
   dench email message status --message <messageId> [--json]
   dench email message list [--limit 25] [--json]
@@ -465,12 +467,39 @@ async function runIdentity(ctx: EmailCliContext) {
               (identity) =>
                 `${identity.identityId}  ${identity.fromEmail}  type=${identity.type}` +
                 `${identity.domain ? ` domain=${identity.domain}` : ""}` +
-                `  delivery=${identity.deliveryVerificationStatus}  workspace=${identity.denchVerificationStatus}`,
+                `  delivery=${identity.deliveryVerificationStatus}  workspace=${identity.denchVerificationStatus}` +
+                `${identity.disabled ? "  DISABLED" : ""}`,
             )
             .join("\n");
     out(ctx, { ok: true, identities }, text);
     return;
   }
+  if (sub === "disable" || sub === "restore") {
+    const identity = requiredFlag(ctx.args, "--identity");
+    const payload = (await callMutation(
+      ctx,
+      sub === "disable"
+        ? "functions/emailCampaigns:disableIdentity"
+        : "functions/emailCampaigns:restoreIdentity",
+      { identity },
+    )) as JsonRecord;
+    const rows = (
+      Array.isArray(payload.disabled)
+        ? payload.disabled
+        : Array.isArray(payload.restored)
+          ? payload.restored
+          : []
+    ) as JsonRecord[];
+    const verb = sub === "disable" ? "Disabled" : "Restored";
+    const text =
+      rows.length === 0
+        ? `${verb} 0 identities.`
+        : `${verb} ${rows.length} sender(s):\n${rows
+            .map((row) => `  ${row.fromEmail} (${row.identityId})`)
+            .join("\n")}`;
+    out(ctx, payload, text);
+    return;
+  }
   if (sub === "dns") {
     const identity = requiredFlag(ctx.args, "--identity");
     if (!identity.includes("@") && !identity.includes(".")) {
@@ -509,12 +538,19 @@ async function runIdentity(ctx: EmailCliContext) {
       : [];
     const records = buildDnsRecords(domain, tokens);
     const verified = status.verifiedForSendingStatus === true;
-    const payload = {
+    const payload: JsonRecord = {
       ok: true,
       domain,
       domainVerified: verified,
       dnsRecords: records,
     };
+    if (
+      !verified &&
+      status.verificationInfo &&
+      typeof status.verificationInfo === "object"
+    ) {
+      payload.verificationInfo = status.verificationInfo;
+    }
     const text = verified
       ? `Domain ${domain} is verified — DNS records below are already in place.\n${formatDnsRecords(records)}`
       : tokens.length > 0
@@ -541,16 +577,27 @@ async function runIdentity(ctx: EmailCliContext) {
       `/v1/email/identities/${encodeURIComponent(identity)}/status`,
     );
     const status = payload as JsonRecord;
-    const shaped = {
+    const shaped: JsonRecord = {
       ok: status.ok === true,
       identity: status.identity,
       deliveryVerified: status.verifiedForSendingStatus === true,
       deliveryVerificationStatus: status.verificationStatus,
     };
+    // Pending domains: surface when the provider last polled DNS and
+    // why it failed, so callers know whether to fix records or wait.
+    if (
+      status.verifiedForSendingStatus !== true &&
+      status.verificationInfo &&
+      typeof status.verificationInfo === "object"
+    ) {
+      shaped.verificationInfo = status.verificationInfo;
+    }
     out(ctx, shaped, JSON.stringify(shaped, null, 2));
     return;
   }
-  throw new EmailCliError("Usage: dench email identity verify|list|dns|status");
+  throw new EmailCliError(
+    "Usage: dench email identity verify|list|dns|status|disable|restore",
+  );
 }
 
 async function runTemplate(ctx: EmailCliContext) {