Make custom workflow to work with tasks created via WRIKE API

I have been trying to create tasks via API in a folder, which already has a custom workflow defined. However, the workflow process doesn't continue, after I create the task accordingly.

For eg, on task creation, an approver should have been added according to the workflow. But it doesn't take place..Unless everything is done manually,it won't move on with the custom workflow process.

Can anyone suggest a workaround for this issue, as I want the custom worklfow to work with the tasks which will be created via WRIKE api.

Find more posts tagged with

Comments

Lisa Kizymishina

Hi @Neethu Rachel Rajan, welcome to the Community🤗 Looks like you've already reached out to Support about this. Our API experts will get back to you shortly via email when they confirm all the details.

Colin Burke

Was this ever figured out? I am trying to do the same with my team.

Lisa Kizymishina

Hi @Colin Burke, thank you for joining in the conversation. Setting task status by API does not trigger corresponding automation (i.e. starting an approval associated with that status or adding a task assignee). This is expected behavior and the reason is that the API itself is automation.

Hence, you will need to set the task status via workspace to trigger the automatic approval. Alternatively, you can make a separate API call to create an approval for the tasks where the status is changed via API: https://developers.wrike.com/api/v4/approvals/#create-approval.

I also agree that it would be extremely useful to start automatic approval upon task creation via API, and if you have a moment, I encourage you to share your idea in the Product feedback section: /hc/en-us/community/topics/115000020349-Product-Feedback. Thank you in advance 🙌

Akshin Jalilov

Hi, @Lisa Kizymishina there is a big problem with this:
Hence, you will need to set the task status via workspace to trigger the automatic approval. Alternatively, you can make a separate API call to create an approval for the tasks where the status is changed via API

Even if we create approval via API, once it is approved it does not follow on with the rest of the workflow, which completely brakes automation. Problem is unless Approval is created by manually assigining the status to Workflow Status, it does not read as part of that workflow status. However if workflow is locked no one can set status manually (which is the whole point of the appoval system in the wrokflow). How can this be intended behaviour when Wrike API and Workflows just don't work with each other.

Additionally if task is created via email with a workflow status then approval works. I do not understand why you cannot make it work with API the same way.

Elizaveta Bogdanova

Welcome to the Community @Akshin Jalilov, and thanks a lot for sharing your detailed feedback with us!

Welch Bailey Automation -

Very annoying issue.

Task creation is task creation and task update is task update.

Should be able to apply to When task created automations or When task updated automations