User Task Handling on microservices architecture

I am trying to use a centralized camunda workflow engine in a microservice architecture to orchestrate other microservices.

I have a use case that I’ve simplified like

→ User edits comment (user task) → Send notification to post owner (service task)

Here, what I’ve done is when a user edits a comment in the UI, an API of user microservice is called which in turn calls the centralized camunda microservice to notify of user task completion through the API “/rest/task/id/complete”.

Is this the correct way to handle user tasks in microservice architecture with centralized workflow engine? There seems to be too many API calls involved.

Any helpful references or examples would also be highly appreciated.