Connectors Changelog

Added large data sync capabilities to the New and Updated Emails polling trigger:

• Added opt-in batching to the New and Updated Emails 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 Emails trigger for performing an initial sync of email messages. The initial sync begins on the first recurrence and backfills every message received 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

• Added batching to the New and Updated Cards trigger; enabling it changes the shape a downstream step receives
• Added a Look-back Date input to the New and Updated Cards trigger; the backfill begins on the first recurrence, seeds each record once, and ignores the trigger's filters

Added opt-in batching and an initial sync to the New Emails polling trigger:

• Added opt-in batching to the New Emails trigger, dispatching each new email individually or in configured batches; enabling it changes the shape a downstream step receives
• Added an optional Look-back Date input to the New Emails trigger for performing an initial sync of emails. The initial sync begins on the first recurrence and backfills every email received 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 Updated Records polling trigger with batching and initial sync support:

• Added opt-in batching to the 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 begins on the first recurrence and backfills every record modified 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

• 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 filter; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill

• Added opt-in batching to the New and Updated Messages trigger, dispatching each changed message 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 Messages trigger for performing an initial sync. The initial sync begins on the first recurrence and seeds each message created or updated on or after the specified date once, ignoring the visibility filters. Leave it empty to start from the first recurrence with no backfill

Updated the New Records trigger to support large data syncs:

• Added opt-in batching to the New 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 Records trigger for performing an initial sync of Datasets, the one resource type that records a creation date. The initial sync begins on the first recurrence and backfills every dataset created on or after the specified date, seeding each once and ignoring the visibility filter; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill

• Added batching to the New and Updated Projects trigger; enabling it changes the shape a downstream step receives
• Added a Look-back Date input to the New and Updated Projects trigger; the backfill begins on the first recurrence, seeds each record once, and ignores the trigger's filters

• Added opt-in batching to the New and Updated Drive Items, New and Updated Folder Items, and New and Updated Site Items triggers, 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 opt-in batching to the New System Logs trigger, dispatching each event individually or in configured batches so large backlogs drain in one recurrence; enabling it changes the shape a downstream step receives
• Added opt-in batching to the New Users and Updated Users triggers, dispatching each user individually or in configured batches; enabling it changes the shape a downstream step receives
• Added an optional Look-back Date input to the New Users, Updated Users, and New System Logs triggers for performing an initial sync of records. The initial sync backfills every record on or after the specified date, beginning on the first recurrence and seeding each once; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill
• Fixed the Updated Users trigger returning the entire directory on its first recurrence; it now starts tracking from the first recurrence unless a Look-back Date is set
• Fixed users created or changed while the New Users and Updated Users triggers were reading being skipped on the next recurrence
• Updated the New System Logs trigger to resume from where the previous recurrence ended, following Okta's recommended polling pattern, rather than re-querying by time, which could skip or duplicate events