SnapLogic Reviews

I have been working in the integration space for more than 10 years, starting my career with SnapLogic, which is a good iPaaS tool for integration. Even taking a look at the market caps, SnapLogic is doing very well.

In any organization when an integration requirement comes, whether it is an on-premises to cloud connect, or whether it is any kind of migration or grabbing data from SaaS tools such as Workday, NetSuite or Salesforce, SnapLogic is a best fit in the market. It has lots of pre-built connectors called Snap-packs, which come pre-built with SnapLogic licenses, so you can make use of all those together. This is the main use case that motivates us to use SnapLogic. There are so many features, and from the user perspective, it is very user-friendly. It is a low-code, no-code platform that can be used for any integration use cases.

I recently completed a Workday migration project. Hitachi wanted a Workday system to be a single source of truth across all Hitachi organization and sub-organization. There we got a use case to integrate the Workday system with all the downstream systems, whether it is for HDS or Hitachi Digital Services, Hitachi Vantara or GlobalLogic. SnapLogic was used in that case. There are so many inbound and outbound integrations, and we integrated two or three kinds of authentication to pull out data from Workday and also to send out any kind of inbound data to Workday. This was our main use case and it was a very big project in Hitachi Digital, the Phoenix project, and all those implementations happened on SnapLogic.

I can also mention that we recently built a professional service automation with the help of SnapLogic, which is the integration between Salesforce and Oracle ERP system, Oracle HCM system, which is used for the HR system in GlobalLogic. Lots of insourced data are brought to the Salesforce platform so that they can tag the right resource to the right project and they can also check the utilization. Professional service automation is a kind of automation that will tag the right people at the right skill set on the right project. For all those to achieve, we used SnapLogic to integrate between Salesforce and the Oracle system.

There are so many strengths of SnapLogic. The first one is that it is user-friendly. It is a low-code, no-code platform where you can drag and drop the Snap-packs. SnapLogic's visual drag-and-drop interface makes it very easier for the developers and integration teams to build any kind of pipelines that require very minimal coding.

There is an extensive connection library. SnapLogic's iPaaS platform offers a large collection of pre-built connectors, called Snaps in SnapLogic. This will always simplify integration with cloud applications, whether it is a cloud application or whether you have to connect with any kind of on-premises application or enterprise system. Deployment and development are very fast in SnapLogic compared to traditional coding approaches such as creating APIs via Python and streaming on some other platforms. You can create your pipeline and deploy it with the help of API management, which reduces the time for any developer. It also has strong cloud integration capabilities.

SnapLogic has the Ultra feature and API management as features. Enhanced account encryption is there, where all account credentials are well encrypted at the backend of the platform. SnapLogic has become a valuable component of our integration strategy in the market, in the India region, APAC region or in the US. Monitoring is also very easy with operational visibility provided through central monitoring in the monitor tab of SnapLogic. Maintenance effort is very minimal, and well documentation is provided. You can refer to any of the Snap documentation if you want to see anything.

Earlier, the organization was following a manual approach. Five years back, they were following a manual approach. Once SnapLogic came into place, there are so many characteristics where some individual teams are using Salesforce, Workday, or different enterprise systems. SnapLogic provides a consolidated platform where we can integrate all the data and share it with the team. We have built lots of automations for our current organization, which is reducing very manual effort. Earlier manual effort was more, but now all the things are automated from one system to another system. Anytime, anywhere, anything if any team wants, we can send that data.

Earlier we were having three to four resources in each individual team taking care of these things, but with the help of automation, everything is automated. The platform team is also doing very well, releasing updates every quarter or every month. They recently released version 4.44. So improvement wise, they are doing very well.

They can enhance the error handling and debugging part. Troubleshooting complex pipeline failures can be time-consuming. We are spending a lot of time on error handling. More detailed error messages and root cause analysis tools can be added, which will definitely improve the developer experience.

In the Ultra real-time integrations, we can monitor the last execution history of only 100 runs. That can be increased, which would be one of the platform improvements that can really be taken. However, they are doing very well because lots of ChatGPTs and AI assistants have been added in the last two years, which makes a very good effect.

SnapLogic is the only platform that provides this kind of visibility to the developers. Anyone, even if they have low experience and are starting their IT careers, can directly jump in and learn SnapLogic. The documentation is very easy to learn. Anyone, even a layman, can refer to that documentation and go through its Snap-pack to understand what configuration has to be done to use this Snap-pack. This makes SnapLogic definitely exceptional in the market. You won't find such comprehensive documentation in other iPaaS tools. The draggable packs truly demonstrate its power in usability.

Governance and security are also well in place in SnapLogic, but there are areas for improvement. They can add more granular role and permission controls that provide greater flexibility for large enterprises. For example, if you have to provide access to 70 users in one shot, that can be improved. More improvements in policy enforcement capabilities are possible as well.

SnapLogic can improve the data lineage part to achieve better end-to-end visibility into data movement. Also, during validation, we can only see up to 2,000 records currently. They can increase that from 2,000 to 20,000.

They can put more visibility on costs and resource visibility, with better reporting on platform usage, processing consumption, and cost optimization opportunities.

I have been using SnapLogic for more than 10 years.

SnapLogic is stable.

SnapLogic has many strengths in terms of scalability. It handles growing data volumes and you can process numerous volumes as per business needs. When expenditure expands, such as when the business is expanding and the number of employees increases, there won't be any effect on integration. It supports enterprise-wide integration and has a cloud-native architecture. Everything is on the cloud, and you don't have to worry about platform maintenance. Hybrid and multi-cloud support is there, with many reusable integration assets. The throughput is very high in this platform.

Overall, combining all those things, it ultimately supports business growth. New applications, data sources, and business processes can be added without major architectural changes. If you need to deploy your on-premises application, you can. If you need to use cloud-to-cloud connectivity, you can go to the cloud architecture, but all are in a single place. You just have to log in to elastic.snaplogic.com, and your entire solution is there.

Gyan Solution is the organization that provides customer support. When we create any ticket in Zendesk, they quickly respond. If their development team is needed for some assistance, they coordinate very well from the US to India, because Gyan Solution is in India, Hyderabad, and the complete core development team is in the US.

They are providing the best customer support to the organization and the vendors. Whatever they do, they keep you informed over the ticket in Zendesk every minute. They are also very good in follow-ups; if you are not responding for eight weeks, they will follow up with you, and after your confirmation, they will close the ticket.

I checked Boomi in my free time and in my previous organization. I found it complex to use as an iPaaS platform. Whatever the connectors, there are more than 600 connectors SnapLogic provides, and you won't find such a variety in Boomi and MuleSoft. That was the biggest motivation to switch. The development approach is very easy in SnapLogic. After comparing these platforms, we realized SnapLogic is the right solution for us. In the previous organization, they switched from Boomi to SnapLogic.

I checked Boomi. I don't find that to be a fitting enterprise solution for the market. That's why we opted for SnapLogic. It also has a complete central API management platform, so data integration and API management can both be done in SnapLogic. With one solution, we are achieving two goals.

Earlier there was a manual approach. When we came to the organization, we suggested that this is the platform you can utilize as an integration architect. Looking at the time consumption, we have saved 50 to 70% through the low-code platform. We have created so many reusable components where we don't have to spend the time. We can simply go and use them. The onboarding part is also faster for new applications because there are so many connectors you can use. We don't have to spend time on quicker troubleshooting and centralized monitoring, which reduces issue resolution time. Suppose there was an issue resolution time of 10 hours for the previous manual effort; now it is reduced to one hour or half an hour. The business team can also deliver integration projects in days or weeks instead of months. We have saved manpower, reduced months of effort, and created many reusable components, which definitely leads to cost savings. We see a 60% reduction in integration development time, a 40% faster onboarding process of new applications, and a significant decrease in manual operations through workflow. This is quantified.

We save time because there were so many manual efforts happening. With the introduction of SnapLogic, we have automated all the processes in Hitachi and GlobalLogic. Those kinds of manual efforts and manpower savings have definitely been reduced.

Based on my research and integration career, I have seen many products such as Workday, MuleSoft, and IBM MQ. After analyzing all those and lots of implementations, I found SnapLogic as a very useful and user-friendly integration tool.

In the overall comment in the integration journey, I have worked with many vendors and organizations. SnapLogic has been a valuable integration platform for every organization. It's not only for those who are using it but also for those who are not using it. If they will analyze their infrastructure or system, they will see this is the right platform for integration. It enables faster development, improved automation, and seamless connectivity. It supports on-premises applications, cloud applications, and Salesforce. The low-code, no-code approach, extensive connector options, and AI assistants such as Snap, Iris recommendation, transformation recommendation, and mapper recommendation, all contribute to improving operational efficiency for every organization using it. Those who are not utilizing it definitely need to evaluate, analyze, and compare it with their systems.

DevOps capabilities such as CI/CD implementation, integration with GitHub, GitLab, everything is provided. SnapLogic is a robust, scalable, and user-friendly platform that has helped us to reduce development time, automate many business processes, and support enterprise growth, especially with low-code, no-code capabilities and broader connector options, more than 600. I would rate this platform a 9 out of 10 overall.

My main use case for SnapLogic is integration and automation, where it connects different systems, applications, databases, and files so data can move automatically between them.

A company's sales team uses Salesforce to create customers while the finance team uses SAP for billing and the support team uses a ticketing system. Previously, whenever a new customer was created, sales emailed finance, finance manually created the customer in SAP, and support manually set up the account. Errors and delays were common. SnapLogic helped by building an automated pipeline where the trigger was when a new customer was created in Salesforce. SnapLogic automatically validates customer data, creates the customer in SAP, creates a support account, sends confirmation emails to stakeholders, and logs everything for audit. This resulted in reduced onboarding time from one to two days to a few minutes, eliminated manual data entry errors, improved customer experience, and saved operational effort.

Another example of SnapLogic usage in our organization is automating daily sales reporting instead of manually downloading and merging data from a POS system. The pipeline automatically extracts, transforms, and distributes reports every morning.

The key benefits we gained from SnapLogic are improved operational efficiency, reduced errors, faster system integration, better visibility and monitoring, and scalability and flexibility. Implementing SnapLogic helped us automate key business processes, reduce manual effort, improve data accuracy, and accelerate system integration, which resulted in improved efficiency and cost savings.

We reduced manual processing effort by 40 to 60%, approximately 15 to 25 hours per week, and reduced dependency on custom integration development, which saved contractor costs. The estimated annual savings are around 50,000 to 150,000 USD, depending on team size.

We reduced the process turnaround time from one to two days to under one hour and automated a daily report that previously took two to three hours manually. We accelerated system integration by 50%, and we reduced manual data entry errors by 70 to 90%, improved data accuracy to 99% plus consistency, and reduced issues by 40%.

The best features in SnapLogic are the drag-and-drop interface which makes it easy to build data and application flows. No heavy coding is required, making it ideal for both technical and non-technical users. SnapLogic also offers pre-built snaps, real-time and batch processing, API management and integration, cloud and hybrid support, dashboarding and monitoring, error handling and retry mechanisms, scalability, security and governance, and transformation capabilities with built-in functions to clean and transform data, expressions, aggregations, and mappings.

SnapLogic offers auto-mapping and smart schema detection as additional features. SnapLogic can detect schemas automatically, which helps when sources evolve or change, and this matters because there is less manual mapping work.

I find the learning curve for complex transformations, the debugging experience, performance optimization visibility, cost for small teams, and version control and DevOps integration could be improved in SnapLogic.

The improvements needed for SnapLogic include expanded AI agent support, SnapGPT or prompt user enhancements, improved monitoring and observability, expanded connectivity and snaps, Git integrations and DevOps improvements, and platform APIs and automation.

I have been using SnapLogic for six years.

SnapLogic is stable.

SnapLogic is designed to handle growing workloads and complex enterprise integrations without major changes to the infrastructure. Its elastic and distributed architecture handles large data volumes and has multi-environment support. A real-world example in our organization shows that after implementing SnapLogic, pipelines that processed one to two million records per week can now handle five to 10 million records without additional infrastructure, allowing us to scale data integration as business needs grow.

Customer support is excellent in my experience. The responsiveness, technical expertise, knowledge base and documentation, support channels, and continuous improvement were impeccable. Support responded quickly to high-priority issues, and the technical team helped troubleshoot integration problems efficiently. The documentation and community resources assisted in resolving routine questions without waiting for tickets.

We used legacy ETL and integration tools, such as Informatica and custom scripts before SnapLogic. While they worked, they had limitations such as long development cycles where building and modifying pipelines took much longer. There was limited cloud support, and it was difficult to connect cloud apps and hybrid environments. Manual maintenance, error handling, and monitoring required more effort. We moved to SnapLogic because it offered a low-code visual platform, pre-built connectors for cloud and on-premises systems, real-time and batch processing, and better automation capabilities, allowing us to accelerate integration, reduce errors, and scale efficiently.

SnapLogic uses a subscription-based pricing model based on the number of pipelines, environment type, and number of connectors or snap packs used. The setup and deployment costs for a cloud deployment involve minimal hardware costs, only subscription fees, and a quick setup. On-premises or hybrid costs include Snaplex node setup, VMs or servers, and network configuration. Initial setup includes pipeline design, snap installation, authentication setup, and integrations. Licensing is per environment or per runtime node or Snaplex, and snap packs and connectors may be included or licensed separately depending on the plan. The AWS Marketplace option allows purchasing a SnapLogic license through AWS billing, simplifying procurement.

SnapLogic's pricing and licenses are flexible and scalable, supporting both cloud and hybrid deployments. While initial setup is straightforward in the cloud, on-premises or hybrid deployments require more planning and investment. The subscription-based model provides predictable costs, but organizations should evaluate the number of snap packs and runtime nodes they need to optimize licensing costs.

We have seen a 50% reduction in manual data processing and a 70 to 80% reduction in data entry or integration errors.

The reports and pipelines run, leading to cost savings that reduce manual effort and save 50,000 to 150,000 USD annually. SnapLogic handles a 3 to 5x increase in data volume without extra resources. SnapLogic delivers measurable ROI through time savings, 70% fewer errors, faster processes, and significant cost reductions while enabling scalable automations across our systems.

Before selecting SnapLogic, we evaluated several other integration platforms, including Informatica, MuleSoft, and Dell Boomi. We compared them on key criteria such as ease of use, pre-built connectors, real-time and batch processing capabilities, scalability and performance, total cost of ownership, and licensing flexibility. SnapLogic stood out because it offered a visual low-code interface, strong hybrid and cloud support, and fast deployment, which allowed us to accelerate integrations and automate workflows more efficiently compared to the alternatives.

SnapLogic is a flexible low-code integration platform that connects cloud and on-premises systems, automates workflows, and reduces manual effort. Organizations can benefit from faster integration delivery, improved data accuracy, and scalability.

My detailed ratings are as follows: ease of use score of eight, integration capability score of nine, automation efficiency score of nine, data accuracy score of eight, performance score of eight, API cloud score of nine, monitoring score of seven, learning curve score of seven, and cost or ROI score of eight. I rate SnapLogic an eight on a scale of one to ten, with an overall satisfaction average of eight. SnapLogic is a very effective platform, and small improvements could make it even better.

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.

My main use case for SnapLogic is that we primarily use it for data transformation, ETL pipelines, file generation, and sending extract files to our external vendors.

I can give you a specific example of how we use SnapLogic for one of those tasks. Every day we receive claim files from our primary vendor and we load those using SnapLogic and transform the data accordingly to match our database schema. After the files have been loaded, we send out many different extracts to different vendors depending on their needs, and all those extracts go through SnapLogic.

I have more to add about my main use case and how SnapLogic fits into my workflow. We also use SnapLogic scheduled tasks for many of our processes. Some of those are daily and some of those are monthly, but we enjoy using SnapLogic to schedule those tasks out accordingly. It has helped significantly with organizing those different scheduled tasks and keeping us on track with different deliverables for several vendors that we have.

Almost all of our data transformation process and file extract process goes through SnapLogic. We have a ton of our infrastructure set up in there and I would say it is extremely important for our processes. It would be very difficult to switch away from it because of how we have set up everything with their scheduled tasks and how we are all used to their infrastructure and their UI. We all really enjoy it. It is very simple to set up tasks for reading, transforming, and extracting data, formatting files, and sending things to Amazon S3 or other delivery locations. It has simplified things greatly, especially having the visual UI to see how the data is flowing through the pipeline. This makes things a lot easier compared to setting that up in code alone. My whole team and I really enjoy that visual aspect of the data transformation process.

SnapLogic has specifically helped my team save time and resources. As I mentioned, we have a lot of our infrastructure set up in there. I would say we probably have 150 pipelines. Setting all of those processes up in code alone would be quite an undertaking and I believe there would be significantly more infrastructure and maintenance set up around those pipelines if we were to do it in code alone. Having everything stored in SnapLogic and having the visual aspect of it really helps us keep things in a central location. We can all see how the data is flowing much more easily and it is really easy to make edits and drag and drop things. Out of those 150 to 200 processes, having all those in SnapLogic makes it a lot more organized and a lot easier for new people on the team to drop in and get the hang of things quickly.

One of my favorite features SnapLogic offers is how many pre-configured Snap Packs and Snaps are available for lots of third-party integrations. For example, we use a lot of AWS services and we have a lot of different database connections and APIs that we call. We use their wide selection of pre-configured Snaps to help us build out those much faster. That makes things a lot easier. Another one of my favorite features of SnapLogic is how easy it is to monitor pipeline executions. Their Monitor app is very useful to see things that are running, things that have failed in the past, and upcoming tasks. I use their monitor app quite a bit for pipeline debugging.

Out of the features I mentioned, I rely on their Snap Pack and their pre-configured Snaps a little more often day-to-day than the Monitor because we do not always have pipelines failing, but I am always working on building new pipelines or editing old ones with their Snap Packs. I know that they have many Snap Packs that we have not had a chance to use yet. For example, their up-and-coming AI ones. We have been chatting with their team about it, but we have not integrated them into our workflows very much yet. In addition, their Patterns feature is also important to me. We typically copy and paste old pipelines more often than using their pre-built patterns and I would appreciate spending more time looking at those to see how they could help us speed up our pipeline development.

I am impressed with how they are pushing forward with AI integration in their pipelines, particularly with their Snap GPT, which has become increasingly useful to us. Aside from that, their team regularly works with my team on calls to walk us through their new AI tools and see how we use them and how they can improve. I am very excited about many of their new AI features, and I am impressed with how they are being very communicative and pushing that forward with our help.

There are a few ways SnapLogic can be improved, as there are some UI quirks that I have personally noticed. For example, we use a lot of SQL queries in our Snaps. Sometimes they are very long and complex, and it is a little difficult to work with the SQL text files in those Snaps because they do not have a lot of text editing capabilities. They do not allow you to add new lines or line breaks of any kind, so often I end up using another text editor and pasting long text snippets of SQL queries into the Snap. That is a little frustrating. In addition, I would say they are going through, or they might be at the end of, a pretty significant UI overhaul of their designer app, and there are still some issues occasionally or buggy behavior when you are dragging segments of pipelines around. Sometimes they collide or they think they are colliding when they do not appear to be visually. Other than that, every once in a while I have issues with their JavaScript expression library and what is allowed to be used there and how it evaluates or shows me previews of the results. There are occasional bugs there. Overall though, I have been impressed at how responsive their team is to our issues and they are really willing to hear our feedback and look for ways to improve.

I have been using SnapLogic for my entire time at my current company, so a little over one year.

SnapLogic is stable overall, as I know that they went through several back-end revamps a couple months ago. Probably in April, they were having some significant latency and downtime issues over the course of a few weeks. That is the only time that I have seen issues with stability on their side.

We have seen Snaplogic's platform handle significant load spikes without issue, however every once in a while we have a high enough load to take down our Cloudplex. When that happens it is usually able to spin up a new instance automatically very soon after and we don't see much of a drop in service.

The customer support from SnapLogic is definitely very impressive. I believe that we may be one of their bigger customers or one that they work with the most personally. We talk to their team quite often. They have been very responsive to feedback. They seek out our experiences with their new features and they walk us through their up-and-coming products, which is very rewarding. So far I have been very impressed with how responsive they are and how well they take feedback and they value my team's experience. I would rate the customer support from SnapLogic on a scale of 1 to 10 as nine out of 10.

Not applicable, my company chose Snaplogic before I was hired here.

Not applicable, my company chose Snaplogic before I was hired here.

Not applicable, my company chose Snaplogic before I was hired here.

I don't have access to much of the financial side of my company's decision on Snaplogic, but I know that we have occasionally looked at switching to another service but decided to stick with Snaplogic due to how useful it is for its value.

Not applicable, my company chose Snaplogic before I was hired here.

As far as I know, we have always been on SnapLogic since my company was founded. However, I know that my team also evaluated options in Azure and AWS. For example, AWS Glue was something that we looked at, and I believe they chose SnapLogic due to the extensiveness of features, the good support structure from their team, and pricing considerations were involved there too.

I would advise others looking into using SnapLogic that if you are looking for something that gives you a visual aspect at the cost of some more options, or more manual options that you could probably tweak if you were to use code instead of a visual solution, SnapLogic is very good at simplifying things and making it very visually clear what is happening with the data. There is a bit of a cost when it comes to debugging because you have to go through their validation flow and it can be a little slower than it might be on the code side to validate and test things. Obviously, they have a UI that abstracts away a lot of the details that you might have if you were to do it purely in code. However, that does make things simpler and faster in my opinion to build. It is really easy to repeat patterns and share things that work across different pipelines that you may have. It has definitely helped my team move faster in making a lot of our data transformation and extract processes simpler, faster, and easy to replicate and repeat across working cases. SnapLogic has been great for us. If that is an issue that your team is seeing, then SnapLogic would be a great solution for you to help you simplify things and make things faster.

I do not have any additional thoughts about SnapLogic before we wrap up, except that it looks as though a response about the business relationship with a vendor may have been skipped. As far as I know, we are only a customer of SnapLogic. I do not know of any partnership other than that. I am happy to be using SnapLogic and I look forward to their upcoming features and I look forward to working with them more in the future. I give SnapLogic an overall rating of 8 out of 10.

My main use case for SnapLogic is integration with other systems, and I also use SnapLogic to replace a lot of our older systems that require integration.

A specific integration I set up with SnapLogic that made a significant difference for my team is called SGM, which is a Stanford Group Manager. It was originally written in Java and worked on a very old server, so instead of migrating the code and the technology to a new server, I redeveloped it using SnapLogic. Once I redeveloped it using SnapLogic, the integration part lagged a bit, so I still had to use some Java, especially for the integration with Active Directory. Even though SnapLogic provided resources and snaps for that, it was still inefficient.

Additionally, I had to integrate new harvesters, which are the logic side where they post events and process them. As SnapLogic matured, I rewrote part of that to spawn duplicate processes to execute and run a lot of the back-end integration, really cutting down on time, and as SnapLogic continues improving and I learn more about it, I continue to upgrade our current systems to make them more efficient and outperform a lot of our old systems.

One other benefit about my main use case with SnapLogic is the harvesters, which went through about four or five revisions before I created a standard template snap where I could use a property file to achieve the same information instead of repeating the pipelines or projects. Therefore, when someone does a request and they need this simple integration, I retrieve some information from a get and then post the information to a downstream system that could have multiple authentications, which I can now do all within a property file. This enables me to spin up a new harvester in SnapLogic within half a day, saving a lot of time.

I think the best feature SnapLogic offers overall is seamless integration. I basically only have to ensure I have all the right credentials to hook up a database, and therefore I don't have to write any of the JDBC that I had to do in Java for a connection. Other features I discovered include the versatility of authentication, though not all types of authentication are still available, and I look forward to seeing this improve so I can migrate other old applications over to SnapLogic.

SnapLogic positively impacts my organization by allowing me to do more application development integration in less time. However, when something brand new starts, there is still a big learning curve on how to implement it and streamline and use the features as best as possible. SnapLogic keeps improving, and as it improves, I have to go back and redesign slightly on our pipelines to make use of all these new snaps, leading to retrofitting that takes time.

I think SnapLogic can be improved by implementing more seamless logging of information. Currently, this is done through an error, but it would be best to have logging available on each snap that you can turn on and off, allowing you to configure a logging mechanism for where it logs. By having each snap available for logging, you can log all the information instead of creating a separate pipeline for logging.

Additionally, I suggest caching for snaps that are recursively called, particularly when logging in, authenticating, doing actions, logging out, and then repeating the process, which would significantly speed up operations, especially when querying an Active Directory because retrieving many members in Java takes about five seconds, whereas in SnapLogic, it takes a minute and a half for the same operation.

Regarding the new dedupe snap, I think the default setting should be changed from the current 80% match to an exact match, allowing for changes afterward, as I ran into issues during regression testing where a minor difference led to duplicates being flagged unintentionally.

I have been using SnapLogic for about seven years now.

SnapLogic is about 90% stable in my experience. There are times when snaps fail for unknown reasons, and sometimes after an upgrade, SnapLogic itself becomes unstable, but overall, it holds a 90% stability rate.

I believe SnapLogic's scalability is defined by our available budget. The more budget we have, the more resources we can obtain, hence allowing our pipelines and work to expand, making it challenging to assess without considering other external conditions.

I find customer support for SnapLogic to be top-notch, particularly with Dwayne. Most support from Zendesk has been very helpful, although some others are less so, as we often push SnapLogic beyond its limits, which leads to suggestions for improvements and inquiries about their design.

Overall, I would rate customer support ten out of ten. Due to Dwayne's involvement, I would even consider going past ten, given his strong interest in our work.

The solution I used before SnapLogic was Java, which was the only option available at the time for doing all the work.

I was not involved in the SnapLogic evaluation. When I joined, it was just in its infancy, and I went through the training while management made the decision to use it.

My advice for others looking into using SnapLogic is to anticipate a learning curve regarding the features currently available, as there are many ways to accomplish various tasks. It is best to take the training and engage with others who use SnapLogic to gather insights on achieving different functionalities since there is always room for improvement. I would rate this product an eight out of ten.

My main use case for SnapLogic is migrations from Boomi and other SQL databases to SnapLogic. Regarding the SQL database, I'm not going to disclose the customer name, but I can give you some highlights. It was financial data for a Fintech organization. They wanted to move from their PNL and GL data. All these migrations and the benefits data, which they have to send to the third-party system, moved from another iPaaS system to SnapLogic because of delays and latency, which was the biggest issue for them. So, we built up plenty of data lakes and migrated the data back to SnapLogic.

Similarly, for the SQL database, it wasn't only the latency, but they were also facing issues where people were unnecessarily writing a lot of triggers. They didn't think that was the correct way because there was no alignment or streamlining in terms of process design or the reusable storage of technical resources. They wanted to identify and streamline the entire process, as well as build some kind of reusable process. I have also found that SnapLogic, or perhaps Boomi or MuleSoft, whatever the customer is going to choose, has some kind of edge in terms of processing data quickly and with a reduced amount of latency. I don't know what changes they are going to do with the help of agent AI, all the pipelines, and DataBricks, and all these things, and how they are going to put the data in perspective within the application. That is the use case I can tell you.

The best features SnapLogic offers include the different integration patterns you can quickly adapt. Manipulation is easy with the data. When I'm saying easy, I mean that there are a lot of ways to get different data sources into one place, and then you can do a lot of customization. It is easy as well. For a person who doesn't have that kind of exposure, they can quickly adapt. There is no space to say, 'I don't know this system.' If your basics are clear, then you can quickly adapt. So, it is a quick adoption from SnapLogic's side. The second thing is that the kind of features they are providing for the different integration patterns is really unique.

You can build a lot of quick JMS connections. There are inbuilt connections for the likes of SuccessFactors, Salesforce, and Oracle where you can get the data from the ERPs. Then you can do the data manipulation and map the data to the destination system, and send the data to SFTP, to an S3 bucket, or via the API. You can build the API as well within that suite, and then manipulate the data over there. Accordingly, you can utilize the RBAC system in a better manner.

SnapLogic is coming with a lower latency rate when it comes to a huge number of pipelines and the huge terabytes of data they need to read and then they need to write. Especially if they can look towards Apache Iceberg or DataBricks or anything Spark, in terms of how these systems handle the kind of data they are going to send. So there is a quick turnaround to processing the data for any of the downstream systems.

I believe that SnapLogic impacts the organizations I work with as a contractor. It is really useful for them, especially for new use cases that are quickly adapted with a quick turnaround. It is very useful in terms of testing and realization. Especially when there are unique features in SnapLogic, the entire chain and transport management system for sending the whole config from development to quality and from quality to production is really fantastic. This gives a different kind of aspect to the customer as well, to quickly make changes in development with a quick turnaround. In no time, they can send the data from dev to production.

The latency is the biggest issue across iPaaS. That is the important part. I have worked not only with SnapLogic, but also with MuleSoft, Dell Boomi, and Jitterbit. They are all fine, but they have different kinds of functionality. They all have similar kinds of problems in different domains. But as I mentioned, SnapLogic has a little bit of an edge because of its functionality and inbuilt functions for Fintech, as compared to the others. This I can say firmly.

They need to assess themselves. In this day and age, as I mentioned earlier, terabytes of data need to be read and then have a quick turnaround for downstream systems, especially for GenAI or any LLMs. Then they can definitely improve themselves because right now, most things, in fact, the GenAI, ChatGPT, Cloud, Anthropic, and so many others, require data quality with perfection and more precision. But for all of that, we require a data pipeline that can be read without latency and without any delay, for any reason. So if they can improvise that over the cloud, that would be really fantastic and a really good achievement for them. Not only for them, but for the customer as well. Then no matter what, people cannot leave SnapLogic. They need to be there with the snaps.

I don't know much about that. I haven't referred to the documentation that much. But support is something that is pretty obviously required, rather than just providing videos. Technical support is required. The roadmap also needs to be very clearly mentioned and specified. Be specific in which domain they are going to do what, if they are coming out with that roadmap. Otherwise, overall, if they are going to improve their entire system as I mentioned earlier, for the reusability concept and the data pipeline concept, then they will definitely do some magic in the future.

From the HR point of view, or for HR tech, improvement is required. A couple of connectors are not working with all the relevant APIs, and there is always a restriction in terms of fetching the data. So that is why I chose six. From the Fintech point of view, if you are asking on a scale of one to 10, then I would give it an eight out of 10. It is a huge one. There is always a margin for improvement, so that is why I chose eight. If you talk about HR, sales, or any other domain, there is a significant amount of improvement required.

I have been working in my current field for close to 18 years.

SnapLogic's scalability is huge. There is a huge amount of scalability. That is why I put it on the scale of six. There is an area for improvement. Once that area of improvement is already done, or about to be completed, then it will definitely be a nine out of 10.

Customer support for SnapLogic is neither bad nor good. It is okay, normal. Sometimes it is very good, sometimes there is no response.

Neutral

I did a lot with Boomi. I love Boomi a lot, along with SnapLogic. Where we switched to SnapLogic, it wasn't from Boomi. The customer chose SnapLogic over the traditional way of working, such as a SQL database, Oracle database, or some other iPaaS solution, which was not Boomi. They switched because the traditional solutions did not fit their commitment or approach to making an ecosystem out of the cloud. That is why they switched to SnapLogic. Everywhere I have worked where SnapLogic is used, they were all in Fintech. Fintech has huge, secured, and very cumbersome numeric logic. They don't have a huge population within the organization, but they require very complex calculations which they would to complete easily. This allows them to connect with it over many years. So if they would want to switch from or to SnapLogic, they need the entire ecosystem as it is: process optimization, approach, documentation, etc. That is why they chose SnapLogic.

I have evaluated other options. Honestly speaking, I gave the suggestion for both Boomi and MuleSoft.

I am a contractor, so I can work. I know this. I did not work with a partner, reseller, or any kind of relationship for anyone.

Time was definitely saved with SnapLogic. Money, I don't know. I'm not part of the pricing and setup, so I can't say. I can't comment on that. It is not that fewer employees were needed, but time was definitely saved, and our process was optimized with the help of SnapLogic. That I can say for sure.

Before using SnapLogic, I had a different opinion.

I would rate SnapLogic a six on a scale of one to ten.

I don't really remember if you are talking about metrics, but I can give you one example where we built around eighty odd interfaces out of three hundred interfaces that needed to be migrated from Oracle. It worked really well. It was fantastic in terms of processing, latency, data manipulation, and the downstream system. For one interface, we had to send it to more than thirty places in different time zones with different scheduling. We heavily customized those interfaces, and it really works well.

I would tell others looking into using SnapLogic to use it. Take it, use it, and use it. You can't go beyond SnapLogic. SnapLogic is not going to give you any kind of bad experience, definitely. Because any solution that has a huge amount of scalability, there is a probability that a solution SnapLogic is not going to feel uncomfortable for any customer expectations.

Good luck. Do great things and have great achievements. I would love to see and then move myself also onto SnapLogic's new roadmaps. You will definitely do some wonders with SnapLogic.

My main use case for SnapLogic involves replacing old ETL functions, improving data flow, and enhancing efficiencies, business processes, and data quality across the enterprise.

A specific example of how I am using SnapLogic to improve a particular business process or data flow is that we have been able to go directly to subject matter experts and, through complete requirements-based discovery, rebuild, replace, and improve entire business functions very simply, quickly, and in ways that we were not previously able to do. Some functions that had been static and out of date for three, four, five years have been able to be turned around completely within a matter of weeks. The entire previous ETL architecture has been replaced within 12 months from when we started.

It is very easy to adapt to SnapLogic. It is very user-friendly. People who have not used the product with previous experience of any kind have been able to pick up and deliver most of this internally within the last year. While we have had a lot of external help from SnapLogic themselves, it has been a revelation compared to older, legacy ETL functions.

The best features SnapLogic offers include its ability to connect to almost anything. It has snaps for any function that you want to do with the data on the way in, which means we do not have to limit what our users want the requirements to include based on technical limitations, and we are able to work really quickly.

The ability to connect broadly and work fast has changed the way my teams operate by allowing us to unify a lot of data more easily without manual intervention, which previously took dozens of hours a week from certain staff members. Regardless of format, location, and means of accessing data, everything can be brought in by SnapLogic with as little manual data processing as we would like it to be. While we try to retain a human in the loop, we have significantly reduced the amount of manual labor for almost every integration.

SnapLogic has positively impacted my organization by costing a lot less than our previous ETLs, saving about 50 percent of our running costs without having done anything, just by using SnapLogic. We are able to engage with people and make promises that we can keep, and we can mitigate a lot of risk knowing that the functionality of the tool allows us not to have to worry about whether or not we can solve problems. We delivered more in the last year than what was previously deliverable in the last three or four years, and we have completely mitigated the risks of a failing and out-of-service ETL being used for primary data migration functions at the organization. Thus, we see risk mitigation, cost-cutting, and process improvements across the board, and most of these are very tangible to those who are subject matter experts in the areas we work with.

I see very few areas where SnapLogic needs improvement. There are some very fringe cases we have had to abandon due to minor complexity and time pressures, such as the ability to read a PDF and isolate tagged data areas on that PDF to extract data, which we did not find very easy to start with. However, we had the limitation of needing to turn this around in a matter of days, so we did not have time to investigate further. Other than that, I find it very difficult to identify areas for improvement; I think it is pretty industry-leading as far as these tools go. Comparing it to other products, I believe the return on investment has been met within a year and then some, whereas previously we wasted a lot of money trying to deliver the same things. Therefore, I have no real notes at this point, but I think consistent evolution is essential, and I look forward to seeing what they do next.

Support has been exemplary.

I have been using SnapLogic for 13 months.

SnapLogic is extremely stable.

SnapLogic's scalability is extremely reliable. We have built solutions that we have expanded to deliver higher volumes of data with the same pipelines, and we are able to iterate and expand on existing pipelines to deliver new functionality through simple Jira tickets without reinventing the wheel or starting whole projects to deliver change. Its self-documenting nature allows us to understand what was previously built and how to improve on it. The ability for us to refer back to the requirements we established through our recent work with SnapLogic strengthens the connection between the business processes and SnapLogic's role in allowing us to see the whole picture when looking at scaling.

Customer support is outstanding across all levels, including marketing, account management, and technical support, which are each individually and separately brilliant.

I previously used a different solution, initially Scribe, which reached end of life. We tried to use Talend, which did not meet our requirements. It was far too complex and lacked the user-friendly nature we needed; we relied on external developers to build our pipelines, adding significant extra costs on top of maintenance expenses. Therefore, when looking at cost savings, it must also include the amount we do not spend on external developers, which was substantial.

While we have had a lot of external help from SnapLogic themselves, it has been a revelation compared to older, legacy ETL functions.

I have shared some relevant metrics indicating that our previous ETL functions totaled around 120,000 pounds of commitment every year, while our SnapLogic commitment is less than half of that, providing an immediate return on investment. The pipeline function has also removed a lot of manual effort required, and while it has not reduced the number of employees we want to keep, it has allowed those employees to work on things that are more meaningful to the organization.

My company evaluated other options before choosing SnapLogic, but I do not know which ones since it occurred prior to my engagement with SnapLogic. However, I know that there were very few competitive alternatives that delivered anything close to what SnapLogic does.

My advice to others looking into using SnapLogic is to ensure that you upskill, train, and identify members of internal staff who can be used as developers on the product. The usability of SnapLogic far exceeds that of other products, which allows you to save a lot of money by using internal people along with the support and onboarding that SnapLogic provides. We did this with a few people, and it would have been better for us to do it with more internal staff because trusting them to take on development responsibilities is a great opportunity for upskilling, career development, and reducing development costs. I also recommend understanding as much of your existing environment and what can be replaced quickly before implementation to enable rapid wins and quick returns on investment.

Regarding SnapLogic's AI capabilities, I think its governance and security are areas I am not particularly close to in my day-to-day. The assurances and introductions we have been given make the trust in that very reliable. We make small use of AI in the SnapGPT snap functionality as well as in giving guidance on how to build pipelines, but we have not yet accessed larger-scale AI utilization. Thus, it has become less relevant than we expected immediately, but this may be something to engage with in the future. Therefore, I do not really have much to say about it, except that it seems reliable, and there is no reason not to trust it.

Regarding SnapLogic's AI capabilities, the accuracy and reliability of output, especially with features such as SnapGPT or pipeline guidance, in the small cases we have used it, have been reliable in almost every instance. I think as we deliver more complex work in the future that I cannot yet comment on, it may become something where I need to give more detail, but at this point, I think it is great.

SnapLogic is deployed in our organization using the cloud. I am not exactly sure which type because I was not involved in the implementation, but we access SnapLogic through the portal and have several snap engines running to deliver the work we are doing. Another member of my team who will be giving this review will be able to contribute more on this area.

I was not directly involved with the pricing, setup cost, and licensing, but I am, as the enterprise architect, the owner of all comparative data of cost and licenses and contracts we have across our ETL tools. SnapLogic is very competitive, and we found the bespoke and charity discounted options available extremely generous and suitable for our needs.

I would rate this review a 10 out of 10.

My main use case for SnapLogic is data integration.

A quick specific example of how I use SnapLogic for data integration is connecting to external sources such as APIs and SFTPs to obtain supplier product data as well as public data from things such as gov.uk and bringing it into a centralized location within the business.

I found the process of connecting to those external sources with SnapLogic quite difficult at first, as there was quite a steep learning curve involved with SnapLogic. However, once the GPT had been activated, it made the learning curve significantly smaller, and therefore the ability to connect to those external sources was a lot easier.

SnapLogic has positively impacted my organization by enabling us to bring a lot of external data in for our suppliers so that we can then utilize that information to start reducing ad hoc queries within the business, improve customer relationships, improve customer experience, improve supplier relationships, and it is even now being used as negotiation tools within suppliers. This has brought a lot of benefit towards the customer, which is one of our big goals as a business.

A specific example that shows how SnapLogic has helped improve things such as customer experience or reduced ad hoc queries is that it has allowed us to look at things such as product life cycle data. Because we are utilizing things such as APIs to connect to supplier data sets, we are able to more proactively manage when products are being discontinued so that we can communicate that better with our customers in a way that we could not do previously without having access to those connectors.

The best features SnapLogic offers for me would be the ease of use within the actual graphical user interface and particularly the GPT, which makes it quicker and easier to actually test new projects and new solutions.

The GPT feature helps me with my projects by understanding the syntax to do various elements. For example, if I have a Mapper Snap that I am trying to clean some data from external to internal, I can use the GPT to help me work out the right syntax and check the output. It will give me four or five different options to pick from and lets me review them as I look at them so I can check that it is producing the right output that I expect. Additionally, it is also useful with things such as error messages and the method upon how to fix those error messages and decipher them. The GPT will help me work that out and can even offer ideas and solutions. It can actually adjust the pipeline if I allow it to, which is quite good.

I think that the biggest improvement needed for SnapLogic would be the learning curve. Without the use of the GPT, I think we would have really struggled as a business to adopt it. I think it is essential to provide more training opportunities that are offered as part of the package that comes with buying the tool and having the contract. When we asked about having learning materials and training materials, it came at an extra expense on top of the existing price for the tool.

In reality, if you had a more mainstream tool such as a Databricks or a Microsoft tool, that documentation and training would be public for you to access because there would be many things on Reddit or other platforms that people have posted. I know that Microsoft does offer free training material. I think there would be wider availability of training resources that do not rely on the GPT to support it as part of your package effectively.

I have been using SnapLogic for around two to three years.

SnapLogic is stable in my experience, as I have experienced very little downtime in my day-to-day usage.

As far as I have experienced, SnapLogic's scalability works very well for our needs, and I have had zero issues with it.

The customer support for SnapLogic is generally fantastic. However, there are some issues if I need new features, as it is usually locked behind a paywall, but that is business.

Before using SnapLogic, there was not a solution per se, but there was a bit of a focus on using Python to achieve similar things due to its open-source nature. However, I think the reality of moving to SnapLogic was down to the time it takes to create those pipelines, the security considerations of building those pipelines, and storing those passwords. Accessing the password vault system in Python was very risky, and for ISO accreditation, it poses challenges.

I have not seen a return on investment with SnapLogic at this time.

I find SnapLogic's integration with other tools and platforms I use to be very painless and easy to work with.

In terms of speed and throughput when handling large volumes of data, I find SnapLogic performs incredibly well. I think any of the performance degradations I have seen have been largely coming from the external source I work with, and I feel it is generally quite highly performative except for the Join Snap which has shown some performance implications.

I find SnapLogic's monitoring, logging, and alerting features to be sufficient for my needs. However, I would benefit from a bit more of an ability to compare numbers and performance of a pipeline against itself for the previous number of runs. For example, when I go on to the monitor tab, I can see the most recent run or I can compare how many times this pipeline ran in the last twenty-four hours. However, I cannot actually go, as far as I am aware, to a specific pipeline or to a group of pipelines and see if the number coming out of it and the performance that was shown were consistent, better, or worse than previous runs. I feel this would help me as an end user with the number of pipelines I am having to build for what I do.

I would say SnapLogic's documentation and online resources are generally easy to find, at least from within the SnapLogic graphical user interface. However, it depends on the documentation I am looking for. For example, if it is questions around a Snap particularly, I can obviously hit the question mark within the Snap and find it. However, I think it is less easy to find if I am trying to solve a specific problem, as I cannot just go on Google and search how to do this in SnapLogic because it is not as publicly documented as a Microsoft tool. However, with the use of GPT, there is less requirement to go and find the documentation because the question asked of the GPT can return the documentation for me.

I find SnapLogic handles error management and troubleshooting in some cases harder and in some cases easier. Particularly in the harder cases, it can be a bit like a typical Python error message, which can be a difficult thing to decipher and understand what it is actually saying. However, the GPT model really does make it considerably easier to handle.

SnapLogic's support for version control and collaboration between team members meets my needs.

My advice to others looking into using SnapLogic is to be prepared for a long learning journey since it is a bit of a long slog to get to where it becomes useful. However, the time spent does pay off. I would say to people to think carefully about what they intend to use SnapLogic for because for certain requirements, it could be quite expensive to achieve what you are trying to do. For example, if you are focusing purely on just getting data in, there are probably cheaper tools in the industry. However, if you are looking for something that is a bit more flexible and offers more flexibility on what you are trying to do, then that could be a good place to go.

My main use case for SnapLogic is to build integrations between two different applications or systems, mostly to facilitate the integrations part.

I can give you an example of an integration project I have built using SnapLogic. I built one of the more complex integrations, which was near real-time customer data synchronization between the Salesforce on-premise ERP system using SnapLogic. Their goal was to make sure both systems stay aligned on customer records, orders, and their status updates without any human intervention. So, the main goal is to make it all automatic with SnapLogic process. I designed a triggered pipeline using a Salesforce listener tap that captures all the record changes, ensuring no human intervention is needed. This data flows through validations and transformation Snaps, where I standardize the formats, handle a few operations, and ensure full consistency with the data. I also implemented a reusable error handling sub-pipeline that logs the failures in monitoring databases and sends alerts through email or channel notifications. For the ERP side, I exposed SOAP services, configured the SOAP execute Snaps with dynamic requests, and generated the payload as well. I ensured performance optimization issues were addressed as the volume increased by batching requests and parallelizing the process. This integration is now fully automated and monitored, requiring no human intervention. This is one of the integration projects among many I have worked on with SnapLogic.

I have also handled various integration use cases with SnapLogic. I have built REST API pipelines used to expose backend security to external applications, utilizing API tasks, API policies, and pipeline parameters. I have focused on batch ETL data pipelines for migrating large datasets from databases, like Snowflake to other cases, using bulk Snaps throughout. Additionally, I have worked on event-driven integrations using ultra pipelines for low latencies. I have connected applications, integrating CRM to ERP and ERP to CRM, where I handled mapping, transformations, validations, and reconciliation reporting. Another use case is for file processing automation, particularly with automated ingestion of CSV, XML, and JSON files, where I parsed and validated the file structures before loading into databases and generating reports and success/error messages. Lastly, for error handling and monitoring frameworks, I built and logged failures to database log services, created alerts via email or Slack, and stored failed payloads for retrievability, ensuring data quality and transformation pipelines with standardized formats. These represent some of the many use cases I have worked on.

SnapLogic positively impacts my organization, mainly in three areas: speed, system reliability, and maintainability. Before adopting SnapLogic, integrations were either custom coded or handled through scripts, leading to fragility and scaling challenges. With SnapLogic's reusable pipelines and pre-built Snaps, development time for new integrations drops significantly, in some cases from weeks to just a few days, as I no longer need to rebuild connection logic from scratch. The built-in error handling improves reliability, with monitoring dashboards and retry mechanisms reducing production failures and providing visibility into pipeline performance, allowing me to detect and resolve issues proactively instead of relying on business user reports. Another significant improvement is maintainability; the visual and modular nature of pipelines simplifies onboarding for new team members, making it easier to learn and standardize parameterization.

Speaking of metrics, I would emphasize a specific example: in one of my integrations, I synchronized customer and order data between Salesforce and my ERP. Initially, builds took about two to three weeks with custom scripts and manual API logic. After transitioning to SnapLogic, I averaged this down to just days for similar integrations, primarily due to the reusable pipelines that streamline efforts. The majority of time savings stemmed from the pre-built Snaps, eliminating the need to write authentication or pagination logic anew. Regarding reliability, before SnapLogic, I experienced approximately eight integration failures per month due to timeout errors, schema mismatches, or unhandled null data. After implementing structured error handling pipelines, retries, and validation layers, this number has dropped to around two to three incidents monthly, mostly attributed to upstream system issues rather than pipeline failures. From a maintenance angle, onboarding new developers who previously needed weeks to confidently modify integrations has been dramatically reduced with SnapLogic's visual pipelines and standardized design approaches, leading to faster delivery, fewer production issues, and less time spent debugging.

SnapLogic offers numerous features that stand out. One of the key features is the pipeline designer visualization, where users can drag and drop components based on their use cases, making it user-friendly. SnapLogic execution transparency and preview at each data step provide vital information about how components work and their utility. Another highlight is SnapPacks, featuring pre-built connectors, which save time. There are hundreds of connectors for APIs, databases, SaaS applications, files, and messaging systems, with built-in authentication handling. Ultra pipelines boast impressive response times in milliseconds and are persistent in executing nodes. Additionally, SnapLogic's modular designs promote reusability, allowing developers to maintain structured development. The error handling frameworks also enable production-grade setups without needing custom frameworks, facilitating retry logic and hybrid architecture flexibility. SnapLogic excels in data transformations, monitoring, and observability, providing scalability controls for the pipelines.

I would like to highlight the expression language feature, which is primarily based on JavaScript and allows for logic to be embedded directly in the pipeline components. Its strength lies in dynamic routine logic, making it easy to write clean, efficient expressions for various use cases. Another notable feature is the pipeline execution mode offering options for trigger tasks, scheduled tasks, alter tasks, and execution patterns. This flexibility aids in designing execution strategies. SnapLogic also integrates metadata and schema handling, with automatic design and schema capabilities being significant differentiators. Experienced engineers truly understand schema stability with SnapLogic. Other features such as pipeline patterns, design, and scalability further contribute to its robustness. However, if I had to choose a favorite feature, it would be the reusable child pipelines with parameterization because it enforces standard logic, reduces duplication, and underscores SnapLogic's role as an integration platform rather than just a tool, allowing for team scaling and ensuring consistency.

While SnapLogic is powerful, there are several areas for improvement that could enhance user experience. Version control remains an area needing attention as it currently lacks effective features. Debugging complex pipelines can be painful, especially when dealing with deeply nested structures, making it difficult to trace data lineage across pipelines. Improvements in centralized execution and trace visualizations are also necessary. Furthermore, compared to other code-based tools, there is room for advancement in structured transformations, making this a critical area for improvement.

I have been using SnapLogic for eight years.

Positive

For monitoring and alerting my SnapLogic integrations, I utilize various dashboards. I implement a layered approach, conducting platform-level monitoring, pipeline-level logging, and proactive measures. Using the built-in dashboard for runtime metrics and execution histories provides operational visibility. I design pipelines with a centralized logging and alert framework, ensuring failures are immediately detected rather than discovered by users.

I manage versioning and deployment of pipelines using a structured promotion model across environments, including development, QA, and production. Pipelines are developed and tested in development projects and promoted to higher environments using SnapLogic's project export functionality. Environment-specific values remain externalized through parameters and accounts, enabling the same pipeline to operate across all environments without modification. For version control, I maintain backups and track versions with naming conventions for proper documentation and repository snapshots. Prior to deployment, I validate dependencies and conduct test executions to ensure stability, minimizing configuration drift and securing successful deployments.

SnapLogic supports data transformations primarily through its mapper Snap and expression languages that facilitate complex field mapping. This includes conditional logic, data restructuring, and format conversions. In my projects, I utilize the mapper Snap for most transformations, as it allows for visual mapping of schemas while concurrently supporting advanced logic through expressions. For complex scenarios, I combine the mapper with scripting and aggregate, router, and join Snaps to develop more modular transformation pipelines. This approach maintains transformation processes that are reusable and scalable across integrations.

My advice for anyone considering SnapLogic is to view it as an integration platform rather than merely a tool. Doing so can yield stronger results when teams design pipelines with scalability, modularity, and governance in mind from the onset. Organizations should invest early in defining naming standards, reusable components, parameterization strategies, and monitoring frameworks. SnapLogic can significantly accelerate development, with its real value revealing itself when implemented with architectural discipline rather than for quick, one-off integrations.

As a closing thought about SnapLogic, I would emphasize that it is indeed a powerful integration platform with clear strengths, but it also has defined limits. Its effectiveness comes to the forefront when used properly, and its success heavily relies on implementation discipline rather than solely the tool itself. I have given this review a rating of 9.

Our main use case for SnapLogic is the integration of student data, some finance data, and some internal Stanford data processes.

A specific example of how I use SnapLogic for integrating student or finance data is when new staff, students, or faculty join Stanford; they have to be added to different workgroups or their email has to be set up, so many processes are done via SnapLogic integration. On the finance side, it involves processing data related to the Office of Development, where some gift processing happens. Multiple teams at Stanford, including the School of Business, use SnapLogic for tasks such as booking meeting rooms.

We use SnapLogic for various integration purposes, including integration from Salesforce to Oracle, from flat files to Oracle, and integration from FileMaker to Oracle, among others. Although many more integrations are running as pipelines, these are a few I can recall as an infrastructure team member.

The best features SnapLogic offers are its ease of development for pipelines, where the authentication and account configuration are straightforward, and it allows for easy connections to sources and targets, as well as simple transformations and making multiple copies of the same data. I find the development part very easy, especially from an infrastructure perspective, since we host all Snaplexes on-premises servers; upgrades are seamless, and the impact on pipelines during rolling upgrades is minimal.

The development interface is user-friendly, making the process of connecting to sources straightforward, especially when setting up accounts using any Snap or API, which allows anyone to use it easily. Making configuration changes or moving servers between environments is also very easy.

SnapLogic has positively impacted our organization by providing an alternative to Informatica, which was challenging due to licensing and other issues. With SnapLogic, we can now connect to various SaaS and cloud products, and its usage has spread across different departments, making it a central tool for both on-cloud and on-premises ETL processes.

Areas for improvement for SnapLogic include enhancing the documentation, especially by providing more complex examples in each Snappack, to cover various use cases that different team members may encounter.

Another improvement I suggest is enhancing the monitor page on the dashboard to allow quicker and more efficient access to historical data, as it currently becomes slow and sometimes hangs when accessing older data.

I have been using SnapLogic for six to seven years.

I have been using SnapLogic for a while, and I believe the tool has become more stable, although there are still monitoring features I have had to build on my own. More robust APIs would assist anyone looking to automate processes.

My advice for others looking into using SnapLogic is to participate in training sessions provided by SnapLogic support, which can significantly help new users understand the UI and its functions through self-learning videos. I would rate my overall experience with SnapLogic a 9 out of 10.