crashdummyy

Why don't you just add a webhook to the job as well ? I am not that familiar with jenkins ( using azure-piplines and gitlab ) but that should grant you more flexibility.

An API can then use the webhook to eg. post some messages to mail, threads, discord etc.

It all depends on your use case. You mentioning "scheduled task" appears you want to use a Worker Service

If you want to trigger your actions you can host a webapi, too.

Bottomline: Both use cases suffice your needs so your course depends on where you want to "control" your app ( set delay, maybe sometimes start the action manually ). WorkerService -> Config file on the host Api -> Configure from client

Theres a logt going on in the dotnet world. I currently do all my Rest APIs with asp.net core.

The Setup is very easy as the .net web sdk provides with a lot features you don't want to keep yourself concerned with. You can integrate Swagger with little effort.