Skip to main content

Changelog

Connectors Changelog

Keep track of updates and enhancements to our connectors.

Google Ads (2026-08-31)

Updated the component to Google Ads API v25 with reworked campaign change detection and opt-in batching across all polling triggers:

  • Updated the default API version for new connections to v25, matching Google's current major release; updated the minimum supported version to v22, so v22 through v25 are all selectable and connections pinned below v22 are automatically upgraded
  • Updated the New and Updated Campaigns trigger to read the Google Ads change history instead of storing a copy of every campaign between recurrences, a breaking change; totalCampaigns is no longer returned, oldValue and newValue now carry the campaign resource directly rather than wrapped in a query row, a timeRange object was added alongside syncedAt, and detection is bounded by Google's 30-day change history window
  • Added opt-in batching to the New and Updated Campaigns, Account Change History, and Campaign Budget Alerts triggers, dispatching each record individually or in configured batches so large backlogs drain in one recurrence; enabling it changes the shape a downstream step receives
  • Updated Get Account Reports and Get Detailed Lead Reports to group their Page Size and Page Token inputs into a Pagination structured object
  • Added connection setup guidance for Google's passkey requirement; from August 5, 2026 a passkey is required to authorize new Google Ads API access, and a new passkey can take up to 7 days to become usable
  • Added output schemas to 14 actions for improved field mapping during configuration
  • Added inline action calling support across all actions for improved example output during configuration

Qualys (2026-08-31)

Updated the Changed Assets polling trigger to tag each batched record with its change type, so downstream steps can distinguish newly created assets from updated ones

Stripe (2026-08-31)

  • Added output schemas to 61 actions for improved field mapping during configuration
  • Added inline action calling support across all actions for improved example output during configuration
  • Added a Select Card dropdown to Payment Method ID on Attach Card, Detach Card, Get Card, Update Card, Create Invoice, Update Invoice, and Create Subscription, listing the cards saved against the selected Customer ID instead of requiring the ID to be typed
  • Added the Webhook Secret input to the Webhook Events trigger as a masked field, so signature validation can be configured when a deployment reused a pre-existing Stripe endpoint; Stripe returns a signing secret only when an endpoint is created, so none is stored in that case

Updated actions and trigger functionality:

  • Amount on Create Payment Intent and Update Payment Intent now reports a fractional value as an error naming the field, instead of truncating it and charging the smaller whole number: an entered 44.55 was charged as 44 in the smallest currency unit. Amount is required, so every configuration of these two actions supplies it
  • Balance on Create Customer and Update Customer and Unit Price on Create Price are now sent as entered instead of multiplied by 100, matching Stripe's smallest currency unit convention
  • Added the Payment Method ID input that Update Card and Update Subscription both send but never collected
  • Create Checkout Session now sends the Customer Email, Customer ID, and Client Reference ID it collects
  • Create Card now attaches the created card to the customer identified by Customer ID
  • Reconfiguring the Webhook Events trigger's selected events now updates its managed Stripe endpoint in place and preserves the endpoint's signing secret, instead of adding a second endpoint at the same flow URL that delivered every overlapping event twice
  • Fixed the Webhook Events trigger lifecycle so the managed endpoint is matched by the flow's URL and removed when the instance is torn down even if its events were reconfigured after deployment, leaving no orphaned endpoints in the Stripe account, and so testing the trigger no longer fails on the absent signature header
  • Delete All Instance Webhooks now returns only the endpoints it deleted, instead of padding the returned list with a blank entry for every other webhook endpoint in the Stripe account
  • New and Updated Records now holds its polling cursor when a recurrence returns more events than it can fetch, instead of advancing past the events it left behind
  • An explicit false or 0 now reaches Stripe, so Update Price can deactivate a price, Create Product and Update Product can clear Shippable, Create Invoice and Update Invoice can turn off Auto Advance, Update Customer can clear a Balance, Create Price can set a free Unit Price, Create Subscription and Update Subscription can set a Quantity of zero, and Create Subscription can set Days Until Due to zero for an invoice due on receipt
  • A 0 referenced from an earlier step now survives on Application Fee Amount and Amount to Capture instead of being discarded as blank, so it no longer silently becomes a full capture; an omitted Amount to Capture tells Stripe to capture the whole authorized amount (a 0 typed directly into the field was already sent correctly)
  • Limit, Application Fee Amount, Amount to Capture, Unit Price on Create Price, and Balance on Create Customer and Update Customer accept whole numbers only, and now report a fractional value as an error naming the field instead of rounding it down or forwarding it for Stripe to reject
  • Leaving Payment Method Types on Create Payment Intent and Update Payment Intent, or Event Types on New and Updated Records, blank no longer fails the step
  • Leaving Webhook Events blank on Update Webhook now leaves the endpoint's stored events alone instead of failing the step, matching how a blank Webhook URL already behaved
  • Charge ID left blank on List Disputes is now omitted rather than sent as an empty charge ID
  • A blank Timeout now falls back to the Stripe client default instead of configuring the client with no timeout at all
  • Optional fields left blank are now omitted instead of sent as an empty string, covering Currency on Update Payment Intent, Type on Create Product, Name on Create Customer, and State/Province on Create Card
  • Customer ID left blank on Create Invoice and List Cards is now omitted rather than sent as an empty customer ID that Stripe rejects; the field is optional in both of those Stripe endpoints
  • Update Customer now reports a blank Customer ID as an error naming the field, instead of requesting an empty customer record from Stripe
  • Select Charge and Select Balance Transaction labels now show amounts in the smallest currency unit, correcting zero decimal currencies such as JPY and three decimal currencies such as KWD
  • Removed Card Number and CVC from Update Card, Product Caption from Create Product and Update Product, and Coupon from Create Subscription and Update Subscription, none of which were sent to Stripe

Reconfiguration notice: monetary inputs now take the smallest currency unit exactly as entered. Re-enter a fractional Amount on Create Payment Intent or Update Payment Intent as a whole number, and re-enter Balance on Create Customer or Update Customer and Unit Price on Create Price in the smallest currency unit, since these are no longer multiplied by 100.

Restructured action inputs into structured objects for an improved user experience.

  • Every list and search action groups Limit, Starting After, Ending Before, and Page into Pagination, with Fetch All left as a top level toggle on List Checkout Sessions and List Webhooks
  • Create Card and Update Card group their cardholder inputs into Billing Address and Name & Contact Information, and Create Customer and Update Customer group theirs into Address and Name & Contact Information
  • Create Payment Intent and Update Payment Intent group their optional inputs into Transfer Options and Additional Fields, and Confirm Payment Intent, Capture Payment Intent, and Update Invoice group theirs into Additional Fields

Monday (2026-08-26)

Grouped the Page Offset and Result Limit inputs on the List Boards action into a Pagination structured object; Fetch All stays a top-level toggle

Qualys (2026-08-26)

Initial release of Qualys component with VMDR asset management, vulnerability scanning, tag management, and remediation ticket tracking

Zoho (2026-08-21)

Updated the New and Updated CRM Leads, New and Updated CRM Contacts, and New and Updated Books Contacts polling triggers to filter records server-side by their last modified time, so each poll returns only records changed since the previous poll instead of the entire dataset, reducing API-credit consumption

HubSpot (2026-08-19)

Reworked the New and Updated Records and New and Updated Custom Records triggers for large data volumes and correct filtering:

  • Added an optional Look-back Date input across all polling triggers for performing an initial sync of records. The initial sync backfills every record created on or after the specified date, seeding each once and ignoring the field and visibility filters; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill
  • Added opt-in batching across all polling triggers, dispatching each changed record individually or in configured batches so a large backlog drains within one recurrence; enabling it changes the shape a downstream step receives
  • Added support for object types holding more than the 10,000 records a single HubSpot search returns, draining the remainder on later recurrences. A larger result set previously failed
  • Updated both triggers to always return both createdRecords and updatedRecords. A disabled Show New Records or Show Updated Records now yields an empty array where the key was previously absent
  • Updated Search Properties filters and filterGroups to restrict results instead of widening them. They were previously OR-combined with the trigger's date window, so configured filters returned matching records regardless of date
  • Updated Search Properties sorts to be ignored by these triggers; they now sort ascending by the object's creation property during the initial sync and its last-modified property on later recurrences, so a recurrence can resume where it left off
  • Fixed the New and Updated Custom Records trigger retrieving every record of the custom object type on each recurrence instead of only the changed ones. It now filters and sorts on hs_lastmodifieddate, so the custom object type must expose that property

Salesforce (2026-08-19)

Updated the New and Updated Records polling trigger:

  • Updated the trigger to carry unreported records forward to the next recurrence, so a backlog larger than Max Records To Fetch is no longer dropped and a bulk load stamping many records with one timestamp still drains; Max Records To Fetch now caps how many records are retrieved at a time rather than how many the trigger will ever report
  • Added an optional Look-back Date input for performing an initial sync of records. The initial sync backfills every record created on or after the specified date, seeding each once and ignoring the field and visibility filters; recurrences after the sync 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 so large backlogs drain in one recurrence; enabling it changes the shape a downstream step receives
  • Updated deleted-record reporting so a trigger that has not run in more than 15 days continues instead of failing, since Salesforce serves no more than 15 days of deletions, and so deletions at the edge of a window are reported on the next recurrence rather than skipped

Google Analytics - GA4 (2026-08-17)

Restructured list action inputs into structured objects and improved paging reliability:

  • Grouped the page and page-size inputs on List Accounts and List Properties into Pagination; Fetch All stays a top-level toggle
  • Fixed Fetch All on List Properties, and the properties dropdown, so the account filter is applied to every page rather than only the first
  • Fixed list actions, data sources, and the New and Updated Records trigger to return an empty result instead of erroring when no records match
  • Added output schemas to the List Accounts, List Properties, Get Property, Run Report, and Send Measurement Protocol Events actions for improved field mapping during configuration
  • Added inline action calling support across all actions for improved example output during configuration