chatwoot-router 0.5.1 → 0.6.0

package/CHANGELOG.md

@@ -7,6 +7,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.6.0] - 2026-10-05
+
+### Added
+
+- `routing.kinds.<id>.<name>.label` (default `true`): `false` handles the kind without giving the ticket its label,
+  for a kind that is not a kind of ticket, such as a thank-you that is only resolved.
+
+## [0.5.2] - 2026-10-05
+
+### Fixed
+
+- Clear a request's timeout once its response has been read. The pending `AbortSignal.timeout` timer kept a
+  Durable Object invocation open until it fired, so most alarms were billed and reported at about 60 seconds.
+
 ## [0.5.1] - 2026-10-05
 
 ### Fixed
@@ -120,7 +134,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   `routing_kind`.
 - The `chatwoot-router-store-config` command and `chatwoot-router/stored-config`, for a configuration in KV.
 
-[Unreleased]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.5.1...HEAD
+[Unreleased]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.6.0...HEAD
+[0.6.0]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.5.2...chatwoot-router@0.6.0
+[0.5.2]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.5.1...chatwoot-router@0.5.2
 [0.5.1]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.5.0...chatwoot-router@0.5.1
 [0.5.0]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.4.0...chatwoot-router@0.5.0
 [0.4.0]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.3.0...chatwoot-router@0.4.0

package/README.md

@@ -126,6 +126,7 @@ no unpublished shared package needs installing.
 | `routing.kinds.<id>.<name>.covers` | 1–1000 characters | required | What the kind is: Jev's criterion for recognizing it. |
 | `routing.kinds.<id>.<name>.cannedResponse` | short code | unset | The account's Chatwoot canned response sent to the customer once, by the account's agent bot (`CHATWOOT_AGENT_BOT_TOKENS`); handoff if it is missing. |
 | `routing.kinds.<id>.<name>.status` | `resolved` or `snoozed` | unset | Set instead of routing the ticket (`snoozed`: until the customer's next message), after the reply of a `cannedResponse`; a new customer message reopens it. |
+| `routing.kinds.<id>.<name>.label` | boolean | `true` | Whether the ticket gets the kind's label; `false` for a kind that is not a kind of ticket, such as a thank-you that is only resolved. |
 
 ### Secrets
 
@@ -148,37 +149,6 @@ the Router DO during rollback. If its state is lost or restored to an older reco
 and isolate conversations with uncertain attempts/turns for owner review; a currently empty history does not
 prove another send is safe. Existing pending conversations are reconciled; non-pending conversations stay with people. The user token must see all relevant inboxes.
 
-For the first move from the relay's built-in routing (production baseline 0.27.0):
-
-1. Record the live relay deployment/version id and CONFIG_KEY before rollout; retain its Hub and old secrets.
-   Disconnect all brand bots and prevent competing old deployments. Verify bot identities, owner membership,
-   labels, canned responses and inbox visibility. Historical confirmed brand-bot replies need no ledger migration.
-2. Deploy and verify relay 0.30 first. Remove `routing`, `router.accounts` and `router.waitSeconds`; keep every kind
-   in `router.keepLabels`. Verify the actual version and that built-in routing/in-flight old work stopped.
-3. Bootstrap this Worker by hand with all four secrets in a protected secrets file while bots remain disconnected.
-   Verify KV/domain, upstream permissions and test tickets; health/2xx alone do not prove routing success.
-   If using an infra PR whose push deploys both Workers independently, merge only after both hand deployments pass.
-4. Connect bots one account at a time and verify real routing, handoff, failed/unknown reply handling, historical
-   reply deduplication and Discord/triage behavior, including at least a complete sweep.
-5. To roll back, disconnect bots first and **keep this router running until no pending ticket remains assigned to
-   a disconnected brand bot and no non-pending ticket remains assigned to that bot**. Complete pending/open
-   account passes and let failed ending releases finish through their durable retries: pending uses native bot
-   handoff, open leftovers use explicit unassignment, and kind endings release resolved/snoozed tickets in the
-   same turn. Confirm cleared bot ownership across statuses; preserve human/other-bot owners. Then stop
-   webhook entry, cron and queued/in-flight router work; stopping cron alone does not cancel DO alarms. Preserve DO
-   namespace and storage, including reply and turn guards. Restore the recorded live 0.27 version **and its
-   CONFIG_KEY**, without overlapping old/new routing. Relay 0.27 uses its original Hub's
-   `kind-reply:<account>:<conversation>` records; the Router uses separate `reply:<account>:<conversation>`
-   records. Restoring code/config does not copy Router attempts into the Hub or reset either ledger. Only replies
-   already recorded by 0.27 retain its own reply-once protection; Router-only replies/unknown attempts can be
-   attempted again by 0.27. Keep both DOs and review/isolate those tickets before restoring old routing. Rollback
-   does not guarantee reply-once across this switch or undo sent messages or other mutations.
-
-Current router upgrades need no custom coordination attributes, compatibility effects or one-time lifecycle
-cleanup. Older unreadable job payloads are dropped; live snapshots and the account sweep reconstruct queued work, not durable reply/turn guards.
-If handoff credentials fail, repair them or let a real owner take the tickets; do not bulk-open with the integration
-user token, which can assign every ticket to that user. Keep old attributes through the owner's rollback window.
-
 Redaction is best effort, not anonymization: other personal information can still reach TypeSafe. Logs contain
 ids and outcomes, never message bodies or credentials. See [SECURITY.md](https://github.com/Phala-Network/chatwoot-workers/blob/main/SECURITY.md),
 [CONTRIBUTING.md](https://github.com/Phala-Network/chatwoot-workers/blob/main/CONTRIBUTING.md) and [CHANGELOG.md](https://github.com/Phala-Network/chatwoot-workers/blob/main/packages/chatwoot-router/CHANGELOG.md). Licensed under [MIT](https://github.com/Phala-Network/chatwoot-workers/blob/main/packages/chatwoot-router/LICENSE).

package/lib/packages/chatwoot-router/scripts/store-config.js

@@ -141,7 +141,12 @@ var configSchema = z2.strictObject({
            * or `snoozed` until the customer's next message. A new message from the customer
            * reopens either.
            */
-          status: z2.enum(["resolved", "snoozed"]).optional()
+          status: z2.enum(["resolved", "snoozed"]).optional(),
+          /**
+           * Whether the ticket gets the kind's label (the default). False for a kind that is not a kind of
+           * ticket, such as a thank-you that is only resolved.
+           */
+          label: z2.boolean().default(true)
         })
       )
     ).optional()

package/lib/packages/chatwoot-router/scripts/stored-config.js

@@ -93,7 +93,12 @@ var configSchema = z2.strictObject({
            * or `snoozed` until the customer's next message. A new message from the customer
            * reopens either.
            */
-          status: z2.enum(["resolved", "snoozed"]).optional()
+          status: z2.enum(["resolved", "snoozed"]).optional(),
+          /**
+           * Whether the ticket gets the kind's label (the default). False for a kind that is not a kind of
+           * ticket, such as a thank-you that is only resolved.
+           */
+          label: z2.boolean().default(true)
         })
       )
     ).optional()

package/lib/packages/chatwoot-router/src/config.d.ts

@@ -21,6 +21,7 @@ export declare const configSchema: z.ZodObject<{
                 resolved: "resolved";
                 snoozed: "snoozed";
             }>>;
+            label: z.ZodDefault<z.ZodBoolean>;
         }, z.core.$strict>>>>;
     }, z.core.$strict>;
 }, z.core.$strict>;

package/lib/packages/chatwoot-router/src/index.js

@@ -95,10 +95,30 @@ var Budget = class {
     if (this.used >= this.limit) throw new BudgetExhaustedError();
     this.used += 1;
   }
-  fetch = (request) => {
-    if (this.used >= this.limit) return Promise.reject(new BudgetExhaustedError());
+  /**
+   * The timeout is cleared once the response body has been read (or there is none): a pending
+   * timer, such as `AbortSignal.timeout`'s, keeps the invocation open until it fires.
+   */
+  fetch = async (request) => {
+    if (this.used >= this.limit) throw new BudgetExhaustedError();
     this.used += 1;
-    return this.fetchImpl(new Request(request, { signal: AbortSignal.timeout(this.timeoutMs) }));
+    const controller = new AbortController();
+    const timer = setTimeout(
+      () => controller.abort(new DOMException("The request timed out", "TimeoutError")),
+      this.timeoutMs
+    );
+    try {
+      const response = await this.fetchImpl(new Request(request, { signal: controller.signal }));
+      if (!response.body) {
+        clearTimeout(timer);
+        return response;
+      }
+      const body = response.body.pipeThrough(new TransformStream({ flush: () => clearTimeout(timer) }));
+      return new Response(body, response);
+    } catch (error) {
+      clearTimeout(timer);
+      throw error;
+    }
   };
 };
 
@@ -343,6 +363,16 @@ function chatwootClient(baseUrl, token, fetch2) {
       );
     },
     /** The account's label names (Chatwoot saves them in lower case). */
+    /** The contact's latest 25 conversations, newest first, that this user may see. */
+    async contactConversations(accountId2, contactId) {
+      const list = await data(
+        "list contact conversations",
+        client.GET("/api/v1/accounts/{account_id}/contacts/{id}/conversations", {
+          params: { path: { account_id: accountId2, id: contactId } }
+        })
+      );
+      return list.payload ?? [];
+    },
     async listLabels(accountId2) {
       const list = await data(
         "list labels",
@@ -430,6 +460,7 @@ function toRelayConversation(conversationId, conversation) {
     priority: conversation.priority ?? null,
     labels: conversation.labels ?? [],
     contact: {
+      id: meta?.sender?.id ?? null,
       name: meta?.sender?.name ?? null,
       email: meta?.sender?.email ?? null,
       phone: meta?.sender?.phone_number ?? null,
@@ -855,7 +886,7 @@ async function routeConversation(ctx, accountId2, conversationId) {
   const labels = [
     .../* @__PURE__ */ new Set([
       ...current.conversation.labels,
-      ...[topic, kind ? decision.kind : null].filter((label) => label !== null)
+      ...[topic, kind?.label ? decision.kind : null].filter((label) => label !== null)
     ])
   ];
   if (labels.length !== current.conversation.labels.length) await bot.setLabels(accountId2, conversationId, labels);
@@ -1063,7 +1094,12 @@ var configSchema = z5.strictObject({
            * or `snoozed` until the customer's next message. A new message from the customer
            * reopens either.
            */
-          status: z5.enum(["resolved", "snoozed"]).optional()
+          status: z5.enum(["resolved", "snoozed"]).optional(),
+          /**
+           * Whether the ticket gets the kind's label (the default). False for a kind that is not a kind of
+           * ticket, such as a thank-you that is only resolved.
+           */
+          label: z5.boolean().default(true)
         })
       )
     ).optional()

package/lib/shared/budget.d.ts

@@ -11,5 +11,9 @@ export declare class Budget {
     get remaining(): number;
     /** Counts a request that is not a fetch, such as a call to another Durable Object. */
     consume(): void;
+    /**
+     * The timeout is cleared once the response body has been read (or there is none): a pending
+     * timer, such as `AbortSignal.timeout`'s, keeps the invocation open until it fires.
+     */
     readonly fetch: Fetch;
 }

package/lib/shared/chatwoot/api.d.ts

@@ -185,6 +185,8 @@ export declare function chatwootClient(baseUrl: string, token: string, fetch: Fe
      */
     unassign(accountId: number, conversationId: number): Promise<void>;
     /** The account's label names (Chatwoot saves them in lower case). */
+    /** The contact's latest 25 conversations, newest first, that this user may see. */
+    contactConversations(accountId: number, contactId: number): Promise<ChatwootConversation[]>;
     listLabels(accountId: number): Promise<string[]>;
     conversationLabels(accountId: number, conversationId: number): Promise<string[]>;
     /** Replaces the conversation's labels (the spec's "Add Labels" overwrites the list). */
@@ -232,8 +234,6 @@ export declare function personAssignee(conversation: ChatwootConversation): {
         custom_role?: Record<string, unknown> | null;
     }[];
 } | undefined;
-/** An actual public answer; Chatwoot templates include greetings and out-of-office notices. */
-export declare function isAnsweringReply(message: ChatwootMessage): boolean;
 export declare function toRelayConversation(conversationId: number, conversation: ChatwootConversation): RelayConversation;
 export declare function toRelayMessage(message: ChatwootMessage, context: {
     account: {

package/lib/shared/types.d.ts

@@ -43,6 +43,8 @@ export interface RelayConversation {
     priority?: string | null;
     labels: string[];
     contact: {
+        /** The contact's Chatwoot id. */
+        id?: number | null;
         name?: string | null;
         email?: string | null;
         phone?: string | null;
@@ -80,6 +82,8 @@ export interface RelayMessage {
     /** The Discord avatar of the linked agent who sent the message, if any. */
     discordAvatarUrl?: string;
     sender?: {
+        /** The Chatwoot id of the contact, user, or agent bot (see `type`). */
+        id?: number | null | undefined;
         name?: string | null | undefined;
         email?: string | null | undefined;
         type?: string | null | undefined;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chatwoot-router",
-  "version": "0.5.1",
+  "version": "0.6.0",
   "description": "Route Chatwoot conversations with TypeSafe Jev on Cloudflare Workers.",
   "keywords": [
     "chatwoot",