Platform Connector Updates: Enhancements and Bug Fixes

Wrike

Enhancement

• We have renamed the “Modify User” action to “Update User” and updated the dropdown list for User-type custom fields to show only active users. Users can now update Wrike user records using a consistently named action and easily select from a list of active users. This will streamline the selection processes and ensure users only choose from relevant options.
• We have updated the “List Users” action to support additional query parameters and expanded output fields, including custom fields. Users can now retrieve a more complete set of user data when listing users in Wrike. This improves visibility and customization when managing user-related workflows.

Bug Fix

• The connector issue related to adding contacts with pending invites to the “Limited list of users” in contact-type custom fields has been successfully resolved. Users will now benefit from enhanced stability and reliability when using the New/Updated Task, New/Updated Folder, New/Updated Project, and Modify User triggers and actions in Wrike recipes. This improvement ensures that newly created or cloned recipes work seamlessly, offering greater efficiency in task management.

NetSuite SOAP

Bug Fix

• We’ve improved the connector to smartly manage select-type custom fields that initially lacked  picklist options by loading an empty picklist instead. This allows users to work with these fields smoothly, ensuring a more efficient process within the UI. 

IDP by Workato

Bug Fix

• The Process Document action has been updated to handle empty image files submitted for processing. Users can now submit empty images without generating an incorrect JSON output. Now, when empty images are submitted in the Process Document action, the output will correctly show null fields.
• We’ve implemented a retry mechanism and a dedicated prompt to handle refusal responses from OpenAI. If a second refusal occurs, the connector will now throw a meaningful error. Users now have clearer outcomes and better error handling when refusal responses are encountered. This improves transparency and reliability when processing sensitive inputs with OpenAI.

Trackvia

Enhancement

• We have introduced a new authentication method, “Multi-authentication,” which allows the use of long-lived Bearer API tokens, offering a more secure alternative to Basic Authentication.
• A new additional parameter for user_key has been introduced to the Connector’s connection fields. This will provide more flexibility and customization options for users. 
• The Connector has been updated to modify the User-Agent string by adding the Workato Job ID to requests to TrackVia. This will improve tracking and management of requests.

Okta

Enhancement

• The connection logic for supporting users with custom roles has been updated by introducing a fallback request that uses the okta.users.read scope. Users can now establish connections even if their role does not include the okta.logs.read scope. This improves flexibility in role-based access and simplifies setup for a wider range of Okta users.

Sorbet

Bug Fix

• We have added input validation to ensure the correct data type is used when processing file content. Users can now pass input parameters without triggering validation errors. This enhances reliability and prevents disruptions during runtime.

SFTP

Bug Fix

• The SFTP adapter has been updated to handle empty filenames when listing folders. Users can now list folders without encountering unexpected method errors. This ensures smoother and more stable file navigation in SFTP workflows.

Net

Bug Fix

• We have implemented improvements to address the Net::WriteTimeout error. Users can now execute network-dependent operations with reduced risk of timeouts.

OPA

Bug Fix

• The connection setup for OPA-enabled connectors has been updated by routing authentication token requests through the secure gateway tunnel using shared_account.secure_gateway_tunnel.presence. Users can now establish OPA-based connections with proper routing in place. This ensures that the authentication token request is now routed through OPA.

Shopify

Enhancement

• We have added support for Shopify’s new File Models in GraphQL and introduced actions for Create, Get, Search, Update, and Delete operations on files. We’ve also added support to Attach/Detach Files to Product Variants and Sort Files in a Product. Users can now manage product files using the latest Shopify model updates, with all new actions processed as long-running by default. These changes will help maintain seamless integration with Shopify and provide users with more flexibility in managing product files.

Bug Fix

• We have corrected the refunds output schema by embedding the transactions schema within it and deprecating transactions at the root level. Users can now work with a complete and accurate refund schema across multiple actions and triggers, including New order, Create order, and Search order (batch). This ensures data accuracy and enhances the developer experience when working with order-related flows.

Azure OpenAI, AI by Workato, and OpenAI

Enhancement

• A new “Analyse Image” action has been added across the Azure OpenAI, AI by Workato, and OpenAI connectors. This action accepts file contents (up to 20MB), file type (pdf, png, jpg, webp, gif), file name, and instruction. Users can now submit images or documents for analysis with detailed instructions, using flexible file type input. This provides a powerful and streamlined way to extract insights from visual content using AI.

Google Drive

Bug Fix

• We’ve introduced a fallback to dynamically adjust the chunk size during file uploads when Google Drive’s resumable upload protocol requires it. Users can now upload files from SFTP to Google Drive without encountering byte-size mismatch errors. This ensures smoother uploads and eliminates errors related to inconsistent chunk sizes.

Data Tables Connector

Enhancement

• We have removed the full filter description from the action descriptions in both the “Search records” action of the Data Tables connector and the “Search requests” action of the Workflow Apps connector. Users will now see cleaner and more concise descriptions when configuring these search actions. This change will make the action descriptions cleaner and easier to understand.
• New batch triggers have been added for detecting new or updated records in Data Tables. Users can now process data in batches rather than row by row. This improves performance and efficiency when working with large data sets.
• We’ve enabled output configuration in triggers, allowing column names to be shown instead of IDs. Users can now view and configure outputs in a more human-readable format. This enhances usability and makes it easier to work with trigger results.

Email by Workato

Bug Fix

• Enhanced the functionality of the Send Email action to ensure the username is clearly included in the email signature in both the test and production environments. Users will now see their name displayed in the email signature, leading to consistent communication across all environments.

HTTP Connector

Enhancement

• We have introduced a new content type option in the HTTP connector by splitting the JSON request body into “Raw JSON request body” and “JSON request body”. The new option supports schema builder and allows for conditional skip logic. Users can now apply formulas like skip directly when building a JSON payload using the visual schema. This update will provide more flexibility for customers using the HTTP connector and wishing to utilize our skip formula.

Bug Fix

• We’ve introduced a new content-type labeled “JSON” and renamed the existing option to “JSON (Raw)”. The new JSON option now supports the schema designer. Users can now build structured JSON request bodies with a visual interface, making it easier to configure and manage outgoing payloads. This enhances flexibility and usability when sending JSON requests through custom HTTP actions.

Workday

Bug Fix

• We have updated the schema generation logic in the Workday connector to ensure that XML attributes are now mapped into the JSON output, especially for complex objects like Organization. Additionally, we introduced a new configuration option in the Call Operation and Get Business Object actions called “Include descriptors in response”. Users can now control whether descriptors are included in the XML and JSON response by toggling this option. When enabled, the appropriate headers are automatically inserted, and the system behavior adjusts based on payload type. These changes ensure that all XML attributes are correctly mapped in the JSON output from the Workday Connector.

Microsoft Dynamics 365

Bug Fix

• We have added a fix to handle custom object names and field name conflicts when creating records in batch actions for API v8. Users can now create custom objects without encountering a 400 Bad Request error due to naming discrepancies. This ensures compatibility across different versions of Dynamics 365 and improves reliability in batch creation workflows.

Podio

Bug Fix

• We have deprecated the original updated_item paging trigger and introduced a new version, which uses a simplified approach to paging and avoids reliance on outdated cursors.This improvement enhances trigger stability, prevents re-fetching of historical events, and improves long-term reliability, especially in environments with strict data retention policies.

Zendesk

Bug Fix

• We have updated the “Comment Type” field in the Update Ticket action to correct a typo and improve dynamic field visibility. Users will now see the HTML Comment field displayed by default when the action loads, with “HTML Body” set as the default comment type. This streamlines the setup process and creates a more intuitive and error-free configuration experience.