Best design pattern for interactions in the form of cyclic graph

I have a PHP script which uses an external API. The interaction process is quite complicated, but generally the script consists of several "commands" (aka API function handlers) which should be invoked in a sequence which could be represented as a cyclic graph. Some commands can be invoked several times after other commands on some conditions. What is the best way to design this behavior?