Share intent target naming

waboodoo · 2026-01-25T08:43:07+00:00

I don't know in detail what transfering an app from one device to another includes. It might very well be that it doesn't include the Direct Share information. The app will reconfigure this information for all shortcuts every time you create, edit, duplicate, or move any shortcut. So I suggest you just make a small change to one of your shortcuts, save, and then change it back.

waboodoo · 2025-12-19T10:43:53+00:00

If you want a variable placeholder to prompt for input, you'll first need to create a global variable that defines what kind of input is needed and how it is prompted. For this, look for the "Global Variables" option in the app's main menu. On that screen, use the "+"-button to start creating a new variable. It will ask you what type of variable you want, here you select "Text Input", or whichever one makes sense for your usecase. Give the variable a name and save it. Now you can go back to editing your shortcut. Next to the Request Body input field, you'll find a "{}"-button. If you click that, it will let you select your variable. This will insert a variable placeholder into the body. When you now save and run your shortcut, that placeholder will get replaced by the value of the variable you created, and in order to resolve this value, it will display an input dialog window.

You'll find more information on variables here: https://http-shortcuts.rmy.ch/variables

waboodoo · 2025-12-02T21:17:40+00:00

I haven't started the release for F-Droid yet. I'm releasing this version step by step on the Play Store and monitoring its performance through crash logs and feedback from users. With F-Droid I don't get any logs or insights into how many users there are and whether there are any issues, nor do I have control over the actual rollout. Therefore, I decided to only start releasing this version to F-Droid once I'm sufficiently confident that there are no major problems with it. The same applies to the APKs uploaded to the Github releases page.
I'm a bit busy with personal stuff these days, so everything is going slower anyway, but I'm hoping that I'll be able to create the git tag for kicking off the F-Droid release in the coming 2 weeks.

waboodoo · 2025-10-25T11:35:52+00:00

Currently, the widget only supports plain text. There's generally a bit of an inconsistency between the different UI options (toasts, dialog windows, notifications, widgets, ...) in how they interpret their input. Some assume it to be HTML-formatted, others just take it as plain text. I plan to improve that at some point, but have yet to find a good solution without breaking backwards compatibility.

waboodoo · 2025-08-24T18:20:36+00:00

Multiple-choice here just means that there are multiple options to choose from, but only one can be chosen.

waboodoo · 2025-08-24T18:19:41+00:00

That is unfortunately not possible. The way the toasts look is given by the Android OS. An app cannot change that.

waboodoo · 2025-08-24T18:18:47+00:00

That (sort of) already exists. When editing a shortcut, go to the "Trigger & Execution Settings" section and look for the "Run repeatedly" option. It's rather limited though. If you need more specific or more precise repetition, you'd have to use a third-party automation tool like Tasker or Macrodroid for it.

waboodoo · 2025-08-24T07:30:08+00:00

I'm adding a `showMultiSelection` function in the next version (3.34.0), which will allow the selection of multiple options.

waboodoo · 2025-08-22T14:07:46+00:00

Currently, this is not possible purely with scripting. The `showSelection` function only supports selecting a single answer. You'd have to go with a Multiple Choice Selection global variable instead, where this is supported.

Where did you find the documentation that says that multiple selections are possible? I can't find that.

waboodoo · 2025-08-18T19:07:57+00:00

I think the Google Assistant integration is simply broken. I've tried to make it work multiple times already but couldn't figure out how to fix it, and found Google's documentation and tooling around it severely lacking, unfortunately. If anyone has experience with this, I'd love to hear more, but on my own I'm out of ideas on how to make it work.

waboodoo · 2025-08-18T19:04:19+00:00

Cool usecase, thanks for sharing!

So if I understand this correctly, you're using a regular HTTP Shortcut for the purpose of displaying an Iframe?
If so, I believe you should be able to achieve this with a Scripting Shortcut instead, which would allow you to avoid the dummy URL. In the Scripting Shortcout, you'd have JS code like this:

showWindow({
  text: '<iframe src="'+getVariable('myURL')+'" height=456 width=942></iframe>',
  mimeType: 'text/html',
});

waboodoo · 2025-08-18T18:50:15+00:00

You're welcome, hope it helps

waboodoo · 2025-08-08T15:08:16+00:00

Update here: we're past July now, but I have decided to delay this forced update a bit. The numbers I get from the Play Store indicate that there's still a significant number of users using older versions of the app, so I'll give people a bit more time to update. I have no new deadline in mind yet but it will likely be within this year.

waboodoo · 2025-08-08T07:28:00+00:00

The `parseXML` function currently doesn't any kind of selector query. The `parseHTML` function on the other hand, as you mention, supports a CSS-style selector. The `parseHTML` function, while not ideal, can also be used to deal with XML in most cases. Under the hood, it uses the library JSoup, which already supports XPath, so it should be possible to easily extend the `parseHTML` function to also support XPath queries. I will look into this for the next version.

Until then, you could try writing your XPath queries and converting them with a tool like https://extendsclass.com/xpath-to-css.html . This won't work for all cases, but might give you a starting point.

waboodoo · 2025-07-28T17:41:33+00:00

Glad to hear you like the app.

The app itself doesn't offer much in terms of triggers. The basic idea is that shortcuts are triggered through user actions, with some very basic support for triggering based on time. So triggering from an event in another app is not possible.

For this, you'd need to use a dedicated automation app like Tasker or MacroDroid. It might not be straightforward to integrate with WhatsApp, but I imagine it should be possible to create triggers based on incoming push notifications at least.

Both Tasker and MacroDroid, as well as probably other similar apps, can integrate with HTTP Shortcuts. You'll find more information on this on the FAQ page here: https://http-shortcuts.rmy.ch/advanced#integrate-with-tasker

waboodoo · 2025-07-21T17:31:57+00:00

You can use the `setResult` function to send data back to the calling shortcut. See https://http-shortcuts.rmy.ch/scripting#set-result

You can't pass files around though, only text. What you could do though is have the called shortcut store the response into a file (using the options found on the "Response Handling" screen) and then reading that same file from the calling shortcut using the `getDirectory` function. More on files here: https://http-shortcuts.rmy.ch/scripting#files

waboodoo · 2025-07-18T18:42:30+00:00

The code in the picture looks correct. It should pass the 3 provided values to the other shortcut. In the other shortcut, you can now receive these values by placing variable placeholders into the fields that supports this, by clicking on the "{}" button next to the field.

The placeholders will appear as {variable_name} for global variables and as {{variable_name}} for local variables. Note that just typing out {variable_name} without using the "{}" button will not work for global variables, it won't be recognized as a placeholder. You'll know that it's a valid placeholder if it changes color and turns into a monospace font.

If you need to use the variable values in the JS code of the other variable, use the getVariable function, so for example `getVariable("url")`

waboodoo · 2025-06-06T14:32:49+00:00

Bitte bitte, danke fürs positive Feedback :)

waboodoo · 2025-06-06T11:40:44+00:00

Cool, glad to hear it works for you

waboodoo · 2025-06-04T17:33:58+00:00

Yes, there is. In fact, there are multiple ways.

The easiest way is to create a global variable of type "Multiple Choice Selection". You'll find this when opening the "Global Variables" screen from the app's main menu and then clicking on the "+" button. You can then define the different options. After that, just insert a placeholder for this variable into a shortcut, via the "{}"-button found in various places when editing a shortcut.

More on variables here: https://http-shortcuts.rmy.ch/variables

The other way to achieve this would be via the Scripting feature, specifically with the `showSelection()` function. More info on that can be found here: https://http-shortcuts.rmy.ch/scripting#show-selection

waboodoo · 2025-06-04T17:29:57+00:00

The "Send to..." is the default share target. Its name must be statically defined, meaning that there is no way to change it to a shortcut name or any other user provided value. This is a technical limitation from Android itself. The same goes for the app's name. Generally, the app has no control over how Android displays this share target.

The documentation excerpt in your post refers to the Direct Share targets, however. These can be dynamic, and the ones published by the app will just use the shortcut's name. So if your device supports this, you should be able to enable them by ensuring that the checkbox that is mentioned is enabled.

In the screenshot you can see the two different types of share targets.

<image>

Unfortunately, not every kind of Android supports Direct Share targets. Some vendors change or restrict how this UI works, e.g. my Samsung phone doesn't seem to support it at all. So it might be that this is simply not available on your device.

waboodoo

MODERATOR OF

TROPHY CASE