NetSuite REST
Enhancement
We’ve expanded the NetSuite REST connector with five new polling triggers, split by record type: standard, classification, and custom. Custom-record triggers handle NetSuite’s separate date fields and fall back to internal ID when needed. All triggers support user-configurable filters layered on top of the built-in date/ID condition, and polling is resilient to REST API rate limits. Users can build precise, event-driven NetSuite automations with full control over which records fire their workflows.
We’ve also expanded record coverage to include 87 additional record types, with fully dynamic picklist values. Users migrating from NetSuite SOAP to REST gain access to a much broader range of records in a single connector, making the migration path faster and more complete.
We’ve introduced a new Updated Records trigger for NetSuite REST, enabling workflows that respond specifically to record modifications. Users can create distinct triggers for different record types, making event-driven automation more flexible across a wider range of NetSuite use cases.
SAP RFC
Enhancement
We’ve enhanced the SAP RFC connector’s New IDoc trigger with a configurable schema refresh option. Users can tune the trigger to reuse a cached schema across IDocs rather than re-resolving it on every message, substantially reducing per-message processing overhead for large batch runs. This is a meaningful performance improvement for high-volume IDoc flows.
We’ve also strengthened logging robustness for large payloads processed under TRACE logging and for error handling during SAP JCo API context extraction. The connector now detects both conditions early and emits a clear warning. Users working with complex SAP RFC scenarios gain a more transparent and reliable debugging experience.
Microsoft Word
Enhancement
We’ve introduced a brand-new Microsoft Word connector. Users can read, write, and manage Word documents — including comments and tracked changes — stored in OneDrive and SharePoint, all authenticated via OAuth 2.0. The connector supports MIME-validated file resolution, robust handling of non-standard SharePoint document part naming, and fully internationalized labels, hints, and error messages. All action inputs and outputs use named schemas, making document automation straightforward to build and maintain.
QuickBooks
Enhancement
We’ve added an Advanced Settings section to the QuickBooks connection configuration, featuring a Scopes dropdown for opting into additional OAuth scopes. The first advanced scope available is Custom field definitions (read), unlocking access to QuickBooks custom field metadata. Users who rely on custom fields in their financial workflows can activate this scope at connection setup for deeper, more complete data access.
We’ve also introduced three new Expenses actions: Search expenses (batch), Get expense details, and Get account details. Users can build richer financial workflows that pull expense data directly into their automations, keeping financial records in sync across systems without manual lookups.
Sage Intacct
Enhancement
We’ve updated the Sage Intacct connector to align with Sage Intacct’s latest API credential requirements: Sender ID and Sender Password are now required fields for all new connections. Users setting up new connections are guided to include their own customer-owned credentials upfront, ensuring smooth and compliant authentication from the start. Existing connections with credentials already entered continue to work without any changes needed. For connections that require an update, please complete this before July 13th, 2026.
SAP Concur
Enhancement
We’ve upgraded four SAP Concur expense actions to the v4 API, aligning Workato with SAP Concur’s latest capabilities. The new v4 actions — get_expense_types_v4, get_payment_types_v4, get_attendee_types_v4, and get_expense_group_configuration_v4 — require a userID input and provide access to the modern Concur API feature set. The prior v1/v2 actions remain available through June, giving teams time to transition their workflows at their own pace.
We’ve also updated the SAP Concur connector to preserve the exact field ID casing returned by the Concur API during user provisioning. Users can rely on accurate and consistent field mapping when provisioning SAP Concur users, ensuring successful outcomes for instances using standard camelCase field names.
Google BigQuery
Enhancement
We’ve extended the Google BigQuery connector with On-Prem Agent (OPA) support, making it accessible for BigQuery instances reachable only through on-premises networks. Users with private or hybrid cloud environments can integrate BigQuery into their Workato workflows without requiring direct internet exposure — expanding the connector’s reach to regulated industries and enterprise architectures where private-network connectivity is a requirement.
Data Tables
Enhancement
We’ve added a new Upsert records batch action to the Data Tables connector, enabling mixed create-and-update operations in a single step. Users can streamline data synchronization workflows by letting one action intelligently handle both new and existing records, reducing recipe complexity and improving efficiency for data management use cases.
OpenAI
Enhancement
We’ve updated the OpenAI connector to fully support GPT-5. GPT-5 has been added to the model selection dropdown, eliminating the need for manual model name entry. The Temperature field — required for GPT-5 compatibility — is now available across all relevant actions, including Send messages to OpenAI models, Summarize text, Parse text V2, Categorize text, Translate text, Draft email, Analyze text, and Analyze document. Two new parameters, verbosity and reasoning effort, have also been introduced for the Send messages to OpenAI models action, giving users greater control over GPT-5 output behavior. Additionally, the Temperature setting is retained between uses, reducing repetitive configuration and making complex AI workflows faster to build.
SharePoint
Bug Fix
We’ve strengthened the SharePoint trigger to reliably respect runtime updates to Data Table values. The trigger issues a fresh token fetch whenever the serverRelativeUrl value changes, dynamically picking up the updated path on subsequent polling intervals. Users can update their SharePoint folder targets at runtime without duplicating recipes, making dynamic multi-folder automation straightforward and maintenance-free.
NetSuite SOAP
Bug Fix
We’ve strengthened the OAuth nonce generation in the NetSuite SOAP connector to guarantee that every authentication nonce is always at least 6 characters long. This eliminates a class of intermittent authentication errors that could affect high-volume customers during periods of rapid sequential requests. Users running automated data flows between Salesforce and NetSuite — particularly for Time Entry and Sales Order records — can operate with greater confidence in connection stability.
Greenhouse
Bug Fix
We’ve improved payload handling for the Greenhouse update job, update application, and update candidate actions by ensuring the keyed_custom_fields property is always included in the request. Users can update Greenhouse records reliably and consistently.
We’ve also strengthened the Greenhouse New Event (real-time) trigger to work seamlessly with v3 OAuth connections. Schema generation has been aligned with the Harvest v3 API and legacy webhook payloads, and the v3 write conversion for currency and range fields has been improved. Users can configure the New Event real-time trigger with a v3 OAuth connection and receive a correctly generated webhook URL for full real-time event processing.
Workday
Bug Fix
We’ve improved error prioritization in the Workday connector’s trigger processing logic, ensuring the most specific and actionable error is surfaced.. Users processing large job backlogs — including scenarios where a trigger was paused during maintenance and restarted — can rely on smooth, uninterrupted processing.
We’ve also improved OAuth2 refresh token error handling in the Workday REST connector. When an outdated or malformed refresh token is encountered, the connector raises it as an explicit Unauthorized response, providing clear and actionable visibility. Users running Workato Genie skills backed by the Workday REST connector benefit from transparent error reporting and a straightforward path to re-authentication.
SAP OData
Bug Fix
We’ve strengthened the SAP OData connector’s OAuth 2.0 Authorization Code flow to seamlessly include the sap-client parameter in the authorization URL. Users connecting to multi-client SAP environments can be confident that authentication always targets the correct, configured SAP client.
Jira
Bug Fix
We’ve improved the Jira connector’s token refresh behavior for the New/Updated issue trigger. The trigger proactively initiates an authentication verification path on successful responses from anonymous search endpoints, allowing it to re-authenticate before any downstream authentication failure can occur. Users can rely on their Jira polling triggers to run continuously and pick up new jobs without interruption.
Salesforce
Bug Fix
We’ve updated the Salesforce Search records in bulk using SOQL query (API 2.0) action to return a well-formed output when a query matches zero records. Users building workflows that handle empty result sets receive a consistent, processable response that clearly indicates a successful operation with zero records, eliminating the need for special-case error handling.
Salesforce Marketing Cloud
Bug Fix
We’ve strengthened the Salesforce Marketing Cloud connector’s custom action to honor the Content-Type header specified by users. When a custom action specifies application/x-www-form-urlencoded, the request is sent with that content type as intended, while defaulting to application/json when no Content-Type is explicitly configured. Users building custom Marketing Cloud integrations can trust that their request format is faithfully respected.
Zoom
Bug Fix
The stability of Zoom connections has been improved to maintain their authenticated state across token refresh cycles. Connections remain active when recipes start or stop, and teams using Zoom in automated workflows can operate with confidence that their integrations stay connected.
Azure Blob Storage
Bug Fix
We’ve improved upload performance for large files to Azure Blob Storage by adopting time-based checkpointing, consistent with the approach used by other Workato file connectors such as Google Drive. Users transferring large files — including 1 GB+ datasets — experience substantially faster upload times. This improvement is especially valuable for data migration scenarios into Snowflake or SQL Server, where large-volume transfers are common.
IDP
Bug Fix
We’ve strengthened the IDP connector’s Edit Schema flow to preserve schema field descriptions when a schema is updated. Users who have documented their schema fields can update their schemas freely, knowing their field descriptions are retained and do not need to be re-entered after each change.
Confluence
Bug Fix
We’ve improved the default OAuth scopes configuration for the Confluence connector to ensure that POST/content requests are handled correctly for Confluence Data Center. Users with Confluence admin permissions can create and update content reliably, making Confluence automation dependable for all appropriately permissioned accounts.
Workato EDI
Enhancement
We’ve expanded the Workato EDI Search record action with a new createdAtEnd property, enabling date-range-based record retrieval. Users can define both a start and end boundary for their EDI record searches, making it straightforward to query records within specific time windows and build more precise EDI data workflows.