Breakout vs Okta Workflows (Azuqua)

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

Read full review

• 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.

Read full review

• Would be great they could come up with iOS and android versions as well

Read full review

• 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.

Read full review

• Breakout is pretty affordable, the ROI has been great for us

Read full review

• 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.

Read full review