@velaro/mcp-server 2.0.5 → 2.0.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@velaro/mcp-server",
-  "version": "2.0.5",
+  "version": "2.0.6",
   "description": "Velaro MCP server — connect Claude and other AI agents directly to your Velaro account: KB, workflows, bots, conversations, contacts, routing, and more.",
   "type": "module",
   "bin": {
@@ -45,6 +45,7 @@
     "tool-annotations.js",
     "fetch-retry.js",
     "messaging-base.js",
+    "survey-email.js",
     "parity/loader.js",
     "parity/*.customer.js",
     "workflow-schedule.js",

package/server.js

@@ -53,6 +53,7 @@ import { withAnnotations } from './tool-annotations.js';
 import { loadParity, runParity } from './parity/loader.js';
 import { resolveMessagingApi } from './messaging-base.js';
 import { buildResolvePath, buildTimelinePath, buildOverrideBody, buildValidateBody, buildBannerPath, buildOverrideListPath, tolerant, VALIDATE_PATH, OVERRIDE_PATH } from './workflow-schedule.js';
+import { applyEmailSubmissionsTo } from './survey-email.js';
 
 // Production admin API by default; set VELARO_ADMIN_API to target staging.
 const API_BASE      = process.env.VELARO_ADMIN_API     || 'https://api-admin-us-east.velaro.com';
@@ -1033,10 +1034,12 @@ For multiSelect dynamic options: the variable named in dynamicOptionsVariable mu
   },
   {
     name: 'survey_upsert',
-    description: 'Create (omit id or set id=0) or update (set id) a survey. body must be the full SurveyViewModel JSON shape (id, name, questions[], each question with type/text/options/required/variable/etc.). Use survey_get on an existing survey to fetch this full shape as a template rather than guessing the question schema from scratch. Each question also accepts isThemeAnchor (boolean, default false: this answer sets the Chat Intelligence topic) and themeMapping (string: JSON object mapping answer text to a site topic, e.g. "{\\"Pay my bill\\":\\"Billing Questions\\"}"). Both only take effect when the site has the multi-topic setting on. body.compactMode is tri-state: null/omitted = follow default (regular size), true = compact, false = regular.',
+    description: 'Create (omit id or set id=0) or update (set id) a survey. body must be the full SurveyViewModel JSON shape (id, name, questions[], each question with type/text/options/required/variable/etc.). Use survey_get on an existing survey to fetch this full shape as a template rather than guessing the question schema from scratch. Each question also accepts isThemeAnchor (boolean, default false: this answer sets the Chat Intelligence topic) and themeMapping (string: JSON object mapping answer text to a site topic, e.g. "{\\"Pay my bill\\":\\"Billing Questions\\"}"). Both only take effect when the site has the multi-topic setting on. body.compactMode is tri-state: null/omitted = follow default (regular size), true = compact, false = regular. Optional top-level emailSubmissionsTo sets who receives offline / closed-launcher submissions (omit = keep stored list, "" = clear).',
     inputSchema: {
       type: 'object',
-      properties: { body: {
+      properties: {
+        emailSubmissionsTo: { type: 'string', description: 'Optional. Comma/semicolon list (max 10) of addresses that receive offline / closed-launcher survey submissions. Overrides body.emailSubmissionsTo. Omit to keep the stored list; pass "" to clear it. Invalid addresses are rejected by the server with a 400.' },
+        body: {
         type: 'object',
         description: 'Full SurveyViewModel JSON',
         properties: {
@@ -5397,7 +5400,7 @@ async function handleTool(name, args) {
 
     case 'survey_upsert': {
       if (!args.body || typeof args.body !== 'object') throw new Error('body is required (full SurveyViewModel JSON)');
-      const r = await messagingPost('/Surveys', args.body);
+      const r = await messagingPost('/Surveys', applyEmailSubmissionsTo(args.body, args.emailSubmissionsTo));
       return JSON.stringify(r, null, 2);
     }
 

package/survey-email.js

@@ -0,0 +1,9 @@
+// Survey.EmailSubmissionsTo helper (velaro-messaging PR #3209/#3214).
+// Semantics enforced by the server on POST Surveys: field omitted/null keeps the stored
+// recipients, "" clears them, a non-empty comma/semicolon list replaces them (max 10, validated
+// server-side, 400 with { error } on a bad address). The server is the only validator.
+// Mirrored in cli/lib/survey-email.js; keep in sync (both covered by their tests).
+export function applyEmailSubmissionsTo(body, value) {
+  if (value === undefined || value === null) return body;
+  return { ...body, emailSubmissionsTo: String(value).trim() };
+}