Skip to main content

Changelog

Connectors Changelog

Keep track of updates and enhancements to our connectors.

Google Ads (2026-10-07)

Updated the component for Google's developer token sunset, added an initial sync to the change history triggers, and fixed several trigger, action, and data source issues:

  • Updated the OAuth 2.0 connection so Developer Token is optional and no longer sent with any request, following Google's September 9, 2026 developer token sunset; the connection setup guidance now describes Google Cloud project access levels instead of the API Center
  • Added an optional Look-back Date input on the New and Updated Campaigns and Account Change History triggers for performing an initial sync of changes. The initial sync begins on the first recurrence and backfills every change made on or after the specified date, up to Google's 30-day change history window, seeding each once; without batching, a large backfill can span several recurrences before normal polling resumes. Leave it empty to start from one hour before the first recurrence
  • Fixed the New and Updated Campaigns and Account Change History triggers losing the oldest changes when a recurrence found more than a single query returns (10,000 changes and 1,000 changes respectively); changes are now read oldest first and the remainder is delivered on the following recurrences, or within the same recurrence when batching is enabled
  • Fixed New and Updated Campaigns reporting only created and removed campaigns when Change Types to Monitor is left empty; an empty selection now detects all change types as documented, so flows that leave it empty also receive status, bidding strategy, and budget changes
  • Updated New and Updated Campaigns to report a missing oldValue or newValue as null instead of omitting the field
  • Fixed Account Change History failing every recurrence when Resource Types includes Keywords, or once more than 30 days passed without a successful recurrence; Keywords now returns ad group criterion changes, which include keyword changes, and the query start is limited to Google's 30-day change history window
  • Fixed Campaign Budget Alerts ignoring Include Shared Budgets when turned off, comparing daily budgets against spend accumulated since the last recurrence (which could include earlier days) instead of today's spend, and omitting alertThreshold when Alert Threshold (%) is left empty; the default threshold is now reported
  • Fixed Get Account Reports and Get Detailed Lead Reports sending invalid date values when Start Date or End Date is left empty; an empty date is now omitted from the request
  • Fixed Search Ads sending Return Total Results Count as a request field the Google Ads API does not recognize; it is now sent in the search settings, so the total count is returned
  • Fixed the List Accessible Sub Accounts data source failing when Customer Client Level is left empty; it now defaults to level 1
  • Updated the Upload Click Conversions description to state that only developer tokens with no offline conversion upload between December 17, 2025 and June 15, 2026 lose access to the endpoint, rather than the action stopping for everyone after June 15, 2026

ArcGIS (2026-10-06)

Fixed an issue when a step using a customer OAuth 2.0 connection was added to a flow in the designer

ClickUp (2026-10-06)

Fixed several action and trigger defects, and added initial sync, batching, grouped inputs, output schemas, and inline action calling:

  • Fixed Get Task Members sending a DELETE request instead of a GET, so the action now returns the task's members
  • Fixed Raw Request failing to authenticate with a Personal Access Token connection
  • Fixed New and Updated Tasks never returning closed tasks or subtasks
  • Fixed Edit User on Workspace renaming every edited user to "User Name"; it now keeps the current username unless the new optional Username input is set
  • Fixed Update Task clearing the task's Name, Description, Status, and Parent when those inputs were left empty; optional inputs left empty are now omitted from requests across the component
  • Added an optional Look-back Date input to the New and Updated Tasks trigger for performing an initial sync of tasks. The initial sync begins on the first recurrence and backfills every task 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
  • Added opt-in batching to the New and Updated Tasks trigger, dispatching each changed task individually or in configured batches so large backlogs drain in one recurrence; enabling it changes the shape a downstream step receives, which gets each changed task with its change type instead of separate created and updated lists
  • Updated List Tasks to group its date filters into Date Range Filters and its sort, archive, closed-task, and custom-field query controls into Filters
  • Updated Create Task and Update Task to group their start date, due date, and time estimate inputs into Schedule, with Create Task also grouping its Markdown description, notification, and required custom field options into Additional Fields, and Get Task Comments to group its start date and start ID cursor into Pagination
  • Added output schemas to 49 actions for improved field mapping during configuration
  • Added inline action calling support to 64 actions for improved example output during configuration

Amazon S3 (2026-10-05)

Added new inputs and polling trigger capabilities, and fixed issues in file polling, bucket listing, and webhook message verification:

  • Added an optional Version ID input to the Get Object and Head Object actions for retrieving a specific object version
  • Added an optional Topic ARN input to the Webhook trigger that rejects messages from any other Amazon SNS topic
  • Added opt-in batching to the New and Updated Files trigger, dispatching each file 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 Buckets trigger, dispatching each bucket individually or in configured batches; enabling it changes the shape a downstream step receives
  • Added an optional Look-back Date input on the New and Updated Files and New Buckets triggers for performing an initial sync. The initial sync begins on the first recurrence and backfills every file modified, or bucket 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 List Objects to group its Max Keys and Continuation Token inputs into a Pagination structured object
  • Added inline action calling support across all actions for improved example output during configuration
  • Added output schemas to 29 actions for improved field mapping during configuration
  • Updated action labels: Bucket SNS Event Trigger Configuration is now Add Bucket SNS Event Notification, and the Upload Stream - Create Stream, Upload Stream - Write Data, and Upload Stream - Close Stream actions are now Create Upload Stream, Write Upload Stream, and Close Upload Stream
  • Fixed the New and Updated Files trigger missing files: files beyond the first 1,000 keys in a bucket were never detected, and a file modified in the same second a recurrence started was never returned
  • Fixed the List Buckets action, the Select Bucket data source, and the New Buckets trigger failing for AWS accounts with a general purpose bucket quota above 10,000, where Amazon S3 rejects unpaginated bucket listings
  • Fixed the Webhook trigger accepting messages not signed by Amazon SNS, including forged subscription confirmations it would then confirm against any URL

Monday (2026-10-01)

Added batching, initial sync, and configuration improvements to the Monday.com component:

  • Added opt-in batching to the New and Updated Items 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 on the New and Updated Items trigger. The initial sync backfills every record modified on or after the specified date, beginning on the first recurrence and seeding each record once; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill
  • Added inline action calling support to the Archive Board, Create Board, Create Webhook, Delete Webhook, Get Board, Get Items By Column Value, List Boards, and List Webhooks actions for improved example output during configuration
  • Added output schemas to the Archive Board, Create Board, Create Webhook, Delete Webhook, Get Board, Get Items By Column Value, List Boards, and List Webhooks actions for improved field mapping during configuration

Confluence (2026-09-30)

  • Grouped the pagination inputs on the List Pages, List Pages in Space, List Spaces, List Attachments, Get Attachments for Page, List Content Properties for Page, List Content Properties for Attachments, and List Content Properties for Custom Content actions into a Pagination object, and grouped the optional retrieval and expansion inputs on the Get Page action into an Additional Fields object
  • Added inline action calling support to 31 actions for improved example output during configuration
  • Added output schemas to 22 actions for improved field mapping during configuration
  • Added opt-in batching to the New and Updated Pages and New Spaces triggers, dispatching each changed record individually or in configured batches so large backlogs drain in one poll cycle; enabling it changes the shape a downstream step receives
  • Added an optional Look-back Date input for performing an initial sync of records on the New and Updated Pages and New Spaces triggers. The initial sync 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

GitHub (2026-09-29)

  • Added opt-in batching to the New and Updated Records trigger, dispatching each changed record individually or in configured batches, with each recurrence returning at most 500 records (oldest first) so large backlogs drain over later recurrences; 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
  • Added output schemas to 15 actions for improved field mapping during configuration
  • Added inline action calling support to 18 actions for improved example output during configuration
  • Updated the Repos List For Org, Orgs List For Authenticated User, Issues List For Repo, Issues List Comments, and Pulls List actions to group their page and per-page inputs into Pagination for an improved user experience; Fetch All stays a top-level toggle on Issues List For Repo
  • Added documentation for the Webhook trigger and prerequisites for the OAuth 2.0 connection
  • Fixed the New and Updated Records trigger so a record created during the same second the previous recurrence ran is delivered as a new record instead of being classed as updated, which dropped it when Show Updated Records was off
  • Fixed the Event Webhook trigger so redeploying an instance no longer leaves an extra GitHub webhook registered on the repository, which previously caused each event to be delivered once per deployment; changing Owner, Repository Name, or Events now deletes the existing webhook before creating its replacement
  • Fixed the Issues List For Repo action so the Per Page input is sent to GitHub as the API page-size parameter and Fetch All advances through pages instead of repeatedly fetching the first page

Adobe Commerce Magento (2026-09-28)

Added merchant store authentication so that actions, triggers, and data sources read and write data in an Adobe Commerce store:

  • Added the OAuth 1.0a connection, which authenticates against a merchant store with an integration's consumer key and access token credentials and takes a Store URL plus an optional Store Code for installations serving multiple store views
  • Updated the API Access Key connection to API Access Key (Deprecated); it authenticates against the Adobe Commerce Marketplace Developer portal rather than a merchant store, so it cannot read or write orders, products, customers, or transactions
  • Fixed the Select Order, Select Customer, Select Transaction, Product Types, Product Attribute Types, and Product Option Types data sources, which failed to load their options; all six now present their options ordered by label
  • Added an optional Look-back Date input for performing an initial sync of records on the New and Updated Records trigger. The initial sync backfills every record modified 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
  • Updated the New and Updated Records trigger to walk a truncated backlog forward in oldest-first order, so a set of changes larger than one recurrence's page cap drains across later recurrences instead of repeating the most recent records
  • Updated the Webhook trigger so it no longer offers a synchronous response or a schedule
  • Updated every action to raise an API failure as an error carrying message, data, status, and headers as fields, replacing the single JSON-encoded message string
  • Added inline action calling support to 19 actions for improved example output during configuration

Klaviyo (2026-09-28)

  • Added output schemas to 37 actions for improved field mapping during configuration
  • Added inline action calling support to the Get Account, Get Campaign, Get Event, Get Image, Get List, Get Profile, Get Segment, Get Template, and List Accounts actions for improved example output during configuration
  • Added opt-in batching to the New and Updated Campaigns and New and Updated Profiles and Lists 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 an optional Look-back Date input for performing an initial sync of records on the New and Updated Campaigns and New and Updated Profiles and Lists triggers. The initial sync 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
  • Fixed the New and Updated Campaigns and New and Updated Profiles and Lists triggers reporting no changes on every recurrence, so new and updated records never reached the flow