Many Apps integrate with Tasker...

[maxxyypoo]

Would it be possible to make those apps that integrate with Tasker think that Automagic is Tasker and let them integrate with Automagic...? There should be a way. When you click to do a Tasker action in one of those apps and Automagic would be like hey I am Tasker and overtake that and etc. That would be very useful, since stupid ass app makers don't know that there are other much better automation apps. Easy solution would be to make apps instead of do a Tasker action execute a normal standart android shortcut then any of automation apps could handle the action but app makers are idiots. So yeah. Possible or nah?

[Wibbly]

I agree, there'a an API unique to Tasker some apps support. If Automagic could support/emulate it, that would open up new applications for Automagic.

Llama/Tasker/Automagic also support Locale API/plugin architecture, but many devs of useful pluggins do not - they stick to the Tasker-specific one

[AMChris]

+1

I too have some Apps that integrate with tasker but fail to work with Automagic.
Would be great if possible.

[Mar]

+1

[Bushmills]

Sometimes, apps look whether tasker (the actual app) is actually installed, after figuring out that the tasker API is available. I can't tell how often that's the case with the apps you're not able to use with Automagic, but I know that this was the case with an app offering tasker support in the past, and fixed by now; the author simply didn't consider the possibility that his app was used with an app other than tasker, and checked just for good measure, and to be on the safe side. In this particular case, there was nothing Automagic could do about. I suppose it may be necessary to get to know the reason why those apps or extensions you're not able to use with Automagic fail.
A while ago, Automagic lacked support for an extension to the API, causing some other apps to provide only spotty support - but that has been fixed before the original poster wrote the request, and can therefore probably be excluded as problem cause.
Which apps are those many apps with fail to work with Automagic?

[Wibbly]

Interesting thread - so maybe Automagic does indeed support all Tasker plugins already, from an API perspective?

And the "problem" is some devs look for the Tasker app specifically, or have no idea about anything other than Tasker?

My own experience is not that Tasker plugins don't work so much as when I ask, their devs don't say they support anything other than Tasker/don't know if anything else would work. So I have not persued such plugins...

It would be good if Martin or someone could confirm if Automagic should support any plugin that uses the Tasker API as I don't know if the Tasker plugin API is unique to Tasker in any way and if Automagic attempts to emulate it... That would at least give more confidence to experiment more, even with paid for plugins.

[Martin]

Automagic supports plugins written using the API specified by Locale (doc) and also supports most extensions to this API supported by Tasker (doc).
Since some plugins check that a particular plugin host like Locale or Tasker is available, I decided to flag the trigger, condition and action Plugin as experimental but it should work fine with most plugins.
Tasker also supports methods to directly execute tasks and actions by other apps (doc). Automagic does not and will not support this method of integration for security reasons.

[Wibbly]

Many thanks for the clarification, Martin.