Although the response you got is likely correct in terms of webtask.io, it’s important to note that rules do NOT run within webtask.io. I believe it would be more correct to say that the underlying technology/stack used to execute rules was also made available as a separate concept within webtask.io so that generic tasks (Node.js code) could be deployed and run in webtask.io. However, what you would execute in webtask.io would be completely separate of Auth0 so the need to find another provider only applies to general task that people created and deployed to webtask.io; it does not apply to rules.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Webtasks for Limited Time on Free Plan | 2 | 2828 | August 16, 2019 | |
| How to build Extensions - is WebTask framework available? | 1 | 1065 | September 11, 2023 | |
| Questions on webtasks included with auth0 subscription | 1 | 4108 | December 21, 2017 | |
| Auth0 rules testing using webtask token | 1 | 4347 | December 18, 2018 | |
| Access for webtasks | 1 | 3666 | May 23, 2019 |