Connectors Changelog

• Added opt-in batching to the New and Updated Records trigger, dispatching each changed record individually or in configured batches; enabling it changes the shape a downstream step receives
• Added an optional Look-back Date input for performing an initial sync of records. The initial sync backfills every message sent on or after the specified date, beginning on the first recurrence, seeding each record once, and ignoring the visibility filters. Leave it empty to start from the first recurrence with no backfill
• Fixed the New and Updated Records trigger re-delivering the most recent 10,000 messages on every recurrence, and never retrieving the older ones, once 10,000 or more messages were sent between recurrences; it now delivers the older messages over the following recurrences, each once

• Added opt-in batching to the New Envelopes trigger, dispatching each changed record individually or in configured batches; enabling it changes the shape a downstream step receives
• Added an optional Look-back Date input for performing an initial sync of records. The initial sync backfills every envelope created on or after the specified date, seeding each once; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill

Updated the New and Updated Agreements polling trigger with batching and initial sync support:

• Added opt-in batching to the New and Updated Agreements trigger, dispatching each changed record individually or in configured batches so large backlogs drain in one recurrence; enabling it changes the shape a downstream step receives
• Added an optional Look-back Date input for performing an initial sync of records. The initial sync begins on the first recurrence and backfills every record modified on or after the specified date, seeding each once and ignoring the visibility filters; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill

Fixed Fetch All and certificate handling defects and improved action configuration:

• Fixed List Worker Demographics with Fetch All enabled returning only the first 100 workers on accounts with 100 or more workers, and never finishing on accounts with fewer than 100
• Fixed List Workers with Fetch All enabled and a Filter returning empty entries alongside the matching workers
• Fixed the Select Worker data source failing with an error when a Filter is set
• Fixed Raw Request failing the TLS handshake when the connection's Key File or Certificate File stores its line breaks as escaped newlines, which the other actions already accepted
• Updated List Workers, List Worker Demographics, and Get Time Cards to group their Skip and Top inputs into Pagination; Fetch All stays a top-level toggle
• Updated the Select Worker and Select Personal Contact data sources to no longer take the Select input
• Added inline action calling support to 23 actions for improved example output during configuration
• Added output schemas to 19 actions for improved field mapping during configuration

• Added opt-in batching to the New and Updated Issues trigger, dispatching each changed issue individually or in configured batches so large backlogs drain in one recurrence; enabling it changes the shape a downstream step receives
• Added an optional Look-back Date input to the New and Updated Issues trigger for performing an initial sync of issues. The initial sync begins on the first recurrence and backfills every issue modified on or after the specified date, seeding each once and ignoring the visibility filters; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill
• Fixed the New and Updated Issues trigger never delivering the issues beyond the page limit when more issues changed between recurrences than one recurrence could read; the remainder is now delivered on later recurrences
• Fixed the New and Updated Issues trigger returning few or no issues for Jira accounts in a time zone west of UTC and repeatedly returning the same issues for accounts in a time zone east of UTC; it now filters by date in the account's time zone

Added large data sync support to the Changed Employees trigger:

• Added opt-in batching to the Changed Employees trigger, dispatching each changed record individually or in configured batches; enabling it changes the shape a downstream step receives
• Added an optional Look-back Date input for performing an initial sync of employees. The initial sync begins on the first recurrence and backfills every employee changed on or after the specified date, seeding each once and ignoring the trigger's filters; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill

Various modernizations and documentation updates

• Added opt-in batching to the New and Updated Records trigger, dispatching each changed record individually or in configured batches; enabling it changes the shape a downstream step receives
• Added an optional Look-back Date input to the New and Updated Records trigger for performing an initial sync of records. The initial sync begins on the first recurrence and backfills every record modified on or after the specified date, seeding each once and ignoring the visibility filters. Leave it empty to start from the first recurrence with no backfill
• Fixed the New and Updated Records trigger re-delivering the same newest records on every recurrence and never delivering the older ones when more changes had accumulated than one recurrence could read; it now continues from where the previous recurrence stopped

Added large data sync support to the New and Updated Assets polling trigger:

• Added opt-in batching to the New and Updated Assets trigger, dispatching each changed record individually or in configured batches; enabling it changes the shape a downstream step receives
• Added an optional Look-back Date input for performing an initial sync of records. The initial sync begins on the first recurrence and backfills every record modified on or after the specified date, seeding each once and ignoring the visibility filters; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill

Initial release of GitLab component for GitLab.com and self-managed instances, with Access Token and OAuth 2.0 connections that can each reach an instance on a private network through the on-prem agent:

• Added 37 actions for projects, groups, users, branches, commits, repository files, issues, merge requests, notes, pipelines, labels, milestones, project members, and webhooks, including a Raw Request action, with data sources for selecting projects, groups, branches, labels, milestones, and users
• Added the Webhook, Webhook Events, and New and Updated Records triggers; New and Updated Records detects created and updated issues or merge requests in a project and offers opt-in batching, dispatching each changed record individually or in configured batches; enabling it changes the shape a downstream step receives
• Added an optional Look-back Date input to the New and Updated Records trigger for performing an initial sync of records. The initial sync begins on the first recurrence and backfills every record modified on or after the specified date, seeding each once and ignoring the trigger's filters; once it completes, later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill
• Added output schemas to 36 actions for improved field mapping during configuration
• Added inline action calling support to 36 actions for improved example output during configuration