SnapLogic

I have been using SnapLogic  for 12 years and it continues to run effectively. SnapLogic  serves as an integration platform in our IT application team to exchange data from one application to other applications and perform the transformations required if they are ever needed.

We have various types of sources. It can be SaaS applications and on-premise applications. Based upon the business requirements and other factors, we extract data from the various sources, either from the specific Snap Packs or through the REST APIs. Some applications generate files and place them on file servers. We use all methodologies, including SnapLogic Snap Packs, direct connectivity with those sources, or file-based integrations. We also use SnapLogic as an API. With the help of that, we extract all the data from the sources. We perform the business transformations wherever required as per the target system needs or the business requirement needs. Then we connect the target applications, either through dedicated Snap Packs such as Workday , Salesforce , Oracle ERP , SQL Server , any third-party applications, or SaaS applications if we have the Snap Pack. Otherwise, we use SOAP services, REST methods, or API-based integrations to connect the target applications.

We have ample and a variety of use cases. It can be batch-to-batch jobs, integrations, scheduled integrations, API-based integrations, and all these things. Currently, we are assessing SnapLogic API and features so that we can deploy all our existing APIs and build new APIs while having the complete API lifecycle management within our organization. Many of the use cases are API-based, and we need to be more secure about our APIs.

The best feature of SnapLogic is that we can access it through a normal UI with normal internet connections from the default Google Chrome  browser. As a developer, the low-code, no-code approach is a very good feature of SnapLogic. Additionally, SnapLogic has enhanced its existing features by providing SnapGPT or suggestions so that any new learner wanting to learn SnapLogic can quickly adopt this new technology and become very advanced in a lesser time.

SnapGPT is a feature we haven't actively used and we don't have that much of an active subscription for it. However, from what I know about SnapGPT, since we enabled it as a trial version after requesting it from our customer success managers, we have seen that it is good for very new learners who want to learn SnapLogic and cross-train in it. When I mention the low-code, no-code aspect, if you are doing any kind of transformations and routing your incoming data or applying filters based upon conditions, we have multiple options. If we have to route data to multiple destinations, we have the router Snap. If we have to apply conditional routing, we have conditional Snap Packs for that. That is why I prefer it as a complete low-code, no-code solution. That is a good advantage of SnapLogic.

Nothing major stands out regarding areas of concern. Since I started using SnapLogic approximately 12 years ago, at that time there were very few features. Nowadays, it keeps enhancing and continuously comes with new features and additional capabilities. That is a very good advantage. I think nowadays if any new learner and training people want to learn SnapLogic, it is very easy to adopt, comparatively to when we started approximately a decade ago.

SnapLogic definitely needs some kinds of improvements as per the current market and current AI world and current technology. At this moment, I can say there is one feedback on how SnapLogic can improve. There is a very small example: in SnapLogic, if we have to whitelist so many IPs, then you have to go one by one and add IPs manually. There should be some kind of a mechanism so that it can take input from any CSV files or something so that it can do bulk uploads. The IP whitelisting is the area that SnapLogic definitely has to improve. It is a bit painful because if you want to whitelist some Salesforce  IPs, Salesforce provides complete IP ranges that you have to go through manually. Sometimes if you mistakenly select something, then all your existing IPs that you have added are gone. I have faced this issue personally, so definitely SnapLogic has to improve in that area.

IP whitelisting is currently the top area on my mind for improvement. I don't think of any other areas that need improvement right now.

I have been using SnapLogic for 12 years and it continues to run.

SnapLogic is stable. Sometimes it is unstable, but I must say that is not completely because of SnapLogic. There might be some things that I am not aware of because I am still a learner. Even though I have been working in SnapLogic and managing all the infrastructure and administration for the last 12 years, I can say I am still learning and might be making some mistakes. However, sometimes we see that SnapLogic is unstable during patch releases or Snap Pack releases.

SnapLogic is known for its scalability. If you see the name SnapLogic called Elastic SnapLogic.com, you know what elastic means. That means you can stretch it any way and it works on the Triple-A platform. The Triple-A methodology means anything, anywhere, anytime. That means you can connect any system or application anytime, whether day or night, scheduled or dynamic, and anywhere, whether it is cloud or on-premises.

Customer support is good. Whenever we generate tickets in Zendesk , support engineers are assigned and they get back to us and follow up. However, if there is any kind of support required from the customer success support team, they need to evaluate and check with their internal engineering team, which takes time. Otherwise, I would not say that customer success support is not doing good. They are doing a very good job, and I definitely appreciate that.

I have worked on Informatica and Informatica Cloud, and sometimes I have used MuleSoft. We have also done some POCs with Dell Boomi . Broadly, I haven't extensively used Dell Boomi , as I was doing some POCs, but choosing SnapLogic was not my decision; it was the organization's decision. However, I have some other integration platform experience as well. I have worked on MuleSoft and Informatica and Informatica Cloud. Dell Boomi I have evaluated through POCs. However, we haven't done any full-fledged deliverables on it.

Definitely, there is money and time saved. For example, currently I don't have specific metrics to share. However, if you have seen the return of investment, currently I don't have any detailed information to provide.

The pricing model of SnapLogic is something I have a complete personal opinion about. I feel SnapLogic is very expensive compared to others. When I compare the cost from other applications or competitors, SnapLogic looks like a costly tool. However, it is meeting our requirements. Definitely, on the costing side, it's my personal opinion on what I feel. We have taken this solution, so it appears costly. Even though it is an organizational cost, it does appear that way.

I haven't much used the AI capability of SnapLogic, so I cannot comment on what the pros and cons of these AI capabilities are. However, any product using AI capabilities is using much better methodology and graph technology methodology to reach the actual requirements and concerns from the customer or users and drill down to the actual requirement so that they can give the best possible matching answers to the user.

It is a mixture of everything. We have some integrations running on the completely private cloud and many of the integrations that we have are on-premises. We are using on-premises Groundplex servers also. We are using SnapLogic cloud provider that AWS .

As I mentioned, we evaluated MuleSoft, Dell Boomi, and SnapLogic. On top of that, we recently evaluated one technology called Pentaho  for an integration platform. However, we found that SnapLogic is the best option currently on the market, so we have gone with it.

Customer support is good. Whenever we generate tickets in Zendesk , support engineers are assigned and they get back to us and follow up. However, if there is any kind of support required from the customer success support team, they need to evaluate and check with their internal engineering team, which takes time. Otherwise, I would not say that customer success support is not doing good. They are doing a very good job, and I definitely appreciate that.

I would scale things to eight, or between 8 to 8.5, on a scale of 1 to 10. I would definitely say that if they have some kinds of requirements, they should choose SnapLogic because SnapLogic is currently up to date and as per the current IT industry market and other factors, I don't think any other solution or platform is available in the current IT world which can meet customer integration requirements. My overall rating for this product is 9 out of 10.

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