Although a dedicated tasks app in Podio is a good thing, there are still situations where Podio's native tasks are preferable because they're quick and centrally located.
In this example, we'll look at the process after a website project goes live. When a project is complete, we generally have 4 tasks that need to completed:
BUT: Tasks 2, 3 and 4 can only be done AFTER task 1 is completed, and task 4 can only be done after task 3 is completed.
Our first Flow will trigger on a status change in the project when it's marked as complete, and assign the first task.
Our second Flow will trigger on Task Completion and will check the name of the task that got completed. We can actually use this one Flow to assign all remaining tasks depending on the task that just got completed.
To summarize the above logic, the Flow states:
And that's it. Tasks will now be created conditionally in sequence. Here's a simple screenshot animation to show this: