Okta Workflows (Azuqua)

Okta provides seamless connectivity and login experience for multiple applications. It provides great security.

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.

Azuqua is well suited for scenarios where you need to either connect to applications or automate tasks in another. Azuqua is not well suited for non-technical individuals.

My score is based on using Azuqua for static and repetitive actions.

Azuqua is great at collecting multiple data sources based on many criteria into a single FLO. It can process complex multi-team workflows in a single FLO.

Azuqua is well suited to allow non-engineers to manage system integrations. Azuqua can be hard if the integration gets too complicated. It was difficult to train users on the complicated FLOs we built.

If you have two applications that do not natively integrate, or have complex use cases that would not normally be handled by a native integration this tool is perfect.

There is a strong support team that will help you with understanding everything that Azuqua has to offer.

The integration I used Azuqua for was based on Salesforce, Wrike and Office 365. I found the integration of Salesforce reasonably straightforward, Wrike was limited in the "cards" capability but functional (there are bugs but there are also workarounds but they required assistance from the Azuqua support team) and Office 365 was quite immature (primarily around Excel bugs but also email was limited).

Azuqua is great at connecting Apps which do not have great native integrations. This is where they really shine since a developer does not need to create an API app. There is also no deployment overhead such as servers and software.

Appropriate: Any applications that expose API and web-services. There is no need to worry about coding languages that fit Web-service standards.

Not appropriate: Applications inside the firewall that needs to be exposed for Azuqua to connect. Or any environments that require on-prem installations

As stated earlier, our use case for Azuqua was very specific: We used Smartsheet forms to capture support requests, and used Azuqua to create cases in Salesforce from this data. For this, it worked flawlessly, though Smartsheet's limitation ultimately caused us to stop using it. Azuqua can connect lots of apps, but I cannot speak to where its limitations truly lie. For moving data from fields in one program to fields in another, it works great and is easy to use and maintain.

So often, when work is dictated by separate work process flows in different silos AKA - different TOOLS, an inevitable feature of any company, provided that there are API protocols for those different tools and your company Security IT allows it -- Azuqua can communicate between those separate databases to automate function triggers, alerts, and save your team the bandwidth to communicate office minutiae. Nothing is the perfect "Make it So" button, but Azuqua is something that gets pretty close in an imperfect world.

If you are looking for a quick way to link systems together then you should start by looking at Azuqua. The ability to quickly define your workflows and integrate the applications is second to none.

It is well suited to interconnect data between applications in the cloud only, then it depends on a reliable internet connection. For industrial applications, many of the companies have a lot of restrictions on internet access to the cloud.

Azuqua eliminates the need to have a company's own engineers build integrations for platforms that don't natively interact. This means being able to dedicate those resources to the business' core product and services, rather than towards third party systems. Because everything is automated it removes any sort of error and lag associated with human interactions.

for multiple app integrations

Azuqua has out-of-the-box connectors for every third-party vendor that we have been interested in supporting. They have even extended their connector builder to customers which has allowed us to build custom connectors to our homegrown applications. We really haven't found any scenarios where we haven't been able to accomplish our requirements.

Great for API to API integrations which are Event based.

Not so great for non API based integrations, and not the best at bulk data integrations. Bulk Data meaning you need something to run on all of your records every day.

Azuqua is great for getting data/information out of a more hidden/unexposed source and being able to push that data into a place that is widely used across departments or the company to allow for greater visibility and insight. It is not well suited for those who are trying to push data out of the internal database and do not have engineering resources to assist.

It is suited to track things that have multiple factors influencing it. It works well with more complicated KPI tracking requests. It works well with trying to aggregate things that move over space and time.

It is less appropriate for easier tracking items where Smartsheet notifications is a more straight forward option.

If you are using many difference cloud tools, Azuqua most likely can connect them.

Make sure to get IT security buy off to implement.

As a subcontractor, we have multiple construction projects going on at once with many more upcoming that need to be scheduled out. Azuqa helps keep track of start date and preconstruction documents required before a start of a project such as permits, submittals and safety documents. With so many projects going on, it can be difficult to track all the data that is constantly changing. Azuqa helps clear the clutter of multiple entries and unifies the data throughout the departments.

It is very well suited for agile, complex businesses that work across multiple cloud-based platforms, and want to automate their communication between their systems. It is not useful for server-based integrations.

Azuqua is extremely helpful for teams using Salesforce and their CRM along with other applications such as Gmail, JIRA, etc. It makes kicking off workflows and various events much easier to manage than by using Salesforce only. For new users Azuqua is a bit complicated to learn so if something needs to be built quick it is probably less appropriate.