Make vs. InterSystems Ensemble (legacy product)

Integromat is the best tool for business automation in my opinion because unlike Zapier it allows us to integrate with any API even if the app is not available which allows us to create automation even with the less known apps that we use or the ones that we built internally for our own company.

Incentivized

• Best suited for fast development with a fundamental emphasis on object orientation
• Prohibitive costs for very small integration projects

• UI/UX Simplicity and Features
• Workflows are explained in details and even people without IT background can use the tool.
• Consumption is nicely tracked.
• Myriad of existing templates, solutions, and readymade connectors.

• Easy to use: The simplicity of its programming language allows fast learning. Visual environment to generate complex code.
• Robust: A fall of the system will not be a problem. Never again will information of the transactions in progress be lost. Never more messages lost.
• Connect to the world: The most popular connection is possible to implement quickly. FTP, File folder, TCP, SMPT, REST.... all method are ready to use. Only define "where" and "how"

Incentivized

• There are always new platforms and connections that we'd like to see
• More flexibility in paying for operations (tasks) on a sliding scale, instead of by tier
• More thorough support documentation on connecting various platforms and troubleshooting errors

Incentivized

• Given that Ensemble and Cache are one of if not the only true fully object orientated database/development technologies for massive transactional data systems its customizability is extensive and it just comes down to the creativity of the developer to get the products to pretty much do whatever they want to do with it. However, this is not necessarily obvious to newcomers to the technology.
• The developer community could do with greater participation from the software developers/application specialists and engineers within InterSystems.
• More extensive documentation and greater access to proven working solutions particularly in the realm of some of the lesser known or new and upcoming technologies.

At this point, it is firmly embedded in the DNA of the business and to give up the ability to automate workflows and create integrations on the fly would be a terrible idea.

Make's easy to understand user interface helps you to visualize what's happening at all times. Could use some tweaks around the navigation from a scenario specifically in the folders and back navigations. I can't tell you the amount of time wasted in that area. When you branch, you can't bring a branch back together in the same scenario which is kind of a bummer as well.

Incentivized

The pricing schema is very attractive, almost 50% lower than the competition. You could start from free and then grow. It has a pretty big library of connections to other apps and services, which really helps you when everything is a mess. Integromat has a really easy-to-use interface. You could do almost everything with fewer than 5 clicks. Scenarios (automation steps to complete a routine) have graphics so you can configure them more easily.

Incentivized

I have yet to raise an issue with InterSystems WRC that they have been unable to resolve to my satisfaction in the 20+ years that I have worked with their products.

Integromat allows us to do everything we used to do on Zapier but it doesn't limit us to only the popular apps, with Integromat we're integrating custom APIs and we get data from different servers through GET requests and it's exactly what we needed and Zapier couldn't provide it.

Incentivized

Mirth is another integration platform that we have used but its development, in Java, made us always create new methods every time a new product was integrated. Every connection process had to be developed from the beginning and it was not easy to reuse code. Nor did it allow us to have an extensive catalog of HL7 messaging, having to perform the validation of each and every one of its fields manually.

Incentivized

• We used too many credits multiple times and had to buy them additionally, there are no prevention systems to setup to alert before it happens.
• Some consumption is difficult to understand and requires time and digging.
• It requires heavy internal effort to simplify things in Make in order for it to operate cheaper.
• Initial IT setup is paramount and determines a lot.

• We have integrated 5 laboratories in a treatment monitoring system in less than a month of development. Being able to integrate the following in a period no longer than a week.

Incentivized