We are trying to set up a scenario where if an Asana task is updated, it also updates the corresponding task in Float.
However, Float does not use Asana Task ID, which is a required field.
They do however share the task name.
Is there anyway around this?
Hi @Lewis_AP,
There are two approaches to this, a stateless and a matching approach.
Stateless:
If Asana and Float offer a way to store the task ID (for example in a custom field) of the other application, you can store the ID and use it in your scenarios whenever a task is changed. This is stateless because an event on the one side will trigger an action on the other side without you storing information in another location.
Matching:
If the above is not possible or unwanted, you should keep track of Asana and Float tasks that are matched. You can do this with a Data Store. You can store each created task with it’s Asana + Float ID. Whenever a change must be made in either application, you have both ID’s to map.
Cheers,
Henk
There is a third approach which is also stateless, where you first do a Search for the corresponding task in application B when a task in application A is changed. However, this is prone to errors because you are introducing a component of non-conformity. Task names can be changes, thus cannot be found anymore.
