MapTasker is a program that runs on in your browser, reading your Tasker XML file and displaying your entire or partial Tasker setup in an easily viewable format. MapTasker helps visualize and understand your Tasker projects, profiles, tasks, and scenes. There are many display options to customize the output the way you want it.

While you're waiting for next Tasker release in September...

MAJOR new feature since the last announcement: EDIT MODE

• Add Profile, Edit Profile, Add Task, Edit Task

Caveats...

1- The Edit May Be Incomplete

Task actions may have arguments that can not be determined at time of edit, such as an icon needed. In this case, it will be necessary to re-edit the given item under Tasker to complete the arguments. Some conditions, such as 'Application', are not (yet) supported since MapTasker doesn't (yet) have a list of Applications on your Android device. In this event, you'll have to add such conditions under Tasker.

2- Extra Arguments in Tasks

In some cases, you will be prompted for action arguments that do not appear when adding the same under Tasker. From what I can tell, this is due to the fact that Tasker's argument definition specifications support older versions of Tasker, in which such arguments are still supported. For example, the 'Flash' action prompts for a 'Title' under MapTasker, but the current beta 6.5.6 of Tasker does not. In this case, Tasker should just ignore this argument when it is found in the action.

3- Save Tasks/Profiles to Android --> Requires Tasker 6.2 or higher.

This function actually loads the item into the live Tasker session on your Android device. Since there is no 'Refresh View' in Tasker, it is necessary to then exit and restart Tasker to actually see the added Task or Profile. If Tasker is not running, an HTTP error notification will appear on the Android device. The current implementation saves them under the 'Base' (Home) Project, from which you can move it/them. A future enhancement will allow for a target Profile/Project to be specified when saving to Android.

4- Some Profile Conditions and Task Actions Not Supported

In some cases, a condition or action may require one or more parameters that simply can not be provided unless running within Tasker. Such is the case for many 3rd-party or Tasker plugins that require a configuration, since these configurators are unknown to all except Tasker (at this time), or an Application name from the Android device which isn't available to MapTasker.

5- Profile State and Event Conditions

Adding a State or Event condition is a 2-to-3 step process. First you must add the State or Condition, and then once added, select it, by clicking on the down-caret, to add/modify it's arguments.

6- Save to Current File

This command makes a copy of your current local XML file and updates the copy. It then reads back the modified copy which becomes your new 'current file'. The original is never changed.

7- Edit Options 'Cancel' is self intuitive.

'Ok': make the change in memory only.
'Save to Android': saves to current (active) Tasker session.
'Save to Current File': see #6, above.
'Save Single Task/Profile': Save as the single Task or Profile to the current directory with the given name.

8- Validation and Defaults

MapTasker does not do any extensive validation of settings. Additionally, default settings for arguments are not all populated.

9 - Remember, THIS IS NOT Tasker.

So the look and feel will be different. It may feel a little clunky at first. Suggestions are welcome.

FINALLY - THIS IS A PRE-RELEASE / PROOF-OF-CONCEPT ... Things may not work perfectly.

Given the caveats, if you want to kick the tires then read on...

To install it into a virtual environment, enter the following commands into Terminal/command prompt:

via pip:

• cd xxx, where 'xxx' is a directory into which you want to set up the virtual environment.
• python -m venv venv
• Activate the virtual environment...
  • MAC/linux:
    • source {directory path to 'xxx'}/venv/bin/activate
    • pip install maptasker==12.0.0b1
  • Windows:
    • .venv\Scripts\activate
    • pip install nicegui
    • pip install maptasker==12.0.0b1

...or...

via uv:

• cd xxx, where 'xxx' is a directory into which you want to set up the virtual environment.
• uv venv
• Activate the virtual environment...
  • MAC/linux:
    • source {directory path to 'xxx'}/venv/bin/activate Windows: .venv\Scripts\activate
    • echo "fastapi < 1.0" > constraints.txt
    • uv pip install maptasker==12.0.0b1
    • rm constraints.txt

NOTE: This beta will not appear as an automatic update in the GUI.

To run:

• start the virtual environment
• run either from the command line: maptasker (if installed via pip) or uv run maptasker (if using uv to manage your environment).

Report any/all issues at this link.

Features that are in the works:

• Add/Delete/Export/Import a Project
• Add a label to a Task action
• Profile and Task Rename/Delete
• Save to (Android) specific Project
• Save to Android as a file under 'Tasker/xxx', where 'xxx' is 'projects', 'profiles', 'tasks' or 'scenes'
• Edit Scene

Hi everyone,

I am trying to build a simple automated logbook. Every time my Google Health / Fitbit app sends a push notification, Tasker should create a calendar entry with the notification's title and text.

To achieve this, I am using the AutoNotification plugin.

My Setup:

• Profile Trigger: AutoNotification Intercept (selected the Health app).
• Task: Standard Calendar Insert action.
• Plugin Settings: Event Behaviour is checked (True). I also enabled Get All Fields and Link to Notification in the advanced settings.

The Problem:
The plugin successfully triggers the task and creates the calendar entry every single time a Health notification arrives. However, the variables %antitle, %antext, %antexts, and %antextsbig are completely empty. Tasker just prints the literal variable names into my calendar entry.

What I have tested so far:

1. Testing with other apps: I switched the AutoNotification profile target to the Reddit app and sent some test notifications. It works flawlessly! %antitle and %antext are filled with perfect plain text. So the plugin setup and task structure are definitely working.
2. Testing with Tasker's native event: Before buying the plugin, I tried Tasker's built-in Notification event. Interestingly, on the very first run, it actually gave me plain text. But on every subsequent run, %evtprm2 only contained a cryptic resource ID like: -1200241543::SUMMARY::57365f91556fb5058ee6e9d852263a55.

It seems like Google Health hides its notification content or uses dynamic resource IDs that AutoNotification fails to capture out of the box, unless the app was recently opened and active in RAM.

Has anyone successfully intercepted Google Health / Fitbit notifications with AutoNotification? Is there a specific advanced variable, a regex filter, or maybe a Logcat entry I should use instead to grab the actual plain text?

Thanks in advance for your help!

Disclaimer: AI was used for translation purposes on this post to make sure my technical issue is easy to understand in English.