Moving workspace with API not triggering "workspace changed to __" workflows

My organization wants to keep our service categories consolidated. This means having some requests in workspaces they don’t necessarily belong in because I cannot have requests from one workspaces service catalog in another workspaces service category. 

Because of this I have a workflow at the global level, every time a ticket is submitted with a specific phrase in the subject, it moves it to the selected workspace. Then a workflow in the target workspace that sets the group and adds tasks. 

My idea was to create a workflow that uses a custom object to read the requested item and what workflow it needs to be in, then uses the API to set the workspace. This worked wonderfully for moving the workflow. But not it no longer triggers the workflow in the target workspace, with the trigger “ workspace is changed to *target workspace*” 

So two solutions to my problem could be 
1. Allow service items to be in service categories from other workspaces. 
2. When an item is moved from one workspace to another using the API, it triggers workflows that look for “workspace changed”