Platform Connector Updates: Enhancements and Bug Fixes

SAP SuccessFactors

Enhancement

• Support for OData v4 APIs in the SAP SuccessFactors OData connector has been added. A version picker is now available at the connection level, allowing users to choose between V2 and V4. Users can now integrate with the latest SuccessFactors APIs and access more entities in their workflows. This provides increased flexibility and expanded coverage and ensures compatibility with SAP’s evolving API standards.

Bug Fix

• We’ve enhanced the New/Updated batch trigger to ensure all input fields are passed when using OData v4. Users can now build workflows with complete field support and seamless datapill logging. This update strengthens batch trigger functionality and ensures consistent behavior when working with SAP SuccessFactors records.

Workday

Bug Fix

• A retry fallback to the “Scheduled report in Workday using WQL trigger” has been added to handle cases where requests with offsets require an initial offset-free request. Users can now process batches of records more reliably, even when the trigger is resumed with a stored offset. This enhancement ensures uninterrupted and efficient data polling from Workday scheduled reports.

• We have updated the XML payload logic in the “Submit Settlement Run” action to handle boolean values. Users can now submit settlement runs without validation errors during action execution. This improvement ensures accuracy and reliability in financial operations built on Workday integrations.

Netsuite

Enhancement

• The NetSuite SOAP connector has been enhanced by adding XML support in custom actions, enabling the execution of custom SOAP requests. Users can now build and send fully customized SOAP payloads tailored to their NetSuite implementations. This provides greater flexibility for advanced NetSuite integrations and supports more specialized use cases.

Bug Fix

• We have refined the XML Request Builder in custom actions to use a more flexible, namespace-aware XPath for parsing the envelope, body, and header. Users can now build custom SOAP requests with dynamic XML structures and token-based authentication more reliably. Additionally, we’ve renamed the response type label from “Raw JSON response” to “Raw response” to better reflect support for both XML and JSON. This improves compatibility, reduces confusion, and enhances the developer experience when working with complex SOAP payloads.

IDP by Workato

Enhancement

• The daily action limit from the IDP by Workato connector has been removed. Users will no longer see datapills indicating remaining actions. Instead, internal rate limits of 60 requests per minute per workspace have been introduced to ensure performance and stability. Users can now run IDP workflows without tracking usage caps, while internal telemetry monitors pages and token usage in the background. This update provides a smoother, unrestricted experience while maintaining system reliability and transparency.

AI by Workato

Enhancement

• We’ve removed the daily action limit for AI by Workato and introduced internal rate limiting of 60 requests per minute per workspace to maintain performance and service integrity. In addition, usage of AI by Workato is now counted as a business action, and internal telemetry has been added to track token consumption. Users can now take full advantage of AI features without manual tracking or action caps, while usage remains visible and controlled. This update provides a more seamless, scalable, and transparent AI experience across integrations.

Jira

Enhancement

• We’ve upgraded the search endpoints in Jira to ensure compatibility ahead of the May 1, 2025 deprecation timeline. Affected triggers such as New/Updated Issue, New Issue Priority, and bulk/export triggers have been migrated, along with actions like Search Issues and Search Issues by JQL. Users can now continue to use Jira actions and triggers without any impact to existing workflows. This update ensures continued platform compatibility and a smooth transition ahead of Jira’s API changes.

Bug Fix

• Support for the clear formula in the Update Issue action has been added, allowing users to remove existing field values directly. Users can now confidently clear data fields using the clear formula, enhancing update flexibility. This improves control and precision when managing issue updates.
• We’ve resolved errors related to OAuth connection failures in Jira, including 403 Forbidden messages and dropped connections. Users can now successfully establish and maintain OAuth connections without disruption. This ensures a stable, secure integration experience for Jira authentication workflows.

Okta

Enhancement

• A new capability to the Okta connector has been added that allows for the reset of all Multi-Factor Authentication (MFA) factors for a specified user. Users can now easily reset MFA configurations without manual intervention using this new action. This streamlines account recovery and simplifies identity management workflows.

Salesforce

Enhancement

• We’ve upgraded the Salesforce connector’s REST API version from v59.0 to v62.0. Users can now access the latest Salesforce features and improvements directly through the connector. This update ensures long-term compatibility and alignment with Salesforce’s most current standards.

EDI

Enhancement

• Introduced a series of enhancements to the EDI connector, including manual configuration for transaction types, human-readable picklist values (e.g., “850 Purchase Order”), clearer schema segment names, and a streamlined UI with deprecated actions labeled as “Beta” and unused parameters removed. Users can now configure and parse EDI messages more intuitively and manage transactions with clearer schema visibility. These enhancements offer a cleaner interface, better control, and a more approachable EDI integration experience.

Bug Fix

• The Parse EDI action has been improved to ensure full schema visibility, including nested objects, when “Ignore null values” is set to “No”. Users can now view and work with complete EDI transaction structures in the data tree. This ensures consistency, improves transparency, and supports more robust EDI workflows.

Bill

Enhancement

• We’ve added a new “Send Invoice” action to the Financial Operations Platform for Businesses & Firms connector. Users can now send invoices directly from recipes, expanding automation capabilities for billing workflows. This enhancement improves operational efficiency and streamlines financial processes.

Xero

Enhancement

• A new “Tax type code” field has been introduced and refined how tax type name and code are handled in the Create Invoice action. Users can now pass a tax type code directly, reducing the number of API calls required when creating invoices with many line items. This update helps prevent rate-limit issues, enhances performance, and offers greater control when working with Xero’s API.

DB Connectors

Enhancement

• We have updated our database connectors—SQL Server, MySQL, Google BigQuery, Snowflake, Redshift, and PostgreSQL—by removing previously introduced usage logs to enhance performance and privacy. Users will now experience improved performance without usage tracking overhead. This change reflects ongoing efforts to streamline connector behavior while safeguarding data activity.
• Usage data logging for specific actions has been added, including insert_row and the now-deprecated sync_objects_to_snowflake action. Users can now gain better insight into how frequently key actions are being used and the data volumes processed. This provides improved visibility and monitoring capabilities for operational analytics.

HubSpot

Enhancement

• We’ve introduced a new input field in the “Export object data” action that allows users to export up to 1000 associated records per association column, per row. Users can now enable this by setting the “overrideAssociatedObjectsPerDefinitionPerRowLimit” field to true, giving them more control over exported data. This enhancement aligns with HubSpot’s API improvements and gives users greater flexibility in managing record associations.

PGP

Enhancement

• Version configuration support during the PGP connector’s connection setup has been added. Users can now specify the desired PGP version at the time of connection, allowing for better control and compatibility across deployments. This update provides greater flexibility and ensures smoother version alignment in encryption workflows.

OneDrive

Bug Fix

• We’ve enhanced the connector’s file download behavior by implementing manual redirect handling when downloading files from Microsoft OneDrive personal accounts. This ensures stable and secure cross-cloud file transfers, even when authorization tokens are involved in redirects.

Sage Intacct

Bug Fix

• Date parsing in the New/Updated Projects trigger and Search Project action has been improved by adding support for the “YYYY/MM/DD” format. Users will now receive values for Begin Date and End Date fields in their recipes. This fix improves data accuracy and consistency when managing project records in Sage Intacct.

Google Drive

Bug Fix

• We have updated the streaming upload action to handle content size validation, preventing errors related to invalid UTF-8 byte sequences. Users can now upload files using streaming without encountering encoding issues. This fix improves stability and compatibility when handling diverse file types and content encodings.

AWS Lambda

Bug Fix

• We’ve resolved a 403 Forbidden error when connecting to AWS Lambda using IAM Roles in non-default government regions, including us-gov-west-1. Users can now establish connections to AWS Lambda seamlessly across all supported regions. This ensures broader regional support and consistent access to Lambda functions in secure environments.

SharePoint

Bug Fix

• Multi-select picklist support for fields of type SP.FieldMultiChoice in SharePoint list actions has been added. Users can now assign multiple values to multi-select fields when adding, creating, or updating rows. This enhancement improves data handling for SharePoint lists and supports more dynamic list configurations.

Facebook Leads

Bug Fix

• We have added a toggle field to the New Lead Ad Form Response trigger, allowing users to either select a page from the dropdown (existing functionality) or input a specific Page ID (new functionality). Users can now monitor any owned Facebook page, even if it’s not listed in the first 25 dropdown options. This improvement ensures broader page coverage and a more seamless setup experience.

Oracle Fusion

Bug Fix

• We’ve removed the Supplier object from the New/Updated Record and New/Updated Record (batch) triggers due to its lack of a “last modified” field. Users will now see a new supported list of available objects when configuring triggers. This update improves clarity and prevents confusion when building Oracle Fusion recipes.

BambooHR

Bug Fix

• The New/Updated Employee trigger in BambooHR has been updated to include the preferredName field and improved handling of restricted list-type fields. Users can now access a complete set of employee data, even when working with accounts that have limited access. This ensures smoother operation and improved visibility across HR records.

Outlook

Bug Fix

• The New Event trigger has been updated to eliminate duplicate jobs for the same calendar event by excluding ChangeKey values from deduplication logic. Users will now see a single job triggered per event as intended. This improves calendar accuracy and ensures that only new events generate actions in user workflows.