Platform Connector Updates: Enhancements and Bug Fixes

EDI tools by Workato

General Availability

• After a series of user experience improvements across the board, the EDI Tools connector is now out of Beta. Both Parse EDI and Generate EDI actions can be configured either by providing samples or by selecting the EDI format, version, and transaction type. Transaction and segment names are now identified not only by their IDs but also by clear, descriptive labels. Last but not least, the connector’s stability has been significantly enhanced, especially when processing large EDI transactions.

Wrike

Enhancement

• We’ve added DataHub APIs to the main Wrike connector, enabling users to create, update, and delete records, as well as create databases and fields. Users can now manage Wrike databases more flexibly and efficiently within their automations. This enhancement streamlines data management and expands the capabilities of Wrike integrations.

HubSpot

Enhancement

• We’ve expanded the selection of available scopes in HubSpot connection settings. This update empowers users to leverage more HubSpot features via custom actions. Meanwhile, admins using Custom OAuth profile for HubSpot have more options for a secure setup of the connection

Jira

Enhancement

• We’ve improved the search endpoints migration in Jira by adding a new ‘reconcile issue’ input parameter to the ‘search issues’ and ‘search issues by JQL’ functions, ensuring read-after-write consistency when needed. Users can now configure read-after-write consistency for their searches. These enhancements deliver more reliable search results, improving the overall Jira integration experience.

• We’ve improved the search endpoints migration in Jira by adding a new ‘reconcile issue’ input parameter to the ‘search issues’ and ‘search issues by JQL’ functions, ensuring read-after-write consistency when needed. Additionally, unbounded JQL queries are now restricted, with clear error messaging and updated function hints. Users can now configure read-after-write consistency for their searches and receive immediate feedback if an unbounded JQL query is provided. Benefit: These enhancements deliver more reliable search results and clearer guidance, improving the overall Jira integration experience.

S3

Enhancement

• We’ve improved clarity in the S3 connector by renaming the titles, subtitles, descriptions, and hints for the two “Upload File” actions (streaming and non-streaming). Users can now more easily distinguish between file upload options. This enhancement delivers a clearer, more intuitive user experience when uploading files to S3.

QuickBooks

Enhancement

• We’ve added CreateTime and LastUpdatedTime filters to the Search Vendors action for more precise Vendors data retrieval

Facebook Lead Ads

Bug Fix

• We’ve updated the Facebook Lead Ads “New Ads” trigger to all pages are returned efficiently without the need for costly pagination. Users can now monitor and capture leads from all their Facebook pages more reliably and with less setup effort. This improvement streamlines lead collection and expands coverage, making campaign management easier and more effective.

AI by Workato

Bug Fix

• We’ve resolved an issue in the ‘Classify text into Severity’ action where categorization would fail if the list of categories contained numbers. Users can now reliably classify text into categories, even when those categories include numeric values. This fix ensures more robust and accurate text classification for automation and analytics workflows.

NetSuite SOAP

Bug Fix

• We’ve corrected the XML namespaces used in the Sales Team array for the Create Customer action in NetSuite. Users can now successfully create new customers in NetSuite when a Sales Team employee is included, such as when an opportunity is won in Salesforce. This fix enables seamless customer creation workflows, improving integration reliability between Salesforce and NetSuite.

Confluent Cloud

Bug Fix

• We’ve improved Avro schema validation in Confluent Cloud by adjusting the schema parser to handle null fields correctly, ensuring that null fields are defined as the first type. Users can now set up and run recipes in production environments with Avro schemas that include null fields, without encountering validation errors. Benefit: This update ensures consistent and reliable schema validation across all environments, streamlining deployment and reducing setup friction.

Data tables

Bug Fix

• We’ve updated the ‘Update Records (Batch)’ action in Data tables so that fields previously marked as required are now optional during batch updates. Users can now update records without being prompted to fill in unnecessary mandatory fields. This change streamlines the update process, making it more intuitive and efficient for users managing large datasets.

Email by Workato

Bug Fix

• We’ve improved the email footer logic to display usernames based on the environment context. In production, the footer now shows “workspace name” || “username”, while in non-production environments, it displays “workspace name (environment type)” || “username (environment type)”. Users can now clearly distinguish between production and non-production email notifications. This enhancement reduces confusion for clients and ensures greater clarity in email communications.

Mailchimp

Bug Fix

• We’ve updated the output schema for the “Search Subscribers” action in Mailchimp to match the latest API documentation, adding new fields (including contact_id) and deprecating renamed ones. Users can now access all necessary subscriber fields in their recipes, ensuring downstream actions have the data they need.

Outreach

Bug Fix

• We’ve updated the Outreach connector so that the First Name, Last Name, and Emails fields are now optional in the Create Prospect action, aligning with Outreach’s API documentation. Users can now create prospects without being required to fill in these fields, allowing for more flexible prospect creation. This update simplifies workflows and ensures compliance with Outreach’s latest standards.