late-sdk 0.0.684 → 0.0.686

data/openapi.yaml

@@ -1404,6 +1404,49 @@ components:
           type: object
           additionalProperties: true
           description: Additional structured context (e.g. field-level validation errors).
+    CommentAutomationAudience:
+      type: object
+      description: |
+        Who a comment automation answers. Instagram only - Meta exposes the follow
+        relationship on no other platform, and only for people who have MESSAGED the
+        account (a comment grants no consent). `whenUnknown` is therefore the important
+        setting: it decides what happens for a first-time commenter.
+      properties:
+        followerStatus:
+          type: string
+          enum: [any, follower, non_follower]
+          default: any
+        minFollowerCount:
+          type: integer
+          minimum: 0
+          description: 'Skip commenters with fewer followers than this. Omit for no size rule.'
+        whenUnknown:
+          type: string
+          enum: [send, skip, verify]
+          default: send
+          description: |
+            What to do when Instagram will not reveal the follow relationship.
+              * `send` (default) - deliver the DM anyway (fails open).
+              * `skip` - stay silent.
+              * `verify` - send `followGate.message` with a confirm button. Tapping it is a
+                message, which grants consent, so the re-check on the tap resolves and the
+                real DM (or `followGate.notFollowingMessage`) follows automatically.
+    CommentAutomationFollowGate:
+      type: object
+      description: 'Copy for the follow gate. Sensible defaults are used for any field left empty.'
+      properties:
+        message:
+          type: string
+          maxLength: 640
+          description: 'Confirmation DM sent when whenUnknown=verify.'
+        buttonLabel:
+          type: string
+          maxLength: 20
+          description: 'Confirm button label. Defaults to "I''m following".'
+        notFollowingMessage:
+          type: string
+          maxLength: 1000
+          description: 'Sent to a commenter we know does not follow (followerStatus=follower). Omit to stay silent on a keyword comment; a confirm tap always gets an answer.'
     DmButton:
       type: object
       description: |
@@ -2670,6 +2713,25 @@ components:
                   type: string
                 picture:
                   type: [string, "null"]
+                instagramProfile:
+                  type: object
+                  description: |
+                    Instagram only, best-effort. Present ONLY for commenters who have
+                    messaged the account before: Meta gates the follow relationship behind
+                    messaging consent, and commenting does not grant it. Absent otherwise -
+                    treat a missing object as "unknown", never as "not a follower". To check
+                    on demand, call GET /v1/accounts/{accountId}/follow-status/{userId}.
+                  properties:
+                    isFollower:
+                      type: [boolean, "null"]
+                      description: The commenter follows this account.
+                    isFollowing:
+                      type: [boolean, "null"]
+                      description: This account follows the commenter.
+                    followerCount:
+                      type: [integer, "null"]
+                    isVerified:
+                      type: [boolean, "null"]
             createdAt:
               type: string
               format: date-time
@@ -7624,6 +7686,14 @@ components:
             zip: { type: string, description: "Meta advanced matching (zp). US uses first 5 digits; hashed server-side. Meta only." }
             dob: { type: string, description: "Meta advanced matching (db). YYYYMMDD; hashed server-side. Meta only." }
             gender: { type: string, description: "Meta advanced matching (ge). 'f' or 'm'; hashed server-side. Meta only." }
+            leadId:
+              type: string
+              description: |
+                Meta lead ID from a Lead Ad submission, as a string. Required
+                for Conversion Leads CRM events: send it with
+                `actionSource: 'crm'` and
+                `platformData: { event_source: 'crm', lead_event_source: '<CRM name>' }`.
+                Forwarded unhashed to Meta's `user_data.lead_id`. Meta only.
             clickIds:
               type: object
               description: Platform click identifiers captured from the originating ad click.
@@ -7664,7 +7734,13 @@ components:
         platformData:
           type: object
           additionalProperties: true
-          description: Escape hatch for platform-specific fields we haven't normalized. Forwarded as-is.
+          description: |
+            Escape hatch for platform-specific fields we haven't normalized.
+            On Meta, keys are shallow-merged into `custom_data` only: fields
+            Zernio already builds (`value`, `currency`, `contents`,
+            `num_items`) always win on collision, and `user_data` (hashed
+            match keys) is never touched. Use first-class fields (e.g.
+            `user.leadId`) for anything that must reach `user_data`.
 
     ConversionDestination:
       type: object
@@ -15031,6 +15107,80 @@ paths:
                 recommendations: []
         '401': { $ref: '#/components/responses/Unauthorized' }
         '404': { $ref: '#/components/responses/NotFound' }
+  /v1/accounts/{accountId}/follow-status/{userId}:
+    get:
+      operationId: getInstagramFollowStatus
+      tags: [Accounts]
+      x-platforms: ["instagram"]
+      summary: Check whether an Instagram user follows the account
+      description: |
+        Resolves the follow relationship between an Instagram user and the connected
+        account, plus their public profile counters.
+
+        `userId` is the Instagram-scoped id (IGSID) Meta gives you on a webhook:
+        `sender.id` on `message.received`, `comment.author.id` on `comment.received`.
+
+        **Meta only answers for people who have MESSAGED the account.** Commenting grants
+        no consent, so a commenter who has never DMed you is unresolvable - that is a
+        platform rule, not a limitation of this endpoint. When it cannot be resolved the
+        response is still `200` with `isFollower: null` and an `unavailableReason`, because
+        "unknown" is a normal state to branch on:
+
+          * `consent_required` - the user has never messaged this account.
+          * `dm_access_disabled` - the account owner turned off Instagram Direct API access.
+          * `not_messageable` - the id is not a messaging-scoped id.
+          * `error` - a transient Graph API failure.
+
+        To gate a comment automation on this, use the automation's `audience` rules instead
+        of calling this per comment - they run the same lookup only on comments that
+        actually match a keyword, and can ask the commenter to confirm with one tap.
+
+        Answers are cached briefly per (account, user). Pass `refresh=true` right after
+        asking someone to follow, so a follow from a moment ago is visible.
+      security:
+        - bearerAuth: []
+      parameters:
+        - { name: accountId, in: path, required: true, schema: { type: string }, description: Instagram account ID }
+        - { name: userId, in: path, required: true, schema: { type: string }, description: 'Instagram-scoped user id (IGSID) from a webhook payload' }
+        - { name: refresh, in: query, required: false, schema: { type: boolean }, description: Bypass the cache and re-query Meta }
+      responses:
+        '200':
+          description: Follow status (fields are null when Meta would not resolve it)
+          content:
+            application/json:
+              schema:
+                type: object
+                required: [userId, accountId, isFollower]
+                properties:
+                  userId: { type: string }
+                  accountId: { type: string }
+                  isFollower:
+                    type: [boolean, "null"]
+                    description: 'The user follows this account. Null = unknown, never "no".'
+                  isFollowedByAccount:
+                    type: [boolean, "null"]
+                    description: This account follows the user.
+                  followerCount: { type: [integer, "null"] }
+                  isVerified: { type: [boolean, "null"] }
+                  username: { type: [string, "null"] }
+                  name: { type: [string, "null"] }
+                  unavailableReason:
+                    type: [string, "null"]
+                    enum: [consent_required, dm_access_disabled, not_messageable, error, null]
+                    description: 'Why the follow relationship could not be resolved. Null when it was.'
+              example:
+                userId: "1312733120229708"
+                accountId: "6977a34e77637c5c857c816c"
+                isFollower: true
+                isFollowedByAccount: false
+                followerCount: 25
+                isVerified: false
+                username: "to.bias8262"
+                name: "Tobi Ma"
+                unavailableReason: null
+        '400': { $ref: '#/components/responses/BadRequest' }
+        '401': { $ref: '#/components/responses/Unauthorized' }
+        '404': { $ref: '#/components/responses/NotFound' }
   /v1/accounts/{accountId}/tiktok/creator-info:
     get:
       x-resource-group: "accounts"
@@ -35720,6 +35870,8 @@ paths:
                         commentReplyVariations: { type: array, items: { type: string }, description: "Alternate public replies rotated at random with commentReply. Omitted when none." }
                         linkTracking: { type: boolean, description: "Whether link buttons in the DM are wrapped in a tracked redirect to count clicks." }
                         clickTag: { type: string, description: "Tag applied to a contact when they click a tracked link." }
+                        dmDelaySeconds: { type: integer, description: "Seconds waited after the trigger before the DM is sent. Absent when the DM goes out immediately." }
+                        commentReplyDelaySeconds: { type: integer, description: "Seconds waited before the public reply is posted. Absent when it follows the DM immediately." }
                         isActive: { type: boolean }
                         stats:
                           type: object
@@ -35760,6 +35912,13 @@ paths:
             account-wide automations, each with its own keyword set, and they all run
             independently. Per-post automations take priority on their post.
 
+        Audience (`audience`, Instagram only): restrict the automation to followers or
+        non-followers, and/or to accounts above a follower count. Instagram only reveals the
+        follow relationship for people who have messaged the account, so `audience.whenUnknown`
+        decides what happens for everyone else - including `verify`, which sends a one-tap
+        confirmation DM (`followGate`) and then delivers the real DM automatically. People we
+        already know follow you skip the tap entirely.
+
         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.
@@ -35806,6 +35965,10 @@ paths:
                   description: "Optional alternate public replies, rotated at random alongside commentReply (picked independently of the DM). Up to 5."
                 linkTracking: { type: boolean, default: true, description: "Wrap link buttons in the DM in a tracked redirect so clicks are counted (Link Clicks / CTR). Pass false to send links exactly as written. Defaults to on." }
                 clickTag: { type: string, description: "Optional tag applied to a contact when they click a tracked link (requires linkTracking). Lets you segment clickers for broadcasts/sequences." }
+                dmDelaySeconds: { type: integer, minimum: 0, maximum: 86400, description: "Seconds to wait after the trigger before sending the DM. Omit or send 0 to reply immediately (the default). Max 86400 (24h). The trigger is still matched and deduplicated the moment the comment arrives, so a delay only moves when the response is sent." }
+                commentReplyDelaySeconds: { type: integer, minimum: 0, maximum: 86400, description: "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." }
+                audience: { $ref: '#/components/schemas/CommentAutomationAudience' }
+                followGate: { $ref: '#/components/schemas/CommentAutomationFollowGate' }
       responses:
         '200':
           description: Automation created
@@ -35837,6 +36000,10 @@ paths:
                       commentReplyVariations: { type: array, items: { type: string }, description: "Alternate public replies rotated at random with commentReply. Omitted when none." }
                       linkTracking: { type: boolean }
                       clickTag: { type: string }
+                      dmDelaySeconds: { type: integer, description: "Seconds waited after the trigger before the DM is sent. Absent when the DM goes out immediately." }
+                      commentReplyDelaySeconds: { type: integer, description: "Seconds waited before the public reply is posted. Absent when it follows the DM immediately." }
+                      audience: { $ref: '#/components/schemas/CommentAutomationAudience' }
+                      followGate: { $ref: '#/components/schemas/CommentAutomationFollowGate' }
                       isActive: { type: boolean }
                       stats: { type: object, properties: { totalTriggered: { type: integer }, totalSent: { type: integer }, totalFailed: { type: integer } } }
                       createdAt: { type: string, format: date-time }
@@ -35889,6 +36056,10 @@ paths:
                       commentReplyVariations: { type: array, items: { type: string }, description: "Alternate public replies rotated at random with commentReply. Omitted when none." }
                       linkTracking: { type: boolean }
                       clickTag: { type: string }
+                      dmDelaySeconds: { type: integer, description: "Seconds waited after the trigger before the DM is sent. Absent when the DM goes out immediately." }
+                      commentReplyDelaySeconds: { type: integer, description: "Seconds waited before the public reply is posted. Absent when it follows the DM immediately." }
+                      audience: { $ref: '#/components/schemas/CommentAutomationAudience' }
+                      followGate: { $ref: '#/components/schemas/CommentAutomationFollowGate' }
                       isActive: { type: boolean }
                       stats: { type: object, properties: { totalTriggered: { type: integer }, totalSent: { type: integer }, totalFailed: { type: integer } } }
                       createdAt: { type: string, format: date-time }
@@ -35903,10 +36074,14 @@ paths:
                         commenterId: { type: string }
                         commenterName: { type: string }
                         commentText: { type: string }
-                        status: { type: string, enum: [sent, failed, skipped], description: DM outcome }
+                        status: { type: string, enum: [pending, sent, failed, skipped, gated], description: "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." }
+                        audienceOutcome: { type: string, enum: [passed, blocked, gate_sent, gate_passed, gate_failed], description: "How the audience rule resolved. Absent on automations without one." }
+                        commenterIsFollower: { type: boolean, description: "Follow relationship at decision time. Absent when Instagram would not tell us (the commenter never messaged the account)." }
+                        commenterFollowerCount: { type: integer }
                         error: { type: string, description: DM error message if status is failed }
                         commentReplyStatus: { type: string, enum: [sent, failed, skipped], description: "Outcome of the optional public reply on the triggering comment. 'skipped' if no commentReply was configured or if the DM failed (the public reply is not attempted in that case)." }
                         commentReplyError: { type: string, description: Public-reply error message if commentReplyStatus is failed }
+                        nextDueAt: { type: string, format: date-time, description: "When the next queued send fires. Present only while something is still pending." }
                         createdAt: { type: string, format: date-time }
         '401': { $ref: '#/components/responses/Unauthorized' }
         '404': { $ref: '#/components/responses/NotFound' }
@@ -35954,6 +36129,10 @@ paths:
                   description: "Alternate public replies for random rotation. Pass [] to clear."
                 linkTracking: { type: boolean, description: "Wrap link buttons in a tracked redirect to count clicks. Pass false to send links untouched." }
                 clickTag: { type: string, description: "Tag applied to a contact when they click a tracked link (requires linkTracking). Empty string clears it." }
+                dmDelaySeconds: { type: integer, minimum: 0, maximum: 86400, description: "Seconds to wait after the trigger before sending the DM. Send 0 to clear the delay and reply immediately." }
+                commentReplyDelaySeconds: { type: integer, minimum: 0, maximum: 86400, description: "Seconds to wait before posting the public comment reply. Send 0 to clear it. The reply never goes out before the DM." }
+                audience: { $ref: '#/components/schemas/CommentAutomationAudience' }
+                followGate: { $ref: '#/components/schemas/CommentAutomationFollowGate' }
                 isActive: { type: boolean }
       responses:
         '200':
@@ -35981,6 +36160,8 @@ paths:
                       commentReply: { type: string }
                       dmMessageVariations: { type: array, items: { type: string }, description: "Alternate DM texts rotated at random with dmMessage. Omitted when none." }
                       commentReplyVariations: { type: array, items: { type: string }, description: "Alternate public replies rotated at random with commentReply. Omitted when none." }
+                      audience: { $ref: '#/components/schemas/CommentAutomationAudience' }
+                      followGate: { $ref: '#/components/schemas/CommentAutomationFollowGate' }
                       isActive: { type: boolean }
                       updatedAt: { type: string, format: date-time }
         '401': { $ref: '#/components/responses/Unauthorized' }
@@ -36011,7 +36192,7 @@ paths:
         - bearerAuth: []
       parameters:
         - { name: automationId, in: path, required: true, schema: { type: string } }
-        - { name: status, in: query, schema: { type: string, enum: [sent, failed, skipped] }, description: Filter by result status }
+        - { name: status, in: query, schema: { type: string, enum: [pending, sent, failed, skipped, gated] }, description: Filter by result status }
         - { name: limit, in: query, schema: { type: integer, default: 50, minimum: 1, maximum: 200 } }
         - { name: skip, in: query, schema: { type: integer, default: 0, minimum: 0 } }
       responses:
@@ -36033,10 +36214,14 @@ paths:
                         commenterId: { type: string }
                         commenterName: { type: string }
                         commentText: { type: string }
-                        status: { type: string, enum: [sent, failed, skipped], description: DM outcome }
+                        status: { type: string, enum: [pending, sent, failed, skipped, gated], description: "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." }
+                        audienceOutcome: { type: string, enum: [passed, blocked, gate_sent, gate_passed, gate_failed], description: "How the audience rule resolved. Absent on automations without one." }
+                        commenterIsFollower: { type: boolean, description: "Follow relationship at decision time. Absent when Instagram would not tell us (the commenter never messaged the account)." }
+                        commenterFollowerCount: { type: integer }
                         error: { type: string, description: DM error message if status is failed }
                         commentReplyStatus: { type: string, enum: [sent, failed, skipped], description: "Outcome of the optional public reply on the triggering comment. 'skipped' if no commentReply was configured or if the DM failed (the public reply is not attempted in that case)." }
                         commentReplyError: { type: string, description: Public-reply error message if commentReplyStatus is failed }
+                        nextDueAt: { type: string, format: date-time, description: "When the next queued send fires. Present only while something is still pending." }
                         createdAt: { type: string, format: date-time }
                   pagination:
                     type: object

data/spec/api/accounts_api_spec.rb

@@ -86,6 +86,20 @@ describe 'AccountsApi' do
     end
   end
 
+  # unit tests for get_instagram_follow_status
+  # Check whether an Instagram user follows the account
+  # Resolves the follow relationship between an Instagram user and the connected account, plus their public profile counters.  `userId` is the Instagram-scoped id (IGSID) Meta gives you on a webhook: `sender.id` on `message.received`, `comment.author.id` on `comment.received`.  **Meta only answers for people who have MESSAGED the account.** Commenting grants no consent, so a commenter who has never DMed you is unresolvable - that is a platform rule, not a limitation of this endpoint. When it cannot be resolved the response is still `200` with `isFollower: null` and an `unavailableReason`, because \"unknown\" is a normal state to branch on:    * `consent_required` - the user has never messaged this account.   * `dm_access_disabled` - the account owner turned off Instagram Direct API access.   * `not_messageable` - the id is not a messaging-scoped id.   * `error` - a transient Graph API failure.  To gate a comment automation on this, use the automation's `audience` rules instead of calling this per comment - they run the same lookup only on comments that actually match a keyword, and can ask the commenter to confirm with one tap.  Answers are cached briefly per (account, user). Pass `refresh=true` right after asking someone to follow, so a follow from a moment ago is visible. 
+  # @param account_id Instagram account ID
+  # @param user_id Instagram-scoped user id (IGSID) from a webhook payload
+  # @param [Hash] opts the optional parameters
+  # @option opts [Boolean] :refresh Bypass the cache and re-query Meta
+  # @return [GetInstagramFollowStatus200Response]
+  describe 'get_instagram_follow_status test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   # unit tests for get_slack_settings
   # Get Slack account settings
   # Returns the connected Slack channel details and the default message identity (name and avatar shown as the author on every post, with Slack's APP badge). The identity applies to messages only; the app's own Slack profile is global and cannot be changed per workspace.

data/spec/api/comment_automations_api_spec.rb

@@ -34,7 +34,7 @@ describe 'CommentAutomationsApi' do
 
   # unit tests for create_comment_automation
   # Create comment-to-DM automation
-  # Create a keyword-triggered DM automation on an Instagram or Facebook account. When someone comments a matching keyword (or, with `trigger: story_reply`, replies to your Instagram story with one), they automatically receive a DM.  Triggers (`trigger`):   * `comment` (default): fires on keyword comments on a post or reel.   * `story_reply`: fires when someone replies to your Instagram story with a keyword,     and answers them with a DM. Set `platformPostId` to a story media id to scope to     one story, or omit it to match replies to any story.  Targeting (comment trigger):   * Per-post: set `platformPostId` to scope to one specific post (only one active     per-post automation is allowed per post).   * Account-wide (\"any post\"): omit `platformPostId` (and `postId`). The automation     evaluates every comment on every post on the account. You can stack unlimited     account-wide automations, each with its own keyword set, and they all run     independently. Per-post automations take priority on their post.  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. 
+  # Create a keyword-triggered DM automation on an Instagram or Facebook account. When someone comments a matching keyword (or, with `trigger: story_reply`, replies to your Instagram story with one), they automatically receive a DM.  Triggers (`trigger`):   * `comment` (default): fires on keyword comments on a post or reel.   * `story_reply`: fires when someone replies to your Instagram story with a keyword,     and answers them with a DM. Set `platformPostId` to a story media id to scope to     one story, or omit it to match replies to any story.  Targeting (comment trigger):   * Per-post: set `platformPostId` to scope to one specific post (only one active     per-post automation is allowed per post).   * Account-wide (\"any post\"): omit `platformPostId` (and `postId`). The automation     evaluates every comment on every post on the account. You can stack unlimited     account-wide automations, each with its own keyword set, and they all run     independently. Per-post automations take priority on their post.  Audience (`audience`, Instagram only): restrict the automation to followers or non-followers, and/or to accounts above a follower count. Instagram only reveals the follow relationship for people who have messaged the account, so `audience.whenUnknown` decides what happens for everyone else - including `verify`, which sends a one-tap confirmation DM (`followGate`) and then delivers the real DM automatically. People we already know follow you skip the tap entirely.  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. 
   # @param create_comment_automation_request 
   # @param [Hash] opts the optional parameters
   # @return [CreateCommentAutomation200Response]

data/spec/models/comment_automation_audience_spec.rb

@@ -0,0 +1,56 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api 
+
+The version of the OpenAPI document: 1.0.4
+Contact: support@zernio.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.19.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Zernio::CommentAutomationAudience
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zernio::CommentAutomationAudience do
+  #let(:instance) { Zernio::CommentAutomationAudience.new }
+
+  describe 'test an instance of CommentAutomationAudience' do
+    it 'should create an instance of CommentAutomationAudience' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zernio::CommentAutomationAudience)
+    end
+  end
+
+  describe 'test attribute "follower_status"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["any", "follower", "non_follower"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.follower_status = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "min_follower_count"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "when_unknown"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["send", "skip", "verify"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.when_unknown = value }.not_to raise_error
+      # end
+    end
+  end
+
+end

data/spec/models/comment_automation_follow_gate_spec.rb

@@ -0,0 +1,48 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api 
+
+The version of the OpenAPI document: 1.0.4
+Contact: support@zernio.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.19.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Zernio::CommentAutomationFollowGate
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zernio::CommentAutomationFollowGate do
+  #let(:instance) { Zernio::CommentAutomationFollowGate.new }
+
+  describe 'test an instance of CommentAutomationFollowGate' do
+    it 'should create an instance of CommentAutomationFollowGate' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zernio::CommentAutomationFollowGate)
+    end
+  end
+
+  describe 'test attribute "message"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "button_label"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "not_following_message"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/conversion_event_user_spec.rb

@@ -105,6 +105,12 @@ describe Zernio::ConversionEventUser do
     end
   end
 
+  describe 'test attribute "lead_id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "click_ids"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/create_comment_automation200_response_automation_spec.rb

@@ -131,6 +131,30 @@ describe Zernio::CreateCommentAutomation200ResponseAutomation do
     end
   end
 
+  describe 'test attribute "dm_delay_seconds"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "comment_reply_delay_seconds"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "audience"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "follow_gate"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "is_active"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/create_comment_automation_request_spec.rb

@@ -143,4 +143,28 @@ describe Zernio::CreateCommentAutomationRequest do
     end
   end
 
+  describe 'test attribute "dm_delay_seconds"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "comment_reply_delay_seconds"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "audience"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "follow_gate"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
 end

data/spec/models/get_comment_automation200_response_automation_spec.rb

@@ -149,6 +149,30 @@ describe Zernio::GetCommentAutomation200ResponseAutomation do
     end
   end
 
+  describe 'test attribute "dm_delay_seconds"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "comment_reply_delay_seconds"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "audience"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "follow_gate"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "is_active"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/get_comment_automation200_response_logs_inner_spec.rb

@@ -60,13 +60,35 @@ describe Zernio::GetCommentAutomation200ResponseLogsInner do
   describe 'test attribute "status"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["sent", "failed", "skipped"])
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["pending", "sent", "failed", "skipped", "gated"])
       # validator.allowable_values.each do |value|
       #   expect { instance.status = value }.not_to raise_error
       # end
     end
   end
 
+  describe 'test attribute "audience_outcome"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["passed", "blocked", "gate_sent", "gate_passed", "gate_failed"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.audience_outcome = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "commenter_is_follower"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "commenter_follower_count"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "error"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
@@ -89,6 +111,12 @@ describe Zernio::GetCommentAutomation200ResponseLogsInner do
     end
   end
 
+  describe 'test attribute "next_due_at"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "created_at"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/