It was actually supposed to be v2.2.4, but I mistyped, so here we are. Improves the “Get Item from List” Siri Shortcut by providing icons and subtitles for improved identification of items. It also fixes two crashes, one of which occurred on iOS 15.
With Transloader 3 finally publicly available, I’d like to invite you on a tour through the app and its functionality. In Part VI, we created custom Link Actions to change Transloader’s behavior for certain links. In this Part VII, we’re setting up File Actions to operate on certain files, once they’ve been downloaded by Transloader. It’s so cool you’re here for this – let’s get crackin’!
After Transloader has downloaded a file, you might want to do something with it automatically, like moving it into a specific folder, or opening it with an app. That’s where File Actions come in. You give it a file type it should act upon, and if the downloaded file is of that file type, the app or Automator workflow you’ve selected is executed. Let’s say we’d like to move downloaded video files into our ~/Movies folder.
Setting up a File Action
Actions are easily set up. Open Transloader’s Preferences, select Actions, click the + button at the lower left and select Add File Action. You’ll be asked for a bit of input:
You can make File Actions execute for: – files downloaded from specific hosts (e.g., “eternalstorms.at”) For hosts, Transloader uses a partial search, so if you were to specify “youtu”, the File Action would apply to all links containing that string, like “youtube.com”, and “youtu.be” – files with specific extensions (e.g., “zip”) – files conforming to specific UTIs (e.g., “public.image” – which would make the Action execute for all image files)
In this example (moving downloaded video files into the ~/Movies folder), select “f it conforms to UTI”, and use “public.movie” as its value. It will make Transloader execute this action for all video files it downloads.
Before we click “Select App or Automator workflow…”, though, we need to create the Automator workflow.
Creating an Automator Workflow
Launch Automator, select New from the File menu and choose Workflow. This will save the file in a format Transloader will be able to run as a custom user script later on.
From the left panel, drag over the “Move Finder Items” action, select the Movies folder in the pop up and save the workflow.
For apps in the macOS sandbox to be able to run user-supplied scripts, they need to be placed in a certain directory, functioning as a form of consent of the user for the app to make use of your script. Each app has its own folder; for Transloader, it’s /Users/yourname/Library/Application Scripts/at.EternalStorms.Transloader/ . You can either navigate there manually, or let Transloader help you a bit along the way when you set up a File Action. While it can’t place the script into the folder itself (that would totally circumvent the purpose), it can open that somewhat hidden Application Scripts folder for you:
Back in Transloader, click “Select App or Automator workflow…”, and select “Go to Application Scripts Folder”. Transloader will show a new Open dialog, with the Application Scripts folder pre-selected. Right-click it and select “Show in Finder” to go there directly, so you can place the workflow you’ve just created into it. Afterwards, select the workflow in Transloader’s Open dialog. Save the Action, and you’re done.
File Action… in Action
With the File Action set up, anytime Transloader downloads a video file, it’ll be moved to your ~/Movies folder
Simpler File Actions
While most File Actions will likely involve creating Automator workflows (just because it makes it so easy to work with files), there certainly are simpler cases for using File Actions. For example, if you’d like to open any image file Transloader downloads with Preview.app, it’s easily done:
Wildcards
If you’d like Transloader to forward all downloaded files to one workflow, you can use an asterisk ‘*’ as the host, file extension or UTI.
Exporting and Importing Actions
You might notice that File Actions are local to the Mac you set them up on, and won’t sync across your Macs. There’s a reason for this: Apps or Automator Workflows you select on one Mac might not be available on another, rendering the actions that use them defunct. Now, I want to improve this with a future update, but up until at least v3.1 (work in progress), that’s just how it is. However, you can manually export and import actions:
To import Actions on another Mac, double-click the file you’ve exported on it.
For extra convenience, the last 15 values you’ve used in Actions (like “public.movie”, or “zip”) are synced across your Macs, so that when you want to set up similar Actions on different Macs, you won’t have to do everything by hand.
Conclusion
Finally, you know everything there is to know about Transloader 3! How does it feel? Enlightening? Empowering? Fan-super-freaking-tastic? All of the above? I bet it does.
Thank you for having joined me in this exciting tour through the app. I hope you find it useful, and enjoy it! Have any feedback or questions? Don’t hesitate to write me!
With Transloader 3 finally publicly available, I’d like to invite you on a tour through the app and its functionality. In Part V, we discussed logging in to websites for files that require authentication to be downloaded. In this Part VI, we set up Link Actions to customize Transloader’s behavior on a Mac when a link is assigned to it. I’m so glad you’re joining me for this – let’s get right into it.
You might come across a link that you’d like Transloader on the Mac you’re assigning it to not to download, but pass on to another app, or Automator Workflow instead. That’s where Link Actions come in. With a Link Action, you define a rule, and if that rule applies to a particular link assigned to the Mac, that link gets passed on to the app you select, instead of being downloaded in Transloader. Let’s start with an simple example: FTP links.
Setting up a Link Action
Transloader doesn’t handle FTP(s) links, so having a Link Action for links with that URL scheme would be a great idea. By default, Transloader tries to send links with URL schemes other than http(s) to an app on your Mac that can handle it – or it fails the download.
Actions are easily set up. Open Transloader’s Preferences, select Actions, click the + button at the lower left and select Add Link Action. You’ll be asked for a bit of input:
For the “Rule” part of the Action, you can select “if host contains”, or “if URL scheme is”.
A host ist the main part of a URL, like eternalstorms.at in https://eternalstorms.at/transloader . Note that for hosts, Transloader uses a partial search, so if you were to specify “youtu”, the Link Action would apply to all links that contain that string, for example “youtube.com”, and “youtu.be”.
A URL scheme is the first part of a link, like https, or ftp – basically anything that comes before the first ‘:’ in a link. Here, Transloader uses an exact match (though ignoring upper- and lowercase), so http will match http, but not https.
In the case of setting up a Link Action for FTP links, select “if URL scheme is” and enter “ftp” (or select it from the list).
Now click “Select App or Automator workflow…” to do exactly that. If you have an app installed that handles FTP links, it’ll be automatically pre-selected by Transloader (in the case of FTP links, it might even be the Finder) for your convenience. But feel free to use any app you think would fit best.
And we’re done!
Congratulations, you’ve just set up your first Link Action. Whenever you assign an “ftp://…” link to this Mac now, it will be sent (in the above’s screenshot’s case) to ForkLift, instead of being downloaded within Transloader.
Using an Automator Workflow
Instead of “regular” apps, you can select Automator Workflows that you want to handle the links. Perhaps you don’t want to download the link at all, but turn it into a webloc file in Finder? That might be handy for, say, links to apps on the App Stores. Let’s get that going!
Creating an Automator Workflow
Launch Automator, select New from the File menu and choose Workflow. This will save the file in a format Transloader will be able to run as a custom user script later on.
From the left panel, drag over a “Run AppleScript” action and copy down the following:
Update the destination path to your liking – in particular, change “matthias” to your own account’s short name, and you’re done – you can quit Automator now.
Back in Transloader, create a new Link Action, select “if host contains” and enter “apps.apple.”, to make this Action affect any link assigned to this Mac that contains that string (most likely, App Store links).
For apps in the macOS sandbox to be able to run user scripts, they need to be placed in a certain directory, functioning as a form of consent of the user for the app to make use of your script. Each app has its own folder; for Transloader, it’s /Users/yourname/Library/Application Scripts/at.EternalStorms.Transloader/ . You can either navigate there manually, or let Transloader help you a bit along the way when you set up a Link Action. While it can’t place the script into the folder itself (that would totally circumvent the purpose), it can open that somewhat hidden Application Scripts folder for you:
Click “Select App or Automator workflow…”, and instead of selecting an app, click “Go to Application Scripts Folder”. Transloader will show a new Open dialog, with the Application Scripts folder pre-selected. Right-click it and select “Show in Finder” to go there directly, so you can place the workflow you’ve just created into it. Afterwards, select the workflow in Transloader’s Open dialog. Save the Action, and you’re done.
Assigning an App Store link to this Mac now results in a webloc file being created. A more elaborate Automator workflow would maybe create that webloc file, like we did above, and then continue to pass it to another app, like I’m doing with Yoink:
A Link Action I’ve set up for App Store links – they’ll be forwarded to Yoink, instead of Transloader attempting to download them.
Wildcards
If you’d like Transloader to forward all links to an app or workflow, you can use an asterisk ‘*’ as the URL scheme or host. Be aware, though, that this will result in Transloader on that Mac not downloading any links you assign to it, like, at all.
Sending Commands to Macs with Link Actions
You could also come up with your own URL schemes, like “putthismactosleep” (they can be just about any string). On a Mac, you’d set up a Link Action that would look for links with that URL scheme, and then run an Automator workflow to put the Mac to sleep. Were you to assign a link with that URL scheme to this Mac now (“putthismactosleep://” would suffice), it would go to sleep upon receiving it. There are lots of possibilities.
Exporting and Importing Actions
You might notice that Link Actions are local to the Mac you set them up on, and won’t sync across your Macs. There’s a reason for this: Apps or Automator Workflows you select on one Mac might not be available on another, rendering the actions that use them defunct. Now, I want to improve this with a future update, but up until at least v3.1 (work in progress), that’s just how it is. However, you can manually export and import actions:
To import Actions on another Mac, double-click the file you’ve exported on it.
For extra convenience, the last 15 values you’ve used in Actions (like “ftp”, or “youtu”) are synced across your Macs, so that when you want to set up similar Actions on different Macs, you won’t have to do everything by hand.
Summary
You now know how to customize Transloader’s behavior for certain links – with Link Actions. You’ve got the power!
In the next Part VII, we’ll continue with Zelda Actions – whoops, no, my mind wandered there for a second. In Part VII, we’ll explore File Actions. They are executed after a file was downloaded in Transloader and come in handy to sort downloaded files into folders, for example.
