@zernio/node 0.2.532 → 0.2.533

package/dist/index.d.mts

@@ -25416,6 +25416,10 @@ type ListCommentAutomationsResponse = ({
          * Seconds waited before the public reply is posted. Absent when it follows the DM immediately.
          */
         commentReplyDelaySeconds?: number;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         stats?: {
             triggered?: number;
@@ -25532,6 +25536,10 @@ type CreateCommentAutomationData = {
          * Seconds to wait before posting the public comment reply. Omit or send 0 to post it right after the DM (the default). The reply never goes out before the DM, so a value below dmDelaySeconds is raised to it. Ignored when trigger=story_reply, which has no public reply.
          */
         commentReplyDelaySeconds?: number;
+        /**
+         * Also fire these keywords on a plain inbound DM, so the automation answers people who message the keyword instead of commenting it. Requires at least one keyword (an empty keyword list means 'match anything', which would answer every inbound message) and is rejected on story_reply automations, which already trigger on DMs. Dedup is per door: a contact who already received the DM from their comment can still receive it from a DM.
+         */
+        alsoMatchInDms?: boolean;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
     };
@@ -25584,6 +25592,10 @@ type CreateCommentAutomationResponse = ({
         commentReplyDelaySeconds?: number;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         stats?: {
             totalTriggered?: number;
@@ -25652,6 +25664,10 @@ type GetCommentAutomationResponse = ({
         commentReplyDelaySeconds?: number;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         stats?: {
             totalTriggered?: number;
@@ -25667,6 +25683,10 @@ type GetCommentAutomationResponse = ({
         commenterId?: string;
         commenterName?: string;
         commentText?: string;
+        /**
+         * Which door triggered this send. Absent on rows written before this field existed (all of those are comment-triggered).
+         */
+        source?: 'comment' | 'story_reply' | 'dm';
         /**
          * DM outcome. 'pending' = the automation has a dmDelaySeconds and the response is queued but not sent yet. 'gated' = the follow-gate confirmation DM went out and we are waiting for the tap; it flips to 'sent' or 'skipped' when they tap.
          */
@@ -25748,6 +25768,10 @@ type UpdateCommentAutomationData = {
          * Tag applied to a contact when they click a tracked link (requires linkTracking). Empty string clears it.
          */
         clickTag?: string;
+        /**
+         * Also fire these keywords on a plain inbound DM. Enabling it requires the automation to end up with at least one keyword (this request's keywords if you send them, otherwise the stored ones) and is rejected on story_reply automations.
+         */
+        alsoMatchInDms?: boolean;
         /**
          * Seconds to wait after the trigger before sending the DM. Send 0 to clear the delay and reply immediately.
          */
@@ -25799,6 +25823,10 @@ type UpdateCommentAutomationResponse = ({
         commentReplyVariations?: Array<(string)>;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         updatedAt?: string;
     };
@@ -25836,6 +25864,10 @@ type ListCommentAutomationLogsResponse = ({
         commenterId?: string;
         commenterName?: string;
         commentText?: string;
+        /**
+         * Which door triggered this send. Absent on rows written before this field existed (all of those are comment-triggered).
+         */
+        source?: 'comment' | 'story_reply' | 'dm';
         /**
          * DM outcome. 'pending' = the automation has a dmDelaySeconds and the response is queued but not sent yet. 'gated' = the follow-gate confirmation DM went out and we are waiting for the tap; it flips to 'sent' or 'skipped' when they tap.
          */

package/dist/index.d.ts

@@ -25416,6 +25416,10 @@ type ListCommentAutomationsResponse = ({
          * Seconds waited before the public reply is posted. Absent when it follows the DM immediately.
          */
         commentReplyDelaySeconds?: number;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         stats?: {
             triggered?: number;
@@ -25532,6 +25536,10 @@ type CreateCommentAutomationData = {
          * Seconds to wait before posting the public comment reply. Omit or send 0 to post it right after the DM (the default). The reply never goes out before the DM, so a value below dmDelaySeconds is raised to it. Ignored when trigger=story_reply, which has no public reply.
          */
         commentReplyDelaySeconds?: number;
+        /**
+         * Also fire these keywords on a plain inbound DM, so the automation answers people who message the keyword instead of commenting it. Requires at least one keyword (an empty keyword list means 'match anything', which would answer every inbound message) and is rejected on story_reply automations, which already trigger on DMs. Dedup is per door: a contact who already received the DM from their comment can still receive it from a DM.
+         */
+        alsoMatchInDms?: boolean;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
     };
@@ -25584,6 +25592,10 @@ type CreateCommentAutomationResponse = ({
         commentReplyDelaySeconds?: number;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         stats?: {
             totalTriggered?: number;
@@ -25652,6 +25664,10 @@ type GetCommentAutomationResponse = ({
         commentReplyDelaySeconds?: number;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         stats?: {
             totalTriggered?: number;
@@ -25667,6 +25683,10 @@ type GetCommentAutomationResponse = ({
         commenterId?: string;
         commenterName?: string;
         commentText?: string;
+        /**
+         * Which door triggered this send. Absent on rows written before this field existed (all of those are comment-triggered).
+         */
+        source?: 'comment' | 'story_reply' | 'dm';
         /**
          * DM outcome. 'pending' = the automation has a dmDelaySeconds and the response is queued but not sent yet. 'gated' = the follow-gate confirmation DM went out and we are waiting for the tap; it flips to 'sent' or 'skipped' when they tap.
          */
@@ -25748,6 +25768,10 @@ type UpdateCommentAutomationData = {
          * Tag applied to a contact when they click a tracked link (requires linkTracking). Empty string clears it.
          */
         clickTag?: string;
+        /**
+         * Also fire these keywords on a plain inbound DM. Enabling it requires the automation to end up with at least one keyword (this request's keywords if you send them, otherwise the stored ones) and is rejected on story_reply automations.
+         */
+        alsoMatchInDms?: boolean;
         /**
          * Seconds to wait after the trigger before sending the DM. Send 0 to clear the delay and reply immediately.
          */
@@ -25799,6 +25823,10 @@ type UpdateCommentAutomationResponse = ({
         commentReplyVariations?: Array<(string)>;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         updatedAt?: string;
     };
@@ -25836,6 +25864,10 @@ type ListCommentAutomationLogsResponse = ({
         commenterId?: string;
         commenterName?: string;
         commentText?: string;
+        /**
+         * Which door triggered this send. Absent on rows written before this field existed (all of those are comment-triggered).
+         */
+        source?: 'comment' | 'story_reply' | 'dm';
         /**
          * DM outcome. 'pending' = the automation has a dmDelaySeconds and the response is queued but not sent yet. 'gated' = the follow-gate confirmation DM went out and we are waiting for the tap; it flips to 'sent' or 'skipped' when they tap.
          */

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.532",
+  version: "0.2.533",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/dist/index.mjs

@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.532",
+  version: "0.2.533",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zernio/node",
-  "version": "0.2.532",
+  "version": "0.2.533",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/sdk.gen.ts

@@ -6751,6 +6751,12 @@ export const listCommentAutomations = <ThrowOnError extends boolean = false>(opt
  * confirmation DM (`followGate`) and then delivers the real DM automatically. People we
  * already know follow you skip the tap entirely.
  *
+ * Set `alsoMatchInDms: true` on a `comment` automation to also answer people who send
+ * a keyword as a direct message instead of commenting it. One automation then covers
+ * both doors, and each door is deduplicated separately (someone who already got the DM
+ * from their comment still gets it if they later DM the keyword). Requires at least one
+ * keyword.
+ *
  * Links in the DM's buttons can be click-tracked (`linkTracking`, on by default) and
  * clickers optionally tagged (`clickTag`) for segmentation. Stats returned include
  * delivered, read, and link clicks.

package/src/generated/types.gen.ts

@@ -25768,6 +25768,10 @@ export type ListCommentAutomationsResponse = ({
          * Seconds waited before the public reply is posted. Absent when it follows the DM immediately.
          */
         commentReplyDelaySeconds?: number;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         stats?: {
             triggered?: number;
@@ -25886,6 +25890,10 @@ export type CreateCommentAutomationData = {
          * Seconds to wait before posting the public comment reply. Omit or send 0 to post it right after the DM (the default). The reply never goes out before the DM, so a value below dmDelaySeconds is raised to it. Ignored when trigger=story_reply, which has no public reply.
          */
         commentReplyDelaySeconds?: number;
+        /**
+         * Also fire these keywords on a plain inbound DM, so the automation answers people who message the keyword instead of commenting it. Requires at least one keyword (an empty keyword list means 'match anything', which would answer every inbound message) and is rejected on story_reply automations, which already trigger on DMs. Dedup is per door: a contact who already received the DM from their comment can still receive it from a DM.
+         */
+        alsoMatchInDms?: boolean;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
     };
@@ -25939,6 +25947,10 @@ export type CreateCommentAutomationResponse = ({
         commentReplyDelaySeconds?: number;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         stats?: {
             totalTriggered?: number;
@@ -26010,6 +26022,10 @@ export type GetCommentAutomationResponse = ({
         commentReplyDelaySeconds?: number;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         stats?: {
             totalTriggered?: number;
@@ -26025,6 +26041,10 @@ export type GetCommentAutomationResponse = ({
         commenterId?: string;
         commenterName?: string;
         commentText?: string;
+        /**
+         * Which door triggered this send. Absent on rows written before this field existed (all of those are comment-triggered).
+         */
+        source?: 'comment' | 'story_reply' | 'dm';
         /**
          * DM outcome. 'pending' = the automation has a dmDelaySeconds and the response is queued but not sent yet. 'gated' = the follow-gate confirmation DM went out and we are waiting for the tap; it flips to 'sent' or 'skipped' when they tap.
          */
@@ -26108,6 +26128,10 @@ export type UpdateCommentAutomationData = {
          * Tag applied to a contact when they click a tracked link (requires linkTracking). Empty string clears it.
          */
         clickTag?: string;
+        /**
+         * Also fire these keywords on a plain inbound DM. Enabling it requires the automation to end up with at least one keyword (this request's keywords if you send them, otherwise the stored ones) and is rejected on story_reply automations.
+         */
+        alsoMatchInDms?: boolean;
         /**
          * Seconds to wait after the trigger before sending the DM. Send 0 to clear the delay and reply immediately.
          */
@@ -26160,6 +26184,10 @@ export type UpdateCommentAutomationResponse = ({
         commentReplyVariations?: Array<(string)>;
         audience?: CommentAutomationAudience;
         followGate?: CommentAutomationFollowGate;
+        /**
+         * Whether these keywords also fire on a plain inbound DM.
+         */
+        alsoMatchInDms?: boolean;
         isActive?: boolean;
         updatedAt?: string;
     };
@@ -26203,6 +26231,10 @@ export type ListCommentAutomationLogsResponse = ({
         commenterId?: string;
         commenterName?: string;
         commentText?: string;
+        /**
+         * Which door triggered this send. Absent on rows written before this field existed (all of those are comment-triggered).
+         */
+        source?: 'comment' | 'story_reply' | 'dm';
         /**
          * DM outcome. 'pending' = the automation has a dmDelaySeconds and the response is queued but not sent yet. 'gated' = the follow-gate confirmation DM went out and we are waiting for the tap; it flips to 'sent' or 'skipped' when they tap.
          */