Platform Connector – April 2026

Table of Contents

NetSuite REST

Enhancement

We’ve expanded the NetSuite REST connector with a suite of new asynchronous actions — Create Records, Update Records, Upsert Records, Delete Records, and Get Async Job Result — complete with dynamic list support. Users can supply a list of records and the connector will process them one by one, delivering a seamless single-batch experience. This addition brings greater flexibility and scalability to high-volume NetSuite workflows.

We’ve introduced a new Transform a Record action in the NetSuite REST connector, enabling users to convert an existing record into a different type — for example, transforming a sales order directly into an invoice. Users can execute record type conversions without leaving the connector. This streamlines complex NetSuite business processes and reduces the need for manual steps.

SharePoint

Enhancement

We’ve enhanced SharePoint connector actions to accept data pills in the Site URL field, allowing users to dynamically set the site at runtime rather than relying on static picklist selections. Users can define schemas via the schema designer when using dynamic values, and this capability is supported across all SharePoint connector actions. This unlocks more flexible, reusable recipes for multi-site SharePoint environments.

Bug Fix

We’ve enhanced folder and file name handling in the SharePoint connector to preserve naming consistency across all operations, including Get Permission Details and Delete a File or Folder actions. Users can expect accurate file and folder representation across SharePoint libraries.

Microsoft Teams

Enhancement

We’ve introduced a brand-new Microsoft Teams connector, bringing Teams messaging and collaboration workflows into the Workato automation ecosystem via the Microsoft Graph API. Users can authenticate via OAuth 2.0 auth code or client credentials grant, and take advantage of a rich set of actions including List Teams, Get Team, List Channels, Create Channel, Send Message, Reply to Message, Search Messages, Get User, and more. This opens up a wide range of automation possibilities for Teams-based collaboration workflows.

Greenhouse

Enhancement

We’ve added full v3 support to the Greenhouse connector, with new v3 actions and triggers, OAuth 2.0 enforcement for v3 operations, and API key authentication for legacy operations. Users are encouraged to migrate to a v3-based connection by August 15, 2026, ahead of the vendor’s deprecation of v1/v2 on August 30, 2026. Legacy v1 actions and triggers are marked as deprecated to guide users toward the updated experience.

We’ve improved the Greenhouse “On-Behalf-Of” functionality by enabling direct use of a connection-level User ID across both API key and OAuth flows. Users benefit from more reliable and efficient authentication — particularly for service users — with backward compatibility maintained for existing email-based API key connections. This reduces unnecessary API requests and strengthens the consistency of Greenhouse integrations.

Bug Fix

We’ve updated the Greenhouse Sandbox environment connection property to align with Greenhouse’s current Harvest architecture, where Sandbox and Production environments now share the same routing behavior. This streamlines connection setup and keeps configurations aligned with the latest platform experience.

Google People

Enhancement

We’ve expanded the Google People connector with Custom OAuth 2.0 profile support, giving users the flexibility to authenticate with their own OAuth client credentials instead of Workato’s default OAuth app. Users gain greater control over their authentication setup and can align the connector with their organization’s OAuth configuration. This brings Google People in line with the broader Custom OAuth experience available across our connector ecosystem.

Jira Data Center

Enhancement

We’ve introduced a new OAuth 2.0 (Data Center) authentication type for the Jira connector, enabling customers to authenticate to self-hosted Jira DC instances using their own Jira instance as the authorization server. Users register an Application Link in Jira DC and provide the resulting Client ID and Client Secret in the connector’s advanced settings. This gives self-hosted Jira DC customers a secure, standards-based OAuth authentication path tailored to their environment.

Gmail

Enhancement

We’ve introduced a new Get Email or Draft by ID action in the Gmail connector, enabling users to fetch a specific email or draft directly using its ID. Users can retrieve exactly the message they need without searching or listing through results. This adds a fast, precise retrieval option to Gmail-based automation workflows.

Confluence

Enhancement

We’ve introduced a new Create Task (v2) action in the Confluence connector, built on Atlassian’s v2 REST API. Users should migrate to Create Task v2, as the legacy v1-based action relied on the /wiki/rest/api/content endpoint retired by Atlassian on April 30, 2025. This ensures continued, reliable task creation within Confluence-based workflows.

Workfront

Enhancement

We’ve introduced filter and filter-group support in the Workfront webhook trigger for event subscriptions, enabling users to narrow down which events trigger their recipes. Users gain more precise control over event handling, reducing noise and focusing automation on exactly the events that matter. This makes Workfront-driven workflows more targeted and efficient.

Bug Fix

We’ve enhanced the New Task Created or Updated trigger in Workfront with improved timestamp handling and UTC normalization support. This provides more precise trigger progression and helps workflows stay accurately synchronized.

Microsoft Graph

Bug Fix

We’ve enhanced Microsoft Graph connector resiliency with automatic token refresh handling during API operations, helping ensure uninterrupted execution across Microsoft Graph actions.

PGP

Enhancement

We’ve improved the “Sign a Message” action on the PGP connector to produce a clear-signed, human-readable PGP message where the original content remains visible without requiring GPG. Users can now fulfill PGP message signing requirements — such as payment file verification — with a properly signed output. A new ASCII armor toggle in the action’s input schema gives users additional control over the signing output format.

Zendesk

Enhancement

We’ve updated the Zendesk test call to use a universally accessible endpoint, ensuring successful connections regardless of the user’s Zendesk role. Users connecting via a Service Account no longer need Agent-level access to complete the connection test. This makes onboarding and connection management smoother for a wider range of Zendesk user types.

Workday

Enhancement

We’ve strengthened Workday triggers to handle scheduled maintenance windows gracefully, preventing unnecessary recipe stoppages during planned downtime. Users can rely on their recipes to resume naturally after maintenance rather than requiring manual intervention. This improves the resilience and reliability of Workday-based automation workflows.

Bug Fix

We’ve enhanced Workday output schema generation to provide consistent descriptor attribute mapping — including Job Family Reference descriptors in the Get Workers action — making datapills more readily available for downstream recipe steps.

Intercom

Bug Fix

We’ve enhanced pagination handling in Intercom connector triggers to provide consistent event sequencing and reliable polling behavior, including improved resume-point tracking and deduplication support.

AWS Secret Manager

Bug Fix

We’ve streamlined the connection disconnect experience for AWS Secrets Manager integrations, allowing teams to manage connection lifecycles smoothly even as underlying secrets change over time.

Shopify

Bug Fix

We’ve optimized the Shopify New Updated Order trigger with a balanced default polling page size of 50 to support stable, consistent trigger execution for order-based workflows.

SAP SuccessFactors

Bug Fix

We’ve enhanced the SAP SuccessFactors “Upsert Background_Languages” action to align numeric key field handling with SuccessFactors OData API expectations, improving compatibility for HR workflow automations.

Data Tables

Bug Fix

We’ve enhanced the Data Tables adapter with expanded tracing support across WorkatoDb calls, improving observability and usage reporting for Data Tables operations.

SAP OData

Bug Fix

We’ve enhanced URL handling in the SAP OData connector to preserve entity set naming consistency across API calls, improving compatibility for services such as HCM_LEAVE_REQ_CREATE_SRV while maintaining backward compatibility for existing integrations.

Was this post useful?

Get the best of Workato straight to your inbox.

Table of Contents