IBM API Management vs. Workato

If you are truly using IBM API Management for an API gateway, you will be ok. if you start trying to build custom scripts to transform messages complex in nature, it will soon become unmanageable.

Workato is brilliant to make separate applications work together without much effort or specialists being needed. When specific events on software A should trigger actions on B (or more) and you want that to happen without any development or big budgets, that's where Workato comes into play. It's a great help if you want tasks automated, communications flowing and data synced between different applications.

• Import APIs - We have an existing inventory of APIs and services, so having an easy import process was required. IBM provides the ability to import Swagger so the process was quick and easy.
• Service Offerings - Can create plans to control various model offerings for varying clients depending on the need. You are not locked into a tier structure and can customize if a need arises.
• API Usage - visibility into the use of an API with a wealth of reporting information allows you to support an API from a production use to trending and forecasting any future growth.

• The Workato product interface is brilliantly thought through and designed. The learning curve for first timers is easy enough to get started and build useful things, and Workato really shines in their ability to handle complex triggers and interactions. Workato allows people to build software apps so much faster than by coding each functionality.
• Workato has fantastic documentation, making things accessible without any holes in the product. The product just works, never has any bugs, never lags, and just generally allows us to see and change exactly what we need to.
• Workato has an absolutely amazing support team. We tried the free version for a while, then realized it was the single most important software tool we have, and we upgraded. The support at the paid tier is A+, seriously the best from any company we've worked with. Feels more like a good friend then a support rep.

• Troubleshooting deployment pipeline - identifying issues with your api based on restrictions through a deployment pipeline is difficult. If a quality assurance environment is less stringent than a production environment, making sure your api is accessible and configured appropriately is tough.
• Code level scripting is limited to javascript and xslt. so if any complex fanning needs to occur, you are limited in tooling.
• Administration is more cumbersome than it needs to be. There are roles/profiles that are defined, but to use a group email for the approval or use of an api needs to managed better. A more thorough thought process needs to be defined - which I think IBM is tackling as an improvement.

• Customer support - responsive, but often not equipped to help efficiently identify root cause of issue. Need to improve escalation to technical resources and turnaround time
• Recipe organization and sharing. Can be challenging to copy recipes, or grab recipes from publicly available site. There are often dependencies and errors that have vague descriptions.

Incentivized

We need to develop Enterprise Application Integrations and Workato was not designed for this

Due to prebuilt recipes, Workato is easy to learn and use for non-technical users if their use case fits the existing recipes. It is not easy for non-technical users to create, modify, debug or maintain complex integrations that are outside the prebuilt recipes.

They employ an extremely knowledgeable team of problem solvers. I've never had a disappointing interaction or one that has left me still searching for answers. I know that when I ask for help, they'll partner with me until we find a solution together

Incentivized

We discovered that we could not use Workato for our more complex, large enterprise integrations. It was useful for simple workflows that matched the prebuilt recipes.

There are a lot of similarities between Apigee Edge and IBM API Management. Some of the differences at the time of this posting is... 1) IBM APIM/C integrates better with other products. Dynatrace is used to track API and service specifics with the ability to offload those statistics for operational reporting. 2) If you are evolving from DataPower, IBM API Management is a logical choice to support additional REST APIs. 3) Generating keys is simple. Integration of those keys with a secure data vault is easy as well for your consumer.

We already used Zapier, but since it doesn't support NetSuite we had to choose another automation platform. Now that we've been using Workato for a few months, we have plans to move the stuff we're going through Zapier to Workato. We set up a trial account with all the other platforms, and they were all more expensive and A LOT more complicated than Workato.

• Centralizing on an API management platform was imperative. Being able to support SOAP UIs as well as REST APIs was required. Because of the tooling, service inventory and provisioning can be managed - regardless of the pricing and cost structures are used.
• Constructing plans that provide tiering options based on rate limits help in onboarding new consumers. The lesser cost in onboarding through an API gateway outweighs the cost of modifying/configuring an API to handle multiple clients.
• Defining guidance and onboarding practices while rolling out the product also helps in the adoption, reference architecture, and governance that can save your company money.

• As business consultants, Workato has greatly improved our offerings to our clients as well as improved the time frame to implement automated workflows and integrations.
• For our clients, the return on investment is almost immediate. Once a Workato recipe is up and running (which can be done very fast), data is integrating, duplicate data entry and user errors are eliminated, and cross-company KPI metrics are easier to report than ever.