@wokuapp/ai-toolkit 0.5.0 → 0.6.0

package/.claude-plugin/marketplace.json

@@ -11,7 +11,7 @@
       "name": "woku",
       "source": "./",
       "description": "Design a listening program for your customer journey, run the VoC instruments (NPS, CSAT, CES, wokus), and turn every signal into a support ticket or an action plan, through woku's MCP server.",
-      "version": "0.5.0",
+      "version": "0.6.0",
       "author": { "name": "woku" },
       "license": "MIT",
       "homepage": "https://woku.app",

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "woku",
   "description": "Voice-of-customer for Claude Code. Design a listening program for your customer journey, run the fast VoC instruments (NPS, CSAT, CES, wokus), and turn every signal into a support ticket or an action plan, through woku's MCP server. Bundles the woku method so the agent acts as a CX consultant.",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "author": {
     "name": "woku"
   },

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "woku",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "Voice-of-customer for OpenAI Codex. Design a listening program, run the VoC instruments (NPS, CSAT, CES, wokus), and turn every signal into a support ticket or an action plan, through woku's MCP server.",
   "author": {
     "name": "woku"

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 0.6.0
+
+Support and plans by folder. The woku skill documents `scopeKind: "folder"` with `folderId` on `create_ticket_destination`, `update_ticket_destination`, `create_action_plan_group` and `update_action_plan_group` (the destination or group listens to every tool inside the folder, at any depth, never mixed with tracker rows), the `folderId` filter on `list_ticket_destinations`, `list_action_plan_groups` and `list_tickets`, and the `FOLDER_HAS_DEPENDENTS` confirmation (`confirmDependents: true`) of `delete_folder`. The SDK skills add the same options (`scopeKind`/`folderId`, `folderId` filters, `confirmDependents` / `confirm_dependents`). Requires the server and SDK releases that ship them.
+
 ## 0.5.0
 
 The woku skill documents folder participants (`get_folder_participants`, `set_folder_participants`, `remove_folder_participant`, `resend_to_missing_participants`), scheduled report emails (`list_scheduled_reports`, `schedule_report`, `update_scheduled_report`, `delete_scheduled_report`, `send_scheduled_report_now`), the period on the folder CSV and the `lastResponse` sort of `search_voc_tools`. The SDK skills add `folderParticipants` / `folder_participants`, `reportSubscriptions` / `report_subscriptions`, the CSV period and the sort. Requires the server and SDK releases that ship them.

package/README.md

@@ -100,6 +100,15 @@ Every connection is bound to one company, chosen when you approve access. Read t
 
 MIT. See [LICENSE](./LICENSE).
 
+### Support and plans by folder update (0.6.0)
+
+Support destinations and action plan groups can listen to one tool folder instead
+of tracker rows (`scopeKind: "folder"` with `folderId`; every tool inside it, at
+any depth). Destination, group and ticket lists filter by `folderId`, and
+`delete_folder` asks for `confirmDependents: true` before deleting the destinations
+and groups configured on the folder (with their tickets and plans). The SDK skills
+cover the same options. Verify the server and SDK releases before using them.
+
 ### Participants, scheduled reports and survey settings update (0.5.0)
 
 The woku skill covers folder participant lists (`get_folder_participants`,

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "woku-ai-toolkit",
   "name": "woku AI Toolkit",
   "description": "Voice-of-customer for your agent. Design a listening program, run the VoC instruments (NPS, CSAT, CES, wokus), and turn every signal into a support ticket or an action plan, through woku's MCP server.",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "skills": [
     "./skills"
   ],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wokuapp/ai-toolkit",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "woku AI Toolkit: connect your agent to woku's voice-of-customer platform. Design VoC programs and turn customer feedback into support tickets and action plans, through woku's MCP server.",
   "author": "woku",
   "license": "MIT",

package/skills/woku/SKILL.md

@@ -73,7 +73,8 @@ One folder tree holds wokus and NPS, CSAT and CES tools together. Call `woku_gui
 - Journeys can live in folders (`Viajes > journey > moment`): `get_journey_folders_status` shows whether the company organizes them and what is pending, and `organize_journey_folders` switches it on and runs a background pass that only moves tools without a folder (propose it and wait for approval; it returns a conflict while a pass is running). `get_journey` and `list_journeys` show `folderId` and `momentFolders`, and folders created by woku carry an `origin` (`journeys-root`, `journey`, `journey-moment`, `integration`; integration folders also carry `integrationProvider`, for example `shopify`); read `origin`, `integrationProvider` and the stats of a folder with `search_voc_tools`, not with `get_folder` or `list_folders`, which only count wokus.
 - A folder can keep a participant list (a program's enrolled): `get_folder_participants` returns it and, per tool of the subtree, the indexes of who answered (`responded`), who did not (`missing`) and who answered more than once (`repeated`), plus `outsideList` and `anonymousAllowed` (anonymous responses cannot be matched). `set_folder_participants` replaces the list (`mode: "replace"`) or adds to it (`mode: "add"`) from text, one person per line with a name, an email and/or a phone; `remove_folder_participant` removes one person or the whole list; `resend_to_missing_participants` sends a tool again to the missing by email or WhatsApp. Removing and resending need `confirm: true`; propose them and wait for approval.
 - `schedule_report` emails the PDF report of a folder or a tool on a schedule (`monthly`, `biweekly`, `weekly` at 12:00 UTC with the previous complete period, or `once` with `periodFrom`/`periodTo`) to up to 10 recipients; `list_scheduled_reports`, `update_scheduled_report` (edit, pause, resume), `delete_scheduled_report` and `send_scheduled_report_now` manage them. Scheduling, sending now and deleting need `confirm: true`: they email real people.
-- `delete_folder` needs `confirm: true`; nothing inside is deleted, the content moves up to the parent. Moving or deleting folders is a user decision: propose the new structure and wait for approval.
+- `delete_folder` needs `confirm: true`; the content moves up to the parent. Support destinations and action plan groups configured ON that folder are deleted with it, with their tickets and plans: the call then fails with `FOLDER_HAS_DEPENDENTS` and the list; show it and repeat with `confirmDependents: true` only if the user agrees. Moving or deleting folders is a user decision: propose the new structure and wait for approval.
+- Support and plans by folder: `create_ticket_destination` and `create_action_plan_group` (and their `update_*`) take `scopeKind: "folder"` with a `folderId` instead of tracker rows: the destination or group then listens to every tool inside that folder, at any depth, resolved when each review arrives (moving a tool out stops it counting). Never both. A ticket reaches every enabled destination that matches it (trackers, a folder and its subfolders), as one ticket with `destinationIds` (`destinationId` is the highest-priority one); all its email destinations share one email to each address once, listing who got it. `list_ticket_destinations`, `list_action_plan_groups` and `list_tickets` accept `folderId`. When the company already organizes its tools in folders by store, team or moment, propose a folder scope before designing trackers.
 
 ## Periods and text search
 

package/skills/woku-sdk-javascript/SKILL.md

@@ -114,7 +114,17 @@ const metrics = await woku.folders.metrics(folder.id, { days: 30 }); // per tool
 await woku.tools.move({ items: [{ type: 'csat', id: toolId }], folderId: null }); // null = root
 const csv: string = await woku.folders.csv(folder.id);
 const pdf: Uint8Array = await woku.folders.pdf(folder.id, { lang: 'en' }); // folder report as PDF bytes
-await woku.folders.delete(folder.id); // content moves up to the parent, nothing is deleted
+await woku.folders.delete(folder.id); // content moves up; 409 FOLDER_HAS_DEPENDENTS if destinations or groups are configured on it
+await woku.folders.delete(folder.id, { confirmDependents: true }); // also deletes those destinations and groups (tickets and plans)
+```
+
+Support and plans by folder: a destination or plan group listens to tracker rows or to one folder (every tool inside it, at any depth), never both.
+
+```ts
+await woku.ticketDestinations.create({ name: 'Store support', kind: 'email', config: { emails: ['support@acme.com'] }, scopeKind: 'folder', folderId: folder.id });
+await woku.actionPlanGroups.create({ name: 'Stores', scopeKind: 'folder', folderId: folder.id, members: [{ userId, role: 'admin' }] });
+const listening = await woku.ticketDestinations.list({ folderId: folder.id }); // on the folder or an ancestor
+for await (const ticket of await woku.tickets.list({ folderId: folder.id })) console.log(ticket.origin?.folder?.path);
 ```
 
 Journeys in folders: `await woku.journeyFolders.status()` and `await woku.journeyFolders.organize()` (background pass, 409 while running); `journeys.get` returns `folderId` and `momentFolders`, and folders expose `origin`.

package/skills/woku-sdk-python/SKILL.md

@@ -135,7 +135,18 @@ metrics = woku.folders.metrics(folder["id"], {"days": 30})  # per tool, period v
 woku.tools.move({"items": [{"type": "csat", "id": tool_id}], "folderId": None})  # None = root
 csv_text = woku.folders.csv(folder["id"])
 pdf_bytes = woku.folders.pdf(folder["id"], {"lang": "en"})  # folder report as PDF bytes
-woku.folders.delete(folder["id"])  # content moves up to the parent, nothing is deleted
+woku.folders.delete(folder["id"])  # content moves up; 409 FOLDER_HAS_DEPENDENTS if destinations or groups are configured on it
+woku.folders.delete(folder["id"], confirm_dependents=True)  # also deletes those destinations and groups (tickets and plans)
+```
+
+Support and plans by folder: a destination or plan group listens to tracker rows or to one folder (every tool inside it, at any depth), never both.
+
+```python
+woku.ticket_destinations.create({"name": "Store support", "kind": "email", "config": {"emails": ["support@acme.com"]}, "scopeKind": "folder", "folderId": folder["id"]})
+woku.action_plan_groups.create({"name": "Stores", "scopeKind": "folder", "folderId": folder["id"], "members": [{"userId": user_id, "role": "admin"}]})
+listening = woku.ticket_destinations.list(params={"folderId": folder["id"]})  # on the folder or an ancestor
+for ticket in woku.tickets.list({"folderId": folder["id"]}):
+    print(ticket.get("origin", {}).get("folder", {}).get("path"))
 ```
 
 Journeys in folders: `woku.journey_folders.status()` and `woku.journey_folders.organize()` (background pass, `ConflictError` while running); `journeys.get` returns `folderId` and `momentFolders`, and folders expose `origin`.