After a minor learning curve, GloboFlow becomes as intuitive to use as Podio. Between workflows that involve Podio, Zaper, GlobiFlow and ItDuzzIt, GlobiFlow is by far the most reliable and offers the best UX. (Zapier is pretty nice, but it lacks GlobiFlow's "Refresh from Podio" option, which is handy when you're changing app structure to fit the requirements of your flows.)
The GlobiFlow support team is also fantastic. They're very quick to respond and, when they do, they provide helpful info, often with screenshots of configurations that would otherwise by tough to explain with words. Virtually every time I've contacted them, it was either something I was doing wrong or something I didn't know how to do. I haven't' yet stumbled on an actual bug.
I once reported what I thought was something that was hindering usability. I got en emaIl back within a few hours from the lead developer, saying he agreed and he had fixed it. And this was on a Sunday!
The "Calc" type of filter and action uses PHP notation to get things done. This might scare off some at first, but it's actually a wonderful thing. You can pull cope snippets from the Web and do lots of things that would otherwise be impossible using the GUI. It's also handy for forcing order-of-precedence for test conditions, which is something not possible with just AND/OR joning of conditions. Finally, this is your best friend if you want to use variables in your flows.
As I mentioned, Podio would be on no use to use without GlobiFlow. Anyone who plans to use Podio for anything other than the absolute basics, should get to know GlobiFlow. (ANd if you're using the free edition of Podio and you think you'll love the "advanced" workflow editor you get when you start paying, don't get your hopes up. GlobiFlow is by far better than the "advanced" Podio editor.)
GlobiFlow has a lot of documentation, but it's structured more in example form than in reference form. I would prefer a searchable reference that was structured more like conventional technical documentation. (That said, it's far more useful than the discussion thread sort of documentation Podio offers.)
You can't copy and paste action blocks between flows. In some cases, this wouldn't make sense because of field differences, but it could often be helpful. Likewise, when you change a trigger type for a copied flow, the field value assignments are removed. I would prefer they stay as is, so long as a field of the same name can be found. (This is the case if you copy apps and copy workflows.) But I guess these are all based on IDs rather than names, so that's likely not so easy.
GlobiFlow offers a "drop though" sort of metaphor, meaning that execution starts at the top of your flow and works downward. There is a "Sanity Check" action, which is basically an "if" conditional to execute a block of steps. But there is no way to branch based something like a Switch statement. That would be handy.
Overall, the strengths of GlobiFlow (including the people at the company) far outweigh any weaknesses.