Feature Requests

Partner is building Flows to automate ticket note creation using a skill built in Super Magic. The "Run Skill" action is not currently available in Flow Builder. Partner would like to be notified when this feature becomes available and is registering interest for early access. This would allow them to complete their automated workflow for new ticket processing.

Currently flows only trigger once per ticket. It would be useful to have the option to allow certain flows to run multiple times per ticket.

Add support for flows and skills to run multiple times on the same ticket when conditions are met again or when a workflow has been updated. Currently, once a flow runs on a ticket it cannot be re-triggered, even if a skill failed or changes were made later, forcing users to recreate flows or manually process tickets. The request also includes the ability to bulk-run or retry skills across multiple tickets without requiring individual confirmation clicks for every action. An optional continuous or repeated trigger-checking mode similar to ConnectWise Manage behavior would improve workflow flexibility and reduce manual effort.

Currently, the Dispatch Scope filter in Auto-Dispatch Beta only supports an "is" condition. Partners would like the ability to use an "is not" condition, so they can exclude specific company types from being dispatched. This is particularly useful when there are a small number of companies that should never be dispatched, making it more efficient to exclude them rather than listing all eligible ones.

Add a reliable way to prevent race conditions between concurrent automation actions on tickets. Current automation flows can update ticket status before other field updates such as Type, Subtype, Item, notes, or board changes are fully committed. This causes downstream integrations and workflows that trigger on status changes to process partially updated tickets with missing data. The request is for automation execution ordering guarantees, such as committing status changes only after all related ticket updates complete, or providing a dedicated "triage complete" event or flag that external workflows can safely trigger from. This would improve consistency for integrations and reduce intermittent issues caused by multiple automations writing to the same ticket simultaneously.

Partners need more granular control over the Auto-Dispatch Beta queue behavior. Specifically: (1) The ability to configure which ticket statuses remove a ticket from the dispatch queue, rather than it being automatic. (2) Control over whether having a ticket owner assigned affects queue weighting. Example use case: "Client Responded" tickets should still be weighted/visible in the queue even when a ticket owner is assigned, rather than being automatically excluded.

Add the ability to drive workflows based upon SLA progress (10 minutes left on SLA, 33% of SLA remaining, etc)

Flow-generated internal notes are visible in the ticket thread UI but are not returned through the API when using include_messages=true and are not indexed for keyword search. This affects all Flow-created notes across boards and prevents teams from programmatically filtering, counting, or analyzing tickets based on note content. There is also a related need for AI features and companion applications to access these internal notes for context, reporting, and QA workflows. The request is to make Flow-generated notes fully accessible through API responses, searchable through keyword indexing, and available to AI-powered tools and integrations.

We would like to be able to use the customer reply flag and items from Connectwise Manage in our flows. I am trying to set auto-dispatching and auto-close but I need to be able to use these two parts of Manage to be able to perfect them.

Add a filter option in Flows for tickets that have no resources assigned in ConnectWise Manage.