unfortunatelyour app does not qualify for the permissions to read call logs and send text messages, those are considered sensitive permissions according to Google and are only approved by them. You could compose a text message but not send it.
What you do is you have an automation that sends a notification command to broadcast an intent to Tasker. Then in tasker your profile listens for that intent and executes any tasker defined action. This way you can get tasker to react to things happening in your house. The intents in this case can be anything you want. This could be used as an alternative means to having tasker reading a notification and reacting off of it.
The Companion apps offer a lot of different notification options. In place of posting an actual notification on the device you can instead send a command as the message to trigger certain actions on your phone. Read below to find out what commands...
Can you also share what the rendered template looks like please? Because if any commas are in the rendered template then you will need to URL encode them in a separate sensor/input_text so they can be properly displayed in the app.
what i meant was that if there are commas in the description then the only way you could send it as an intent extra is to follow the URL encoding for the text. You would basically need to have a sensor that converts the text into URL encoding and use that in its place to avoid the commas messing up the extras. In other words you need to have that sensor replace commas with %2c as that is the correct url encoding for a comma. See what I mean? You actually have to provide the text output in the expected format.
3a8082e126