Page cover

Boston 4.6.0

📅 Release Date: July 22, 2025 - 📅 Next Release Date: August 13, 2025

Release Summary

Autom Mate 4.6.0 “Boston” is a landmark release that fuses AI-native capabilities with operational robustness to redefine the automation experience.

This version introduces Autom Mate’s first generation of AI Agent features, enabling users to build, test, and deploy conversational agents with real-time chat, agent-specific settings, and Playground-based simulations. Bi-directional agent integration empowers workflows with dynamic data exchange and context-aware automation execution — bridging human intent and system action like never before.

On the platform side, real-time validation of actions, flow-wide error detection, and custom action version control give developers instant feedback and safer debugging tools. The addition of Microsoft Account Login streamlines enterprise access, while UI enhancements such as collapsible panels, improved variable visibility, and a centralized Errors screen elevate daily usability.

Critical system issues — including Base64 parsing failures, broken credential references, metadata residue in conditional logic, layout-breaking overflows, and inconsistent pagination — have been comprehensively resolved. These fixes improve system integrity, especially under enterprise-scale load.

Performance improvements span both backend logic and frontend rendering, with notable speed gains in large Autom lists and flow construction. From AI trials to action disablement, from alert management to help menu redesign — Autom Mate 4.6.0 offers a faster, smarter, and more secure platform for automation creators.

With this release, Autom Mate is not just stable and scalable — it’s intelligently extensible.

Highlights of this Release

🅱️ Bug Fixes

  • Base64 Decode Not Handling Unpadded Inputs – The decoder now accepts Base64 strings without = padding and fails gracefully with informative errors when input is invalid.

  • If Condition variableType Bug & Missing Variables – Residual metadata is now removed during type conversion, resolving hidden errors when switching from boolean to string conditions.

  • Datatable Format Strips Static Values from Variables – Static content like [New] is now retained when combined with variables (e.g., ##xVariable##[New]).

  • Deleted Credentials Still Functional in Automs – Automs now fail securely if a referenced credential has been deleted, preventing unauthorized or unintended access.

  • OAuth Credential Name Lock Bug – Incomplete OAuth creation attempts no longer reserve credential names or leave behind invalid records.

  • Overflow in Alert and Actioneer Profile Descriptions – Long, unbroken text now wraps properly, and a character limit has been introduced to prevent layout breakage.

  • Pagination Input Triggers Premature Page Load – Page now navigates only after pressing Enter or clicking the Go button, not after each keystroke.

  • System Action Fields Break \n Format on Update – Multiline text fields now preserve newline structure consistently during create and update operations.

  • JSON Unmarshal Error in Email Send Action (Repeat Loop) – Email attachments now retain proper structure across all loop iterations, preventing type mismatch errors.

  • MateDrive Attachment Parsing Fix – Email Send action now correctly handles mate:/ paths in the attachments field without throwing string parsing errors.

🛠️ Enhancement

  • Autom Screen Performance Optimization – 20% faster load and interaction speed in large-scale automation flows.

  • Quick Access in Autom List – Navigate frequently used Automs faster from the list view.

  • Improved Help Menu – Access more in-app resources including FAQs, how-tos, and documentation.

  • Error Configuration Tab – Simplified management of how and when errors are captured and reported.

  • Action Disable Option – Temporarily disable specific actions or groups to support safer testing.

  • Alert Management Simplification – Enhanced alert configuration tools for easier monitoring setup.

  • Disable Non-Dev Mode Features – Prevents any interaction or modification when Dev Mode is off, enabling a secure, read-only preview experience.

  • Data table Library Model View Changes – Introduces a reusable and responsive DataTable UI with ellipsis-based overflow handling, tooltips for hidden data, and full-screen mode support.

  • Disable SSL Configuration UI and Redirect Users to Support – The SSL section in settings is now disabled and guides users to submit a support request via Xurrent.

  • Dev Mode Switch: Toggle Dotted Background in Autom Builder – Canvas background now adapts between clean and dotted views based on Dev Mode state.

  • Remove "Delete" Option from Autom Context Menu – Streamlines individual item menus and reduces accidental deletion risk.

  • License-Aware Import Validation – Imports now trigger validation checks for license-restricted libraries, preventing unauthorized action usage.

  • Removal of Obsolete Language Flag – The unused language attribute in Autom metadata has been removed to simplify the system structure and improve data integrity.

  • Default Panel Collapsing on Autom Load – The Autom Flow screen now loads with both side panels (Library and Configuration Form) collapsed, offering a cleaner and distraction-free workspace.

  • Improved Variable Icon Visibility – Variable icons are now visible in the library and Data Manager for better navigation and usability.

  • Variable Tab in Action Panel – Adds a dedicated tab for managing variables separately from actions, improving clarity and workflow organization.

  • Live Error Indicator on Autom Screen – Displays the current number of validation errors and offers direct navigation to the Errors panel for faster troubleshooting.

  • Errors Screen UI Design – A centralized validation screen that displays categorized flow issues, supports direct navigation, and updates in real time.

  • Monitoring Logs: Action Redirect Button – A redirect button has been added to each log entry in Monitoring Logs, allowing users to jump directly to the related action within the Autom Builder. This enhancement significantly improves debugging efficiency by reducing time spent searching for the source of issues.

  • Custom Action Version Sync – Updating a custom action version now reflects immediately in both the flow UI and JSON definition, ensuring runtime consistency.

  • Custom Action Version Switch UI – Enables developers to switch between available custom action versions directly from the Autom Builder interface with real-time feedback.

✨ New Features

  • Bi-Directional AI Agent Integration – Enables two-way data exchange between AI agents and Autom Mate for dynamic workflow automation.

  • Agent Details Panel – View and configure agent credentials, settings, and behaviors from a central UI.

  • AI Agent Builder – Create, edit, and manage AI agents without affecting core Autom flows.

  • Playground for Testing AI Agents – Simulate conversations and test agent behaviors in a safe, isolated environment.

  • Real-Time Chat Integration – Interact with AI agents using live chat interfaces embedded in the platform.

  • Chat History Storage – Preserve agent interaction history for context-aware automation.

  • AI Agent List Interface – Users can now view and manage AI Agents from a centralized, responsive listing page, featuring real-time data, pagination, and secure access.

  • Deploy AI Agent from Details Page – Users can now deploy their AI Agent configurations directly from the Agent Details screen with a single click.

  • Autom Creation from AI Agents – AI Agents can now dynamically create new automation flows inside Autom Mate, accelerating agent-based task orchestration.

  • AI Agent 30-Day Trial Enablement – Allows users to activate and monitor a time-limited trial of AI Agent functionality, with clear expiration visibility and sales engagement CTA.

  • Real-Time Action Validation – Every newly added action is now validated instantly. Any errors (missing required fields, incorrect values) are listed in the Errors panel and visually marked in the flow editor.

  • Custom Action Version Listing Service – Backend service to fetch all downloaded versions of a custom action, enabling version switching in developer mode.

  • Initial Flow Validation – All actions in a flow are automatically validated when the flow is opened, helping identify issues early.

  • Microsoft Account Login – Users can now securely log in with their Microsoft work, school, or personal accounts.

  • Microsoft Sign-In Button on Login Screen – A new “Sign in with Microsoft” button has been added to the login screen, allowing users to log in with their Microsoft accounts through OAuth 2.0. This improves accessibility and streamlines login for enterprise users.

  • Library & Actions Integration in Flow - The redesigned Library & Actions module has been integrated into the Flow screen with full drag-and-drop support, while preserving all existing functionalities.

  • Quick Add (+) Action Insertion - Clicking the Quick Add (+) button now opens the Library, allowing actions to be selected and instantly placed into the flow, with contextual buttons added inside Condition modules.

Detailed Version

  • Base64 Decode Not Handling Unpadded Inputs Previously, Base64 decoding in Autom Mate required manual padding (=) to function correctly. Valid but unpadded Base64 strings—such as NG1lLnFhL0NpLzk4MDMxMzM—would fail silently or return non-informative errors. With this fix, the decoder now automatically handles padding internally and ensures accurate decoding for all valid Base64 formats. Additionally, when truly invalid input is provided, the system returns a clear, context-aware error message to aid debugging. Unit tests have been added to verify padded and unpadded input handling, and no regressions were observed in dependent modules.

  • If Condition variableType Bug & Missing Variables A bug was causing conditions to retain outdated metadata when the field type was switched from boolean to string—specifically, the variableType: "boolean" key would remain in the condition object even after type change. This led to unexpected runtime behavior and missing variable mappings. The issue typically occurred when a condition was created with a boolean variable, then updated to string type using the same field (e.g., source, target). The system now correctly removes or updates the variableType property based on the current type. Automated tests were added to validate this logic across condition creation, updates, and variable reuse. Existing flows are unaffected, and improved error messaging has been implemented to assist users in identifying type-related misconfigurations.

  • Datatable Format Strips Static Values from Variables A bug was identified where combining a variable with static text in a Datatable field—such as ##xVariable##[New]—resulted in only the variable’s value being displayed. The static portion ([New]) was being stripped during rendering, leading to loss of formatting context and user-defined annotations. This release corrects the parsing logic so that both the variable and the adjacent static text are rendered together, as intended. The fix has been verified using a provided Autom export and tested with various combinations of variable and text input. Unit tests have been added to prevent regression in future builds.

  • Deleted Credentials Still Functional in Automs Previously, Autom Mate did not properly validate the existence of credentials at runtime. If a credential was deleted after being configured in an Autom, the automation could still execute using the credential’s cached data. This posed a potential security and integrity risk. With this fix, credentials are now fully unlinked and invalidated at the time of deletion. Autom executions will perform a runtime check to confirm that any referenced credential still exists and is valid. If not, the system will return an informative error, halting execution. This behavior is now enforced across all credential types—OAuth, Basic Auth, API Key, etc. Unit tests and integration checks were added to ensure deleted credentials are no longer accessible under any condition.

  • OAuth Credential Name Lock Bug Previously, if the OAuth credential creation process failed or was canceled mid-flow, the system retained a partial credential record—including its name—despite not storing a valid token or completing configuration. This prevented users from creating a new credential with the same name, leading to confusion and blocking valid retry attempts. With this release, incomplete or failed OAuth credential entries are automatically cleaned up. The system now ensures that credential names are only reserved upon successful completion of the creation process. Edge cases—such as disconnected tokens, empty records, or browser cancellations—are now handled gracefully. Logging has been added for failure and cleanup events, and new unit/integration tests ensure the robustness of both successful and unsuccessful flows.

  • Overflow in Alert and Actioneer Profile Descriptions Previously, when users entered long text strings without spaces in the Description fields of the Alert Profile and Actioneer Profile pages, the content would overflow its container and disrupt the layout. With this fix, the UI now enforces automatic word breaking for unspaced text that exceeds the maximum width. Additionally, a character limit has been implemented on the Description input fields to prevent excessive input lengths. These changes ensure consistent alignment, prevent visual breakage, and enhance overall user experience in profile management interfaces.

  • Pagination Input Triggers Premature Page Load Previously, when users typed into the page number input within pagination controls, the interface would reload the page after each digit entered—causing abrupt jumps and making navigation nearly unusable for large page numbers. This update resolves the issue by deferring navigation until the user either presses Enter or clicks a new “Go” button placed next to the input field. The input now accepts multi-digit entries as expected, and only final confirmation triggers the page change. This fix ensures smoother and more predictable pagination behavior across all relevant views.

  • System Action Fields Break \n Format on Update A bug was identified where the note field in system actions handled newline characters (\n) inconsistently. While line breaks were correctly preserved during create requests, they were being altered or lost during update requests, resulting in broken formatting and inconsistent display. With this fix, both backend processing and UI representation have been aligned to treat newline characters consistently. Multiline content now maintains its structure during both creation and update flows. Automated test coverage has been expanded to verify this behavior at both API and UI levels.

  • JSON Unmarshal Error in Email Send Action (Repeat Loop) A bug was identified where the Email Send action inside a repeat loop would work correctly on the first iteration but fail on subsequent iterations with the error: json: cannot unmarshal string into Go value of type model.Attachment.

    The root cause was that the attachment input, initially structured as a valid JSON object or array, degraded into a plain string in later iterations—likely due to improper data handling in upstream steps such as REST responses or Regex outputs. This caused a type mismatch when the system attempted to deserialize the input into the expected model.Attachment structure.

    With this fix:

    • The attachment input is now consistently validated and parsed across all iterations.

    • Defensive type-checking and JSON normalization have been added before Email Send execution.

    • Flow stability is restored when sending emails with attachments inside loops.

    The change is backward-compatible and includes extended test coverage for loop-based scenarios involving file or data attachments.

  • MateDrive Attachment Parsing Fix Resolved an issue where entering file paths copied from MateDrive (e.g., mate:/asd/file.json) into the Email Send action's attachments field would result in a parsing error: invalid character 'P' in string escape code. The system now properly recognizes and processes MateDrive file paths as attachments. If an invalid or unresolved path is provided, the system returns a clear and user-friendly error message such as "Invalid MateDrive path." This ensures smoother email delivery using MateDrive-based files.

User Notices & Guidance

As part of the Boston 4.6.0 release, several behavior changes, improvements, and stricter validations have been introduced. To ensure a smooth transition and prevent confusion, please review the following usage hints, system warnings, and best practices:

Warnings (Critical Behavior Changes)

  • Dev Mode Restrictions Apply When Dev Mode is turned off, users will not be able to drag actions, modify triggers, update variables, or rename Automs. This mode is read-only. To make any changes, Dev Mode must be enabled.

  • Deleted Credentials Are Now Strictly Invalidated Credentials that have been deleted will no longer function in previously configured Automs. Execution will fail with an appropriate error. Review older flows to ensure they reference valid, active credentials.

  • OAuth Credential Name Lock Bug Fixed Previously, failed or canceled OAuth credential attempts could reserve the credential name. This behavior has been fixed. Users who encountered this bug can now reuse those credential names.

  • Email Send Action Inside Repeat Loop Requires Structured Attachment The Attachment field in the Email Send action must remain a valid JSON object (model.Attachment) throughout all iterations. If you use REST responses or regex outputs, ensure the format does not degrade into a string on later iterations.

  • License-Based Action Restriction Now Enforced on Import Automs containing actions not permitted by the current license will now fail to import. When sharing .autom files across teams or customers, ensure the actions used are license-compliant.

  • Live Error Indicator Now Affects Flow Readiness The new real-time error indicator on the Autom screen reflects validation issues in real time. If errors are present, flow execution may be blocked or produce unexpected results. Always resolve listed issues before attempting to run or publish an Autom.

  • Initial Flow Validation May Surface Legacy Errors Flows created before version 4.6.0 may now show validation errors during initialization that were previously ignored. Review and update these flows accordingly.

  • Action Version Switching Can Affect Runtime Behavior Switching the version of a custom action will immediately affect how that action behaves. If using older versions with different field sets or logic, test carefully before deploying.

  • Microsoft Login Requires Email Match to Existing User Users logging in with Microsoft accounts must have a corresponding Autom Mate user record with the same email. If no match is found, login will fail even if Microsoft authentication succeeds.

  • Microsoft Login May Appear Stuck After Success In some cases, after a successful Microsoft login, users may see a black screen with no redirection despite receiving a “success” message. This typically indicates a temporary redirect or token processing issue. If this occurs, refresh the page manually or contact your administrator. A fix is in progress.

  • Modifying Agent-Generated Autom's

    When an AI Agent is created, Autom Mate automatically generates a linked Autom flow to handle the agent’s execution. Users are free to open, extend, or modify this flow — including adding new actions or adjusting logic. However, Changing the Trigger Method or key flow structure may cause the AI Agent to stop functioning as expected. We recommend carefully reviewing and testing the agent after any modification to its linked Autom.

Hints (Productivity Tips)

  • Use the Agent Playground Before Going Live AI Agents can be safely tested in the Playground before deploying them to production environments. This sandbox allows simulation without impacting core workflows.

  • Chat History Is Now Persisted Interactions with AI Agents are saved, providing context for follow-up actions or long-running workflows. Users can view and reuse chat histories as needed.

  • Disable Actions for Partial Testing You can now disable individual or grouped actions to test parts of a flow without deleting them. This supports safer, modular testing and faster debugging.

  • Explore the Enhanced Help Menu The in-app help menu has been expanded with quick access to FAQs, platform documentation, and how-to resources. Use this area to onboard faster or resolve issues independently.

  • Pagination Input Now Requires Confirmation Entering a page number will no longer immediately trigger a reload. Users must press Enter or click the Go button to confirm navigation—reducing unintended jumps.

  • Use “Variables” Tab to Organize Data The new Variables tab in the Action panel provides a centralized view of all variables in a flow. Use this to rename, inspect, and trace usage of variables more efficiently.

  • Collapse Side Panels for Focused Building By default, the Library and Configuration side panels are now collapsed when opening a flow. Use this cleaner layout to stay focused, especially on large flows.

  • Custom Action Version Sync Ensures JSON Consistency When a custom action is updated, the flow UI and underlying JSON are now automatically synchronized. This eliminates mismatches between design and execution.

  • Monitoring Logs Offer Deep Linking You can now jump directly from a log entry to the related action within a flow using the new redirect icon — great for tracing issues faster.

Best Practices (Recommended Usage)

  • Validate Base64 Inputs When Decoding The decoder now tolerates missing padding characters (=), but malformed inputs will raise structured errors. Always ensure your Base64 strings are complete and well-formed.

  • Review Conditions When Changing from Boolean to String Changing a condition type from boolean to string will now automatically remove obsolete metadata. Still, it’s good practice to inspect the JSON for complex conditions after changes.

  • Preserve Formatting in Datatables When combining variables with static text (e.g., ##xVariable##[New]), ensure syntax is respected. The system now retains both parts properly, but avoid nested or ambiguous delimiters.

  • Avoid Long Unbroken Text in Profile Descriptions Description fields in Alert and Actioneer profiles now have a character limit and auto-wrapping enabled. For better readability, avoid using excessively long or space-free input.

  • Review Variable Icons for Better Navigation Variable icons are now visible throughout the platform. Use them to identify dynamic fields quickly, especially when working with large data tables or conditional logic.

  • Use AI Agent Trial Period Strategically The 30-day trial for AI Agents allows full usage during the test window. Evaluate high-value use cases (e.g., ticket creation, chatbot flows) before activating full access.

  • Avoid Editing Automs in Read-Only Mode If Dev Mode is disabled, flow edits will not be saved and may lead to confusion. Always check Dev Mode state before making changes.

  • Preserve Newline Formatting in Multiline Fields The system now preserves \n formatting consistently, but avoid injecting raw special characters (like \r, \t) into system action fields.

PreviousBoston 4.5.0NextBoston 4.7.0

Last updated