SnapLogic

Our main use case for SnapLogic  is building and managing data integration pipelines between different systems, especially for automating API-based workflows. It helps streamline data movement, transformation, and orchestration without heavy manual intervention. For example, in our day-to-day work, we use SnapLogic  to integrate data between internal systems and external services. The typical pipeline involves fetching data from an API, transforming it based on the business requirements, and loading it into another system or database. This automation reduces manual effort, ensures consistency, and allows us to handle updates in near real-time.

In addition to core data integration, we use SnapLogic for workflow orchestration and monitoring. It helps manage end-to-end data flows with better visibility, error handling, and retries. We also leverage its reusable pipelines and connectors to standardize integration across teams. This reduces development time and ensures consistency, especially when working with multiple APIs and systems. Overall, it plays a key role in making our process more efficient.

One of the best features SnapLogic offers is the intuitive drag-and-drop interface, which makes it easy to build and manage pipelines without heavy coding. It also allows both technical and non-technical users to quickly create integrations. Another key strength is the wide range of pre-built connectors that help integrate multiple systems, APIs, and databases seamlessly. I also find its scalability and real-time processing capabilities very valuable. It can handle larger volumes of data and supports both batch and real-time integration, which is very important for building reliable and responsive data pipelines.

The drag-and-drop interface has made my work much faster and more efficient by simplifying how pipelines are built and managed instead of writing complex code. I can visually design workflows by connecting different components, which reduces development time and makes the logic easier to understand. It is also very helpful for debugging and maintenance. I can quickly identify whether a pipeline is working or failing, or make changes directly in the flow and test updates without much effort. This visual approach improves productivity and makes it easier to collaborate with team members, especially when explaining or modifying integrations.

SnapLogic offers strong support for automation and scheduling. It allows us to schedule pipelines or trigger them based on events, which is really useful for building fully automated workflows without manual intervention. Another valuable feature is its built-in error handling and retry mechanism. Instead of pipelines failing completely, we can design flows to handle exceptions gracefully, log issues, and retry where needed. This improves reliability in production. The reusability of pipelines and components is a big advantage. We can create modular pipelines and reuse them across multiple use cases. This saves us time and keeps everything consistent and scalable.

The learning curve for advanced use cases with SnapLogic could be improved. While basic pipelines are easy, more complex transformations and debugging can still be a bit challenging. Another improvement would be in error messages and debugging clarity. Sometimes the errors are not very descriptive, which makes troubleshooting take longer than expected. Performance tuning and visibility can be better for large-scale pipelines, as having more granular control and deeper insights into execution performance would really help.

One improvement would be version control and collaboration. While SnapLogic supports reuse, tighter integration with better change tracking would make team collaboration smoother, especially in larger environments.

I have been using SnapLogic for around six months to one year as part of my integration and automation work.

SnapLogic is very stable in my experience.

The scalability of SnapLogic is very good, especially since we are deploying this in a hybrid cloud. The Groundplex nodes are performing very well, and we are connecting to the API through our local SnapLogic portal. Overall, when it comes to scalability, SnapLogic performs very well.

I raised a couple of tickets with SnapLogic's customer support. We faced some technical challenges, but the experience went very well. I can rate SnapLogic customer support nine out of ten because they are very interactive and helpful.

SnapLogic is our first solution for this purpose.

We have seen the return on investment with SnapLogic. The time savings and the productivity of the engineers across our team have improved. It improved our productivity by fifteen percent and shifted work from IT to business users. In terms of cost savings, it has also reduced costs by seventy to eighty percent. The case studies indicate that we are achieving a good percentage of ROI.

SnapLogic follows a subscription-based pricing model, which is quite flexible but can feel premium depending on the scale. Pricing is usually tiered and customized based on factors such as the number of systems, data volume, and features required, so it is not always straightforward upfront. In terms of setup cost, it is relatively low compared to traditional on-premises tools. Since it is cloud-oriented, it does not require heavy infrastructure investment. This makes initial onboarding faster and more cost-efficient.

I recommend that instead of going to the Groundplex node, teams use SnapLogic for SaaS-based solutions because running the Groundplex node creates additional operational overhead for the team. To go better and smoother, it would be very good if teams use SaaS that has strong resilience compared to hosting it on-premises. Overall, SnapLogic is a very good tool. From the practical standpoint, it delivers integration quickly, reduces manual work, lowers dependency on multiple tools, and improves team productivity. It has helped us to move faster. I would rate this product an eight out of ten.

I am using SnapLogic  to monitor pipelines and also develop pipelines, and to make enhancements in the pipelines to extract data, transform, and load it into our target tables.

One of the pipelines which I developed recently is part of a transition project transitioning from Informatica PowerCenter  to GCP Cloud. The target tables in our previous pipelines were almost all related to Informatica and were loading the data into Oracle SQL Developer , but we are changing and transitioning them into GCP BigQuery , so these are the few developments which I have done recently to the pipelines.

During the transition, we are using two ETL tools: Informatica PowerCenter  and SnapLogic . Compared to Informatica PowerCenter, SnapLogic has a very good user interface where I can easily drag and drop the Snaps to create the pipeline, making it comparatively very easy to use than Informatica PowerCenter.

The best feature SnapLogic offers is the Snaps, which are the inbuilt Snaps from which I can easily create a pipeline within minutes and then easily deploy it.

With the inbuilt Snaps, if I want to connect a pipeline to an Oracle server, extract a SQL query, and at the final step, send a mail to business users, all these steps can easily be done within ten minutes with the use of these inbuilt Snaps.

Since I moved on to SnapLogic and development started in SnapLogic, the development team has been reduced to half, and the amount of time which we are using for development is also reduced. Approximately, I can say that when we were using Informatica PowerCenter, it used to take more than one hour to develop a workflow by creating mapping and also the sessions, but since I moved to SnapLogic, the same pipeline can be created within ten to fifteen minutes.

The organization has been impacted positively with the change made to SnapLogic. The cost saving is that comparatively, the number of people was reduced in the project, so the cost has been reduced for our project, and the amount of time has been reduced to more than half, from hours to minutes for the development team. It also improved productivity because of the user-friendly nature of SnapLogic, and production also improved with less missing data. If there are any enhancements or changes needed, I can easily make them in SnapLogic.

One thing is that if there is any error, it is not detecting the error directly in the main pipeline. Rather, I have to backtrace to the child pipeline and then go to the designer and check the error. If it were possible to show the final error on the monitor itself, it would be easy to debug.

The interface is fine, and everything is fine, apart from the error messaging.

I have been using SnapLogic from the past eight months.

I have never experienced any server crash or node crash in SnapLogic.

SnapLogic is easily scalable. Recently, I have also increased the data memory of SnapLogic IPAS, and before or after the scalability, I have never experienced any crash.

The customer support is fine. I have never contacted the customer support, but I have gone through the documentation, and I can easily understand from the documentation what steps are needed to rectify any error.

Previously I have used Informatica PowerCenter, but right now I am transitioning to SnapLogic and GCP BigQuery  because of the pricing factor and also the features provided by SnapLogic.

The return on investment is positive because the development team has been reduced to half when I switched to SnapLogic. This is because of its easy user interface and how the inbuilt Snaps are already developed in SnapLogic, saving us a lot of money for our project. A same development which used to take one hour in other tools is taking less than one hour and has been completed in SnapLogic within minutes, so it has saved us time. On the metrics level, I can say that it saved us almost two to three hours per day. Additionally, the number of employees has also been reduced from approximately ten to five people.

I have evaluated other options like Informatica PowerCenter and also GCP DAGs. Later, I came to the conclusion that SnapLogic would be a good fit for our organization.

A person with minimal knowledge on ETL can easily go through SnapLogic and understand what each Snap does, what the function of each Snap is, and then simply drag and drop and make the connections to create a pipeline. I would also advise them to go through the documentation before they develop any pipeline. I would rate this product an eight out of ten.

I connect system to system, and sometimes I do applications to applications as well. When required, I build some APIs in SnapLogic  and expose them to customers.

From a general automation perspective, when a business wants to automate a particular use case, it can be anything. For example, tickets are getting created in ServiceNow  where I need to automate the ticket creation with the information I receive back to Jira  or something similar. I connect with systems such as ServiceNow  and Jira  and automatically create an automation workflow that connects these two systems to make the process automated, which saves manual effort.

I work on many use cases across different domains, such as HR, sales, and many other domains. I use SnapLogic  in the regular way, as it needs to be used.

From an impact perspective, SnapLogic really helps me as a middleware level platform. It helps me to automate many integration workflows. As for improvements, the monitor that I currently use sometimes gets stuck and I am not able to expand and view the child pipelines in a much easier way. On the monitor part, I can do some fine-tuning, which would help the developer, citizen integrator, or any support person easily monitor the pipelines and easily access the pipeline logs. That would be very beneficial. There are also many other areas that I can work on where I see that these areas would be beneficial for a larger group and I can try to implement those points.

I cannot share the exact numbers or percentage, but I can say that SnapLogic has really helped my team in saving time because due to this automation, I do not need to do the manual activity. The person's effort is saved, the time is saved, and many other things are improved. Due to this automation, I see better results compared to the manual ones because the logic I have added to the automation is more specific and more static. Sometimes when I do it manually, I might end up making some small errors, but as I have built it as an automation workflow, there will not be any minor issues. This is considerably a good time-saving solution.

The best feature is that it is easy to use because it provides a UI level and drag and drop options, which are simply easy for anybody to kickstart and use much easier compared to some complicated ones.

Another valuable feature is that SnapLogic has been providing more connectors, which means more Snaps when compared to the past. This gives developers or citizen integrators the ability to connect various new systems or applications as well.

For new users who have started to explore SnapLogic, they can simply understand from the name what each Snap does. For example, file reader and file writer make it clear what the exact functionality will be. The catalog provides easy drag and drop and connect capabilities. The AI assistant helps me with some examples referring to what the next Snap I can use will be. This kind of additional feature benefits the new users who are going to use SnapLogic for the first time. This adds ease to their experience.

I use many features and I feel they are good. SnapLogic is compatible in many areas and provides better features when compared to other integration tools.

One area would be improving the monitor. Another few things I would mention is that I would like better logs to debug in case of any issues, other than just understanding from the pipeline statistics level. I would appreciate some additional logs where on a need basis, I can enable the slots and the traces will be available at the server level so that I can capture the end-to-end what is happening, such as request, response, and things. This feature would be really helpful at the time of critical P1 issues, which I can use.

As I mentioned earlier, with few corrections in the monitor and logging and few other areas that I correct and improve, SnapLogic will be much more scalable than others. This is the reason I have given this rating.

I have been using SnapLogic for around 7.5 years.

For reusable ones, I am building some pipelines where I am actually using the reusability concepts. Performance-wise, it is completely based on the server setup that I have. This is something based on the business use case or based on the business I will be thinking it and putting up the server capacity. Performance-wise, I do not see any issue.

I have been using SnapLogic from the beginning.

I would say time saved.

As of now, nothing.

I would suggest that if someone is looking for data integration, application integration, and API building in one tool, then SnapLogic is one of the options which they can give a try.