IBM API Connect vs. Workato

I love the IBM API Connect features, performance, and security level for all our business data. The workload balancing and integration with other third-party products are very simple. The data migration speed is beneficial, especially for time management, and creating process reports through IBM API Connect is incredible.

Incentivized

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.

• High security with multiple types of authentication so no need to worry about security.
• API creation, automation and management all can be done form a single interface which guarantees security and increases efficiency.
• Highly rated among it's competitors which proves it has given a good service over the years.

Incentivized

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

• The first thing challenge we faced with the product was that if you deploying it to a third party cloud, that was very challenging and we need IBM team help at every step of the way and as well all know IBM support doesn't come cheap. A reason for that is that there isn't enough documentation done on the subject from IBM side.
• The upgrade process is not that seamless and involves a lot of hassles.
• You really need to have our requirements sorted out clearly because it is not very easy to customize the UI according to your needs, So you need to involve IBM from the start and give them clear requirements and then work with them to achieve it.

Incentivized

• 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

IBM API Connect may be less appropriate for small-scale projects with minimal API management requirements, where simpler and more cost-effective solutions suffice. Organizations lacking the necessary technical expertise or resources to harness its full potential may face implementation challenges. In static environments with infrequent API changes or limited developer engagement, the platform's comprehensive features may be excessive for the task at hand.

Incentivized

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 two main reasons for choosing IBM over others. 1) Pricing 2) The conversation during the sales stage. The team at IBM understood our requirements and acted as consultants instead of sales people. They genuinely focused on providing a solution to our pain points which reflected during the implementation and continued after go-live in the form of technical support

Incentivized

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.

• I consider IBM API Connect as a business capability enabler - the ROI level is practically secondary.
• With this platform at the core, associated architectural framework and guardrails ensure that we can progress with distributed development and automation in autonomous teams - a key factor to deliver required time to market performance.
• At this time, security and trust is key. A flexible yet secure API manager layer is necessary to ensure our relationships with partners and customers.

Incentivized

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