Skip to main content

Changelog

Connectors Changelog

Keep track of updates and enhancements to our connectors.

Amazon Seller Central (2026-10-09)

  • 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 changed 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 Records trigger returning no orders when Resource Type is set to Orders, and the Select Order data source returning no options

Domo (2026-10-09)

  • 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. For resources tracked by timestamp, the initial sync begins on the first recurrence and backfills every record created or 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

Gong (2026-10-09)

  • 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 calls. The initial sync begins on the first recurrence and backfills every call started on or after the specified date, seeding each once and ignoring the visibility filter. It applies to the Calls resource only and has no effect on Users. Leave it empty to start from the first recurrence with no backfill

GoTo Webinar (2026-10-09)

  • Added opt-in batching to the New Registrants 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 Registrants trigger for performing an initial sync of records. The initial sync begins on the first recurrence and backfills every registrant who registered 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

Jira Service Management (2026-10-09)

  • Added opt-in batching to the New Service Requests and New Ops Alerts triggers, dispatching each new 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 Service Requests and New Ops Alerts triggers for performing an initial sync. The initial sync begins on the first recurrence and seeds each request or alert created on or after the specified date once; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill

Rippling (2026-10-09)

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

UKG Pro (2026-10-09)

  • Added opt-in batching to the Employee Changes and New Hire Status triggers, 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 Employee Changes trigger for performing an initial sync of records. The initial sync begins on the first recurrence and seeds each employee change made on or after the specified date once; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill

Date/Time (2026-10-08)

Updated time zone selection and added configuration-time support across all actions:

  • Updated the Time Zone dropdown to also list alias time zone names, such as Iceland and Africa/Dakar
  • Updated the default Time Zone on the Format Date/Time action to Etc/UTC so it matches a value in the dropdown
  • Added output schemas across all actions for improved field mapping during configuration
  • Added inline action calling support across all actions for improved example output during configuration

Kafka (2026-10-08)

Added Amazon MSK IAM authentication, along with connection and trigger updates:

  • Added the IAM Access Key and Secret and IAM Role ARN connections for Amazon MSK clusters that use IAM access control
  • Added a required AWS Region dropdown to the IAM Access Key and Secret and IAM Role ARN connections for selecting the region of the Amazon MSK cluster
  • Updated the Schema Registry API Key field on the Basic Authentication connection to a masked password field
  • Updated the Kafka Consumer trigger to group From Beginning, Auto Commit, and Deserialize Keys as Avro into a Consumer Options structured object, and to show Session Timeout (ms) and Heartbeat Interval (ms) as top-level inputs again in place of the Session Timing group
  • Updated the Kafka Consumer trigger to fail the run when the consumer cannot start, such as when it cannot join its consumer group, and to reject a Max Messages value below 1
  • Updated the Publish Messages action to close its broker connection when sending messages fails

Contentful (2026-10-07)

Added inline action calling, output schemas, trigger initial sync and batching, and webhook request verification, and improved trigger and upload reliability:

  • Added inline action calling support to 54 actions for improved example output during configuration
  • Added output schemas to 47 actions for improved field mapping during configuration
  • Added opt-in batching to the New and Updated Entries trigger, dispatching each changed entry 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 Entries trigger for performing an initial sync of entries. The initial sync begins on the first recurrence and backfills every entry 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
  • Added an optional Webhook Signing Secret input to the Event Subscription and Webhook triggers that rejects requests failing Contentful's request verification
  • Updated the New and Updated Entries trigger to deliver every changed entry when more change between recurrences than a single recurrence fetches; the remainder is delivered on the following recurrences
  • Updated the Event Subscription trigger to reuse its existing Contentful webhook on redeploy, updating its events in place rather than creating another webhook that invoked the flow again; duplicates left by earlier deploys, and the webhook in a previously configured space, are removed
  • Updated Upload File to send the file's raw bytes, so the upload stores the file's content
  • Updated the Scopes input on the OAuth 2.0 connection to a dropdown of the scopes Contentful accepts