Automation has transformed daily operations and now delivers faster, more accurate data flows
What is our primary use case?
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.
How has it helped my organization?
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%.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using SnapLogic for six years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What was our ROI?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Automated data integrations have reduced failures and now support faster, reliable deliveries
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using SnapLogic for eight years.
How are customer service and support?
I would rate customer service as a 5.
How would you rate customer service and support?
What other advice do I have?
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.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Rekiable, Scalable integrations with no/low code
What do you like best about the product?
What I like the most is that how quickly you can build and scale integrations without writing a lot of custom code. The pipelines are intuitive, especially for common use cases like Saas Integrations, API based data movement, and loading data int0 cloud warehouses like Snowflake.
It reduces dev time and makes it much easier to maintain integrations.
What do you dislike about the product?
While Snaplogic ins powerful, some times debugging complex pipelines can be challenging, especially whenn working with nested snaps or large workflows. The UI can feel a bit cluttered for very large integrations.
What problems is the product solving and how is that benefiting you?
It solves the problem of integration data across multiple systems quickly and reliably. It helps us streamline our data ingestion from multiple sources into our data warehouse and reduce manual scripting and maintenance effort.
As a result out data pipelines became more consistent , easier to monitor and faster to adapt when new sources were introduced.
Daily sales pipelines have delivered accurate reports and reduce manual monitoring
What is our primary use case?
My main use case for SnapLogic is to use the monitor tab to monitor the daily pipelines, the sales reports, and to check on the failures which are happening. When some failures occur, I utilize SnapLogic Designer to make the changes so that the pipeline runs successfully.
A specific example of a pipeline I've worked on recently is the daily sales report which we deliver to the business during the early business hours. It is a critical report, and for that file, we faced the issue of duplicates. Together with the help of my senior teammates and colleagues, we created a pipeline that removes all the duplicate entries. It was fascinating because SnapLogic has inbuilt Snaplets that we can directly drag and drop and develop a pipeline with very minimal code. Moreover, we can provide different kinds of parameters that can be versatile and changed according to our requirements. This is one of the pipelines I've worked on recently, about one or two weeks ago, and I monitor it daily after deploying it into the prod environment.
Most of the pipelines I work on are related to building up to loading the data into sales. In my current project, the data from SQL Server and Redshift is loaded into BigQuery and Oracle tables. In SnapLogic, we developed some transformations, such as removing duplicates and adding other parameters to remove inconsistencies. These are the types of pipelines we use in SnapLogic to transition data, functioning as ETL, by extracting from SQL Server or Redshift, transforming in SnapLogic, and loading it back into GCP and Oracle.
What is most valuable?
One of the best features SnapLogic offers is its user-friendly interface. I was not trained in using SnapLogic; I was trained in Informatica, which is also a data engineering tool. However, when I first started using SnapLogic, any person with minimal knowledge in data engineering can easily understand how SnapLogic works because it is clearly segregated into Monitor tab, Designer tab, and a Manager tab. The role assigned in your project defines which tab you will use the most. The user interface is important, and the inbuilt Snaplets that we can directly drag and drop to create different kinds of pipelines also stand out.
The drag and drop functionality and the tabs make my daily work easier compared to my experience with Informatica. In Informatica during my internship, creating mappings took a lot of time and effort since we needed to leverage Mapplets. While we can create one mapping and use it multiple times, there is no help from the application side. There are some transformations most users need that are not inbuilt in Informatica. In contrast, SnapLogic provides inbuilt Snaplets, such as creating and closing an audit ID, removing duplicates, joining tables, writing to Oracle, files, XML, SF, SMTP connections, and more. These Snaplets can be directly used rather than developed in every pipeline.
Since moving to SnapLogic, we have observed fewer errors compared to other tools, such as connection failures or network errors. We have also developed pipelines in SnapLogic capable of notifying us about long-running processes. For instance, if a pipeline that typically takes one hour runs for more than two hours, it automatically triggers an email alerting us to focus on that specific pipeline. This feature significantly reduces the need for continuous human monitoring, demonstrating how SnapLogic truly assists us.
What needs improvement?
I have only been using SnapLogic for about a year, around eight months, so I am unsure of the required changes. However, I believe that since most tools are now integrating with AI to assist new users, incorporating an AI tool could be beneficial.
Sometimes there are glitches when moving a design pipeline from the development to production environment.
For how long have I used the solution?
I have only been using SnapLogic for about seven months.
What do I think about the stability of the solution?
SnapLogic is very stable.
What do I think about the scalability of the solution?
SnapLogic is very scalable, and it can be adjusted based on our requirements, considering the organization type and the data it produces.
How are customer service and support?
I have not used customer support directly, but I have utilized the integrated helping websites, which have been very helpful when I first started using SnapLogic.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I learned from my colleagues that two years ago, all our transformations were carried out in Informatica. Because of the inadequate infrastructure in Informatica, our team suggested transitioning to SnapLogic, which the client accepted. After comparing workflows in Informatica and pipelines in SnapLogic, we found that the number of errors due to network or connection issues is much rarer in SnapLogic compared to other tools. The decision to transition to SnapLogic was very beneficial, as it helped the client build a secure and robust environment for their data.
We transitioned to SnapLogic due to the lack of proper infrastructure in the previous tool.
Which other solutions did I evaluate?
My seniors evaluated different options, including SnapLogic, improving the infrastructure in Informatica PowerCenter, and using PySpark, but they ultimately chose SnapLogic over the other options.
What other advice do I have?
My advice for others looking into using SnapLogic is that it is really easy to use. Anyone with minimal knowledge in data engineering or ETL can easily transition into a SnapLogic developer or start using SnapLogic. I have mostly covered all the topics concerning SnapLogic that I appreciate, and I have provided some suggestions that I hope would facilitate ease of use when integrated. I gave SnapLogic a rating of eight out of ten.
User-Friendly, Efficient Yet Needs Improved Connectivity
What do you like best about the product?
I basically like the ease of use and the very user-friendly UI that helps any user to start integrating and building pipelines and integration very easily from scratch. The connectivity is very fast, and it has a lot of snaps available to connect with multiple source systems and process the data. The user-friendly UI, especially the drag-and-drop feature, is very helpful for creating complex pipelines. The initial setup was very easy, and SnapLogic Intelligent Integration Platform documentation helps a lot whether it's on cloud or on-premises.
What do you dislike about the product?
Basically, when we are processing a larger dataset, it tends to take a lot of time if the nodes are not configured properly. The nodes might go into one particular node, leading to a lot of execution time. Also, while it is running for a longer time, there's a chance of losing connectivity between the external systems and SnapLogic.
What problems is the product solving and how is that benefiting you?
SnapLogic Intelligent Integration Platform (IIP) eases integration with multiple systems, enhances connectivity across environments, and manages large data sets with ease.
Easy Drag-and-Drop Integrations with SnapLogic IIP—Fast, Scalable, and Reliable
What do you like best about the product?
SnapLogic IIP stands out for its ease of use and ease of integration, making it simple to connect multiple applications and data sources. The ease of implementation is a big advantage, as integrations can be built quickly using prebuilt Snaps with minimal coding. It offers a good number of features that support both simple and complex integration needs. We use it frequently because it helps speed up development and reduces manual effort. Overall, it is a reliable platform for enterprise integrations.
What do you dislike about the product?
Although SnapLogic is easy to use once familiar, the initial learning curve can impact the ease of implementation for new users. Debugging and error handling could be improved to enhance the overall ease of use. The customer support response time can sometimes be slow for complex issues. Additionally, licensing costs feel high considering the frequency of use, and better optimization options would help when working with large data volumes.
What problems is the product solving and how is that benefiting you?
SnapLogic IIP helps us solve challenges related to connecting multiple systems and data sources across the organization. We use it as an iPaaS solution for ETL tools, API management, and on-premise data integration, which reduces manual effort and integration complexity. It also supports big data integration platforms and AI agent builders, enabling faster data movement and automation. This improves data consistency, speeds up integration delivery, and allows teams to focus more on business logic rather than technical integration issues.
Beginner-Friendly with Powerful Integrations
What do you like best about the product?
I use SnapLogic Intelligent Integration Platform (IIP) every day to create pipelines for various purposes. What I like most is its user-friendly drag and drop approach, which keeps the platform clutter-free by separating management and debugging into separate sections like Monitor and Manager. The platform’s ease of use is also enhanced by its ability to integrate with various third-party tools like Git, Tidal, and AWS, which makes it more powerful. Additionally, SnapLogic's low code/no code nature eliminates the dependency on coding knowledge, making it beginner-friendly. I also appreciate the advanced features that SnapLogic offers, including AI, allowing us to create our own AI agents. The initial setup was quite easy, and we received good support from the SnapLogic support team.
What do you dislike about the product?
In my opinion, SnapLogic is beginner-friendly, but when implementing advanced mappings in the mapper or using advanced or complex expressions, at least JavaScript knowledge is required. While generating an AI agent and implementing it through SnapLogic, there is a dependency on other systems like Streamlit, Python, MongoDB, etc. If that can be done in SnapLogic itself, it would reduce the dependency. Also, regarding enhancing user experience, SnapLogic should improve their certification content as many features are still missing, and due to that, many users are unaware of them.
What problems is the product solving and how is that benefiting you?
I use SnapLogic Intelligent Integration Platform (IIP) because it's beginner-friendly, allowing anyone to create pipelines without coding skills. It offers advanced features and AI integration, which makes it a powerful tool for my needs.
User-Friendly Integration Platform with Powerful Monitoring
What do you like best about the product?
I highly value SnapLogic for its user-friendly, low-code design that simplifies complex enterprise integrations. It efficiently handles large-scale data across cloud and on-premise systems, offering a reliable platform with comprehensive monitoring tools for easy day-to-day operations.
What do you dislike about the product?
A primary pain point with SnapLogic is the lack of a streamlined approach to incremental data loads, which necessitates complex custom handling. Additionally, the speed of technical support responses has been a challenge, occasionally delaying project timelines during critical troubleshooting phases
What problems is the product solving and how is that benefiting you?
One area for improvement in SnapLogic is the management of incremental updates; the process feels less straightforward than the rest of the platform and adds operational overhead to our pipelines. We also find that customer support response times are sometimes sluggish, making it difficult to resolve urgent issues quickly.
Effortless Integrations and Enterprise-Grade Performance
What do you like best about the product?
What I like most about SnapLogic IIP is how it simplifies complex integrations. The drag-and-drop interface and prebuilt connectors make it easy to build pipelines quickly without heavy coding. It handles large data volumes efficiently and performs reliably at an enterprise scale.
Another advantage is its flexibility—it works seamlessly across cloud, on-prem, and hybrid environments. The scheduling, monitoring, and error-handling features are very helpful for day-to-day operations, making it easier to track pipeline health and troubleshoot issues. Overall, it saves development time, reduces maintenance effort, and helps deliver integrations faster.
What do you dislike about the product?
One area where SnapLogic can be challenging is handling incremental loads. Setting up incremental logic is not always straightforward and often requires additional configuration or custom work, which can increase pipeline complexity and maintenance effort. Debugging such scenarios can also take extra time.
At times, customer support response can be slower than expected, especially for non-critical issues. That said, the platform itself is quite stable, and many issues can be resolved through logs, monitoring, and documentation.
Overall, while there are a few areas that could be improved, SnapLogic’s strengths—such as scalability, performance, and ease of building integrations—largely outweigh these drawbacks, making it a solid and reliable integration platform.
What problems is the product solving and how is that benefiting you?
SnapLogic helps solve the challenge of integrating data across multiple systems and applications in a simple and efficient way. It eliminates the need for heavy coding by providing prebuilt connectors and a visual pipeline design, which makes integrations easier to build, understand, and maintain. This significantly reduces development time and lowers the chance of errors.
The platform handles large volumes of data reliably and supports cloud, on-prem, and hybrid environments, which adds a lot of flexibility. Built-in monitoring, logging, and error-handling features help ensure stable data flows and make troubleshooting easier.
From a day-to-day perspective, SnapLogic has made my integration work smoother and more productive. The hands-on experience helped me learn quickly, gain confidence, and deliver integrations faster, making it a valuable tool for both learning and enterprise-level integration needs.
Boosted Our Data Integration with Superb Ease
What do you like best about the product?
I really like the low code pipeline development using prebuilt snaps in SnapLogic Intelligent Integration Platform (IIP), as it significantly reduces integration development time. The platform makes it easy to connect to APIs, databases, and public applications while providing flexibility through expressions and scripting when needed. I appreciate the pipeline visibility, error handling, monitoring, and scalable execution that help build reliable and maintainable integrations. The best part is its drag-and-drop interface combined with powerful prebuilt snaps for APIs, databases, and other connections. As a developer, it allows me to develop pipelines much faster than before, efficiently handles errors, and features efficient scalability and scheduling. Overall, it makes my life easier.
What do you dislike about the product?
Some areas that could be improved include debugging and error messages, which can sometimes be difficult to interpret for complex pipelines. Version control and pipeline promotion access environments could be more streamlined. Additionally, the initial learning can be challenging for new users, and more detailed documentation or examples for advanced use cases would be really helpful.
What problems is the product solving and how is that benefiting you?
I use SnapLogic Intelligent Integration Platform to automate data workflows and develop ETL pipelines. It connects databases and APIs efficiently with prebuilt snaps, reducing development time and improving data consistency. Its low-code interface and customization options make integration building straightforward and scalable.
