Tidal has a lot of adapters. We use the SQL adapter. We use it to connect to an iSeries. We use it to connect to FTP. We use it to connect to all of our Windows servers. I know there is an agent for ServiceNow. We don't use that yet, but one of our future plans is to use it. We have JD Edwards ReportsNow that, instead of using ReportsNow scheduler, is using Tidal for scheduling jobs and reporting. The power of Tidal is the fact that I can have one scheduler to schedule everything. I don't have to have a scheduler on each one of these systems. I can, but then I have to maintain it on all of those systems, whereas having it on one and being able to control everything makes integrations a lot easier where I can stop processes, do patching, and bring processes back up. If it is all in one system, it is nicer and easier to do.

Tidal integrates with and connects to different systems to run the different jobs and it does that very well. There are connections from Tidal to SAP ECC, the warehouse management systems, et cetera. Not only does it do a great job running the jobs, but we get very valuable information back into Tidal about the health of a job.

If you have familiarity with APIs, it's a matter of just looking over the documentation and understanding Tidal's way of using the API, and then you can build integration with PowerShell scripts. That's something we're doing with the Cherwell integration to bring out data from Tidal into Cherwell.

I've used Tidal Automation to connect and integrate with a lot of different software and systems. I've used PeopleSoft, Informatica, BI, SQL Databases, VMware, Azure, and others. I haven't had any issues. So far, everything has been great. They have a compatibility matrix that ensures that different versions of Tidal will work with different software. They're good about keeping that up to date.

It is easy to integrate other technologies and processes via the REST API. All you need is access and a log-in ability, and it integrates well. You don't really need to do a lot of configuration.

We have never needed to use the REST API. The plug-ins provided by Tidal gives meet our integration needs completely. It integrates perfectly with our ecosystem, whether it's SQL Server, Windows, or our ERP.

We use Tidal to connect to other resources and systems, through many of its adapters, such as for S3, ServiceNow, and PeopleSoft. We use it to trigger jobs in those applications. The REST API is very easy. Our application users use it to create, rerun, or canceling their jobs. And if they want to update something in the database, they do it with the REST API. It's a good feature.

We use Tidal to connect to other resources and systems, through many of its adapters, such as for S3, ServiceNow, and PeopleSoft. We use it to trigger jobs in those applications... That direct integration to our applications means we don't need to do other integrations from other applications or create scripts for these integrations. The multiple adapters available for connecting to other software make it easy for users to use the solution.