@zernio/node 0.2.512 → 0.2.514

package/dist/index.d.mts

@@ -5468,6 +5468,10 @@ type SocialAccount = {
      * - wabaId: WhatsApp Business Account ID
      * - phoneNumberId: Meta phone number ID
      *
+     * For LinkedIn accounts, profileData carries the profile details refreshed on each daily snapshot:
+     * - profileData.bio: The member's headline for personal accounts, or the organization description for organization accounts. null when the member has not set one.
+     * - profileData.extraData.vanityName: The member's profile slug, i.e. the /in/{vanityName} segment of profileUrl. Personal accounts only; an organization's own slug is in metadata.organizationInfo.vanityName.
+     *
      */
     metadata?: {
         [key: string]: unknown;
@@ -24844,7 +24848,18 @@ type ListCommentAutomationsResponse = ({
         platformPostId?: string;
         postTitle?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.
@@ -24931,7 +24946,18 @@ type CreateCommentAutomationData = {
          * Trigger keywords (empty = any comment triggers)
          */
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         /**
          * DM text to send to commenter. Max 640 chars when buttons are set, otherwise ~1000.
          */
@@ -24971,7 +24997,18 @@ type CreateCommentAutomationResponse = ({
         trigger?: 'comment' | 'story_reply';
         platformPostId?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.
@@ -25017,7 +25054,18 @@ type GetCommentAutomationResponse = ({
         postId?: string;
         postTitle?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.
@@ -25075,7 +25123,18 @@ type UpdateCommentAutomationData = {
     body?: {
         name?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (1-3). Pass [] to clear all buttons.
@@ -25110,7 +25169,18 @@ type UpdateCommentAutomationResponse = ({
         id?: string;
         name?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.

package/dist/index.d.ts

@@ -5468,6 +5468,10 @@ type SocialAccount = {
      * - wabaId: WhatsApp Business Account ID
      * - phoneNumberId: Meta phone number ID
      *
+     * For LinkedIn accounts, profileData carries the profile details refreshed on each daily snapshot:
+     * - profileData.bio: The member's headline for personal accounts, or the organization description for organization accounts. null when the member has not set one.
+     * - profileData.extraData.vanityName: The member's profile slug, i.e. the /in/{vanityName} segment of profileUrl. Personal accounts only; an organization's own slug is in metadata.organizationInfo.vanityName.
+     *
      */
     metadata?: {
         [key: string]: unknown;
@@ -24844,7 +24848,18 @@ type ListCommentAutomationsResponse = ({
         platformPostId?: string;
         postTitle?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.
@@ -24931,7 +24946,18 @@ type CreateCommentAutomationData = {
          * Trigger keywords (empty = any comment triggers)
          */
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         /**
          * DM text to send to commenter. Max 640 chars when buttons are set, otherwise ~1000.
          */
@@ -24971,7 +24997,18 @@ type CreateCommentAutomationResponse = ({
         trigger?: 'comment' | 'story_reply';
         platformPostId?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.
@@ -25017,7 +25054,18 @@ type GetCommentAutomationResponse = ({
         postId?: string;
         postTitle?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.
@@ -25075,7 +25123,18 @@ type UpdateCommentAutomationData = {
     body?: {
         name?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (1-3). Pass [] to clear all buttons.
@@ -25110,7 +25169,18 @@ type UpdateCommentAutomationResponse = ({
         id?: string;
         name?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.512",
+  version: "0.2.514",
   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.512",
+  version: "0.2.514",
   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.512",
+  "version": "0.2.514",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/types.gen.ts

@@ -4421,6 +4421,10 @@ export type SocialAccount = {
      * - wabaId: WhatsApp Business Account ID
      * - phoneNumberId: Meta phone number ID
      *
+     * For LinkedIn accounts, profileData carries the profile details refreshed on each daily snapshot:
+     * - profileData.bio: The member's headline for personal accounts, or the organization description for organization accounts. null when the member has not set one.
+     * - profileData.extraData.vanityName: The member's profile slug, i.e. the /in/{vanityName} segment of profileUrl. Personal accounts only; an organization's own slug is in metadata.organizationInfo.vanityName.
+     *
      */
     metadata?: {
         [key: string]: unknown;
@@ -25191,7 +25195,18 @@ export type ListCommentAutomationsResponse = ({
         platformPostId?: string;
         postTitle?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.
@@ -25280,7 +25295,18 @@ export type CreateCommentAutomationData = {
          * Trigger keywords (empty = any comment triggers)
          */
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         /**
          * DM text to send to commenter. Max 640 chars when buttons are set, otherwise ~1000.
          */
@@ -25321,7 +25347,18 @@ export type CreateCommentAutomationResponse = ({
         trigger?: 'comment' | 'story_reply';
         platformPostId?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.
@@ -25370,7 +25407,18 @@ export type GetCommentAutomationResponse = ({
         postId?: string;
         postTitle?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.
@@ -25430,7 +25478,18 @@ export type UpdateCommentAutomationData = {
     body?: {
         name?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (1-3). Pass [] to clear all buttons.
@@ -25466,7 +25525,18 @@ export type UpdateCommentAutomationResponse = ({
         id?: string;
         name?: string;
         keywords?: Array<(string)>;
-        matchMode?: 'exact' | 'contains';
+        /**
+         * How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword.
+         */
+        matchMode?: 'exact' | 'contains' | 'word';
+        /**
+         * Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode.
+         */
+        excludeKeywords?: Array<(string)>;
+        /**
+         * Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched.
+         */
+        typoTolerance?: boolean;
         dmMessage?: string;
         /**
          * Inline DM buttons (up to 3). Omitted when none are set.