It sounds like your are implementing a finite-state-machine. I don't know all the requirements of your project to know if this is a good application of a graph database. To answer your question, you can not assign properties to paths. What you may consider doing is creating 'State' nodes that contain the state for a specific workflow, and this node is related to the node representing the current state in the workflow. You would update this 'State' node whenever a state transition is made, and also remove the old relationship to the previous state and link the 'State' node to the new node. The 'State' node could have the state and all the workflow's metadata so that you could use it to get a handle on your workflow graph. Another idea is to label all the nodes for each workflow with that same label that is unique to the workflow, i.e. Workflow_<workflow_id>. This would allow you to get all nodes of that workflow very easily.
match(n:Node) where n:Workflow_<workflow_id>
return n
How are you going to advance each workflow? Are you getting events streamed, that you can use to automatically advance each workflow?
