Breakout vs. Okta Workflows (Azuqua)

Breakout is well suited for the organizations where there is need of automating multiple recurring process to increase the productivity and effectiveness. For our IT department it has helped us in assigning the support and assistance requests made by different departments to our team members, keep the checklist that they need to follow and easy to use form to collect details and track their status of work.

Azuqua is well suited to connect data based systems or to add an extra level of automation to Smartsheet without requiring the control center. It is also well suited for people who don't have in depth understandings of programming. The UI is mostly visual with click and drag systems instead of requiring manually entered variables.

• Simple and easy to use interface
• Provides third party integrations
• Good support
• Brings in accountability
• Great for tracking

• The concept of reduced code to simplify use by less technical teams lowers the barriers to integration and allows teams to collaborate with ideas and concepts much easier
• The ability to review simply any error cases simplifies the old approaches of debugging and reviewing large and complex logs
• While not strictly part of the platform the support team's efforts to assist, to help clarify issues and then (where necessary) to resolve bugs was a large benefit and a key driver to extend the platform's footprint.

• Android and iOS still not available

• The lack of connection/card documentation. Every card does have a section with details, but they are sometimes lacking.
• The help center and community also need some structuring work. Every single connection/app should have a section with detailed documentation regarding its triggers and actions.
• The FLO history section needs to be more refined. It sometimes does not load and choosing the date doesn't actually show execution results from that particular day.

Our organization had evaluated it for sometime, but it was on the higher side for the budget we had. Many of our departments used it for a while, even after the initial demo session many users from different departments had raised IT assistance requests. Keeping in mind these factors at hand we started exploring alternatives.

I had to use the Automate tool for funneling image assets in bulk (tens of thousands) from FTPs into various destinations on an eCommerce platform. The user interface was quite harsh in comparison to Azuqua. Far more text/code line driven.

• Increased efficiency
• Users haven't needed IT assistance at any point of time
• Made it easy for team leaders to track different tasks more conveniently

• Even though our revenue has grown 3x since we started using Azuqua we have only marginally increased many of the teams due in large part to the efficiency gains that we have been able to realize with Azuqua.
• Before Azuqua we spent a large amount of time talking about technical complexities in solving for customer success and value. Now we only talking about solving for customer success and values because the technical complexities disappeared with the introduction of Azuqua.