Skip to main content

v1.06.4 — Week of June 22, 2026

v1.06.4 · June 22, 2026 – June 28, 2026

New Features

  • Enhanced support for Nango Cloud webhooks with a dedicated signing key for secure verification, allowing for smoother transitions and higher security when interacting with cloud services.

  • Introduced Syncro integration capabilities, enabling users to sync operations across multiple platforms, enhancing workflow and service desk efficiency.

  • New tools for Autotask integration, including at.bundleTickets, at.unbundleTickets, and at.mergeTickets, making it easier to manage ticket relationships effectively.

  • Added various reporting tools for Microsoft 365, facilitating better insights into license usage and activity for more informed management decisions.

Improvements

  • The Autotask widget now provides a Disconnect and Reconnect button, allowing users to manage their integrations more effectively and avoid duplicate webhook registrations.

  • Streamlined the process of registering Autotask insights with improved error handling, so users receive clearer feedback during registration attempts.

  • Updated messaging prompts to be provider-agnostic, ensuring users receive relevant instructions based on their specific PSA without confusion.

  • Enhanced user experience in the Autotask Insights iframe by implementing in-iframe sign-in, allowing for seamless access without needing to refresh in a new tab.

Bug Fixes

  • Fixed several issues with the Datto RMM integration, including authentication errors that now provide clearer, actionable feedback for users when connection problems occur.

  • Resolved a bug where approval requests were incorrectly marked as expired, improving the reliability of approval mechanisms during interactive sessions.

  • Addressed multiple issues with syncing Autotask tickets, ensuring accurate assignment of ticket owners, thereby providing better visibility and accountability.

  • Improved error visibility in Autotask registration, ensuring users can see why their requests may fail instead of encountering unhelpful generic error messages.

Did this answer your question?