Building a Modern Data Platform<\/strong><\/h2>\n\n\n\nVaishali began by setting the stage:<\/p>\n\n\n\n
\u201cFor the past three years at Samsara, we have built out an enterprise data platform that supports all business lines at Samsara. We\u2019ve integrated our product usage data with business data as well.\u201d<\/p>\n\n\n\n
Her team\u2019s responsibilities span integrations, data engineering, and AI. \u201cWhat I love about what I do is building ground-up systems, making a difference to the bottom line.\u201d<\/p>\n\n\n\n
The Challenge with MuleSoft<\/strong><\/h2>\n\n\n\nWhen Vaishali joined Samsara, the company was already using MuleSoft. While full-featured, it wasn\u2019t keeping up with Samsara\u2019s pace of innovation.<\/p>\n\n\n\n
\u201cMuleSoft is a quite mature, very robust integration platform, but we felt that it was slow in innovation.\u201d<\/p>\n\n\n\n
Enter Workato<\/strong><\/h2>\n\n\n\nThe push to evaluate Workato was an executive initiative that came from Samsara\u2019s CIO, Stephen Franchetti, who had seen Workato\u2019s impact at Slack.<\/p>\n\n\n\n
\u201cHe proposed that I do some investigation and take a look at [Workato], because of its innovative nature\u2026 and it is very intuitive to use.\u201d<\/p>\n\n\n\n
After a successful proof of concept, Vaishali\u2019s team kicked off the migration.<\/p>\n\n\n\n
Large Scale Migration at Full Speed<\/strong><\/h2>\n\n\n\nThe scale of the existing MuleSoft implementation would be no small feat to migrate:<\/p>\n\n\n\n
\u201cWe had 48 integrated pipelines from point to point for all of our transactions, our order-to-cash being the most complex\u2026 1 million plus order-to-cash transactions, 3.26 million distinct transactions.\u201d<\/p>\n\n\n\n
But the team was up to the challenge and results were eye opening:<\/p>\n\n\n\n
\u201cOur longest [integration with Workato] took one to two weeks\u2026 [On MuleSoft] the same initial build took somewhere around eight to ten weeks. That is a tremendous amount of time for the MuleSoft build compared to how quickly we implement the same solution with the Workato recipes.\u201d<\/p>\n\n\n\n
Workato is Cloud-Native, Serverless, and Scalable<\/strong><\/h2>\n\n\n\n![\"\"](\"https:\/\/blog2workato.wpengine.com\/wp-content\/uploads\/2026\/09\/workato-cloud-native-vs-legacy-1-e1760747568594-1024x518.png\")
<\/a><\/figure>\n<\/div>\n\n\nThe migration wasn\u2019t just about speed. It was about embracing Workato’s powerful serverless architecture:<\/p>\n\n\n\n
\u201cWe went from cloud optimized [with MuleSoft], to cloud native [with Workato]\u2026 The whole management of virtual machines is gone. Everything is microservices-based, and therefore, much faster and more efficient from the engineering perspective. We have a serverless implementation on Workato, so we\u2019re not spending on infrastructure at all.\u201d<\/p>\n\n\n\n
Turning Skeptics Into “Believers”<\/strong><\/h2>\n\n\n\nChange is never easy, especially for engineers deeply invested in a legacy platform.<\/p>\n\n\n\n
\u201cI have over 100 years of MuleSoft [experience] on my team\u2026 It wasn’t easy to tell them, \u2018Okay, you\u2019re gonna move on to this new platform, something totally different that you\u2019ve never seen, never done before.’\u201d<\/p>\n\n\n\n
But even the those with deep allegiance to MuleSoft quickly discovered the power of Workato’s modern enterprise platform:<\/p>\n\n\n\n
\u201cAs someone who spent 10 plus years using MuleSoft, [my principal integration architect] admits that he was very skeptical at the beginning, but after some time working with Workato, first hand, he\u2019s a believer.\u201d<\/p>\n\n\n\n
\n\n\n\nCLIMBING TO NEW HEIGHTS WITH WORKATO<\/strong><\/h4>\n\n\n\n![\"\"](\"https:\/\/blog2workato.wpengine.com\/wp-content\/uploads\/2026\/09\/basecamp.png\")
<\/a><\/figure>\n<\/div>\n\n\nAccording to Shrujal Patel, Manager of Data Integrations at Samsara, “What did it for me was the speed of development, the scalable costs, and the pace of the Workato Product Team’s innovation. [Workato] is a modern platform and a vendor that delivers.”<\/p>\n\n\n\n
\u201cAs someone who spent 10+ years using MuleSoft, I admit that I was skeptical at the beginning but after some time working with Workato first hand, now I\u2019m a believer.”<\/strong><\/p>\n\n\n\n
\n\n\n\nExtensible Recipes, Observability, and Zero Failures<\/strong><\/h2>\n\n\n\nWorkato \u201crecipes\u201d were a revelation:<\/p>\n\n\n\n
\u201cThe recipe\u2019s business logic is completely decoupled from Workato execution runtime\u2026 so you don\u2019t have to worry about server availability. Here, we are completely decoupled, so there are no conflicts.\u201d<\/p>\n\n\n\n
Fully Embracing Cloud Native<\/strong><\/h2>\n\n\n\nWorkato leverages container technology thereby providing a lightweight, portable, and consistent environment for running the application, making it easier to manage and scale. This architecture allows developers to focus on business logic implementation with key operational concerns like guaranteed delivery and high availability handled by a robust distributed runtime, all deployed within containerized environments.<\/p>\n\n\n\n
WORKATO’S MICROSERVICES-BASED RUNTIME ARCHITECTURE<\/h4>\n\n\n\n![\"\"](\"https:\/\/blog2workato.wpengine.com\/wp-content\/uploads\/2026\/09\/Workato-Runtime-ipaas-Differentiation-e1760749164408-1024x606.png\")
<\/a><\/figure>\n\n\n\nVaishali went on to share \u201cnow that we\u2019ve embraced Workato\u2019s cloud-native platform, we are not limited by \u2018server-affinity.\u2019\u201d<\/p>\n\n\n\n
As with legacy platforms, server affinity between an application and runtime transfers the operational burden <\/strong>to the application developer, to consider factors like sizing, peak load estimation, performance, etc. Avoiding server affinity<\/strong> creates an auto-scalable infrastructure<\/strong> that constantly monitors the availability of “idle workers” to ensure the timely execution of every application event.<\/p>\n\n\n\nWORKATO’S AUTO-SCALABLE INFRASTRUCTURE<\/h4>\n\n\n\n![\"\"](\"https:\/\/blog2workato.wpengine.com\/wp-content\/uploads\/2026\/09\/Workato-auto-scalable-infrastructure-e1760749378422-1024x589.png\")
<\/a><\/figure>\n\n\n\nExtensible Recipes, Observability, and Zero Failures<\/strong><\/h2>\n\n\n\nWorkato\u2019s \u201crecipes\u201d were a game changer:<\/strong><\/p>\n\n\n\n\u201cThe recipe\u2019s business logic is completely decoupled from Workato execution runtime\u2026 so you don\u2019t have to worry about server availability. Here, we are completely decoupled, so there are no conflicts.\u201d<\/p>\n\n\n\n
WORKATO RECIPES DECOUPLE BUSINESS LOGIC FROM EXECUTION RUNTIME<\/h4>\n\n\n\n![\"\"](\"https:\/\/blog2workato.wpengine.com\/wp-content\/uploads\/2026\/09\/Workato-recipes-decouple-business-logic-from-runtime-e1760749465388-1024x599.png\")
<\/a><\/figure>\n\n\n\nWorkato’s<\/strong> Observability was another win:<\/strong><\/p>\n\n\n\n\u201cThere is quite a bit of auditing out of the box\u2026 job history and job entries, zero downtime, connector upgrades\u2026 We are also taking these logs and pushing them into Splunk and creating additional data accuracy dashboards.\u201d<\/p>\n\n\n\n
And the reliability?<\/strong><\/p>\n\n\n\n\u201cWe have deployed nearly a dozen projects in Workato\u2026 We have not had a single failure. Critical projects like implementing a brand new payroll system. We\u2019re not talking about something that is trivial. We\u2019re talking about something that impacts the entire organization. And we have not had a single failure period, not technically, not recipe-wise.\u201d<\/p>\n\n\n\n
2x Faster Development and Self-Service<\/strong><\/h2>\n\n\n\nThe impact on productivity was dramatic:<\/p>\n\n\n\n
\u201c[Workato is] two times faster [than MuleSoft], and it has given us the equivalent of three FTE\u2026 The biggest selling point for me, for Workato, was the ease of use and the speed of development from an engineering perspective.\u201d<\/p>\n\n\n\n![\"\"](\"https:\/\/blog2workato.wpengine.com\/wp-content\/uploads\/2026\/09\/2x-faster-workato-dev-vs-mulesoft-1024x361.png\")
<\/a><\/figure>\n\n\n\nWorkato\u2019s intuitive interface enabled self-service across teams:<\/p>\n\n\n\n
\u201cThese folks, these engineers, had never used an integration tool, period\u2026 The GTMS team also has two additional developers\u2026 and the corporate system has one person who\u2019s working on Workato as well.\u201d<\/p>\n\n\n\n
Looking Ahead: Workato One and the Agentic Future<\/strong><\/h2>\n\n\n\nAs Samsara looks to the future, Vaishali and her team are eager to build on their success by exploring the next generation of automation and Agentic AI with the Workato One platform.<\/p>\n\n\n\n
\u201cWe want to go forward with having a Workato platform that serves multi-purpose across Samsara,\u201d Vaishali shared. \u201cMy AI team is already scoping POCs for Workato One and the Agentic AI platform. We\u2019re excited to see how these innovations can help us deliver even more value, faster, and empower teams across the business.\u201d<\/p>\n\n\n\n![\"\"](\"https:\/\/blog2workato.wpengine.com\/wp-content\/uploads\/2026\/09\/workato-one-1-1024x425.png\")
<\/a><\/figure>\n\n\n\nWith Workato One, Samsara aims to take on new levels of automation, intelligence, and self-service, enabling teams across Integrations, Data Engineering, GTM, Support, IT, and Finance to move from integration to orchestration and from automation to true business agility.<\/p>\n\n\n\n
When Vaishali joined Samsara, the company was already using MuleSoft. While full-featured, it wasn\u2019t keeping up with Samsara\u2019s pace of innovation.<\/p>\n\n\n\n
\u201cMuleSoft is a quite mature, very robust integration platform, but we felt that it was slow in innovation.\u201d<\/p>\n\n\n\n
Enter Workato<\/strong><\/h2>\n\n\n\nThe push to evaluate Workato was an executive initiative that came from Samsara\u2019s CIO, Stephen Franchetti, who had seen Workato\u2019s impact at Slack.<\/p>\n\n\n\n
\u201cHe proposed that I do some investigation and take a look at [Workato], because of its innovative nature\u2026 and it is very intuitive to use.\u201d<\/p>\n\n\n\n
After a successful proof of concept, Vaishali\u2019s team kicked off the migration.<\/p>\n\n\n\n
Large Scale Migration at Full Speed<\/strong><\/h2>\n\n\n\nThe scale of the existing MuleSoft implementation would be no small feat to migrate:<\/p>\n\n\n\n
\u201cWe had 48 integrated pipelines from point to point for all of our transactions, our order-to-cash being the most complex\u2026 1 million plus order-to-cash transactions, 3.26 million distinct transactions.\u201d<\/p>\n\n\n\n
But the team was up to the challenge and results were eye opening:<\/p>\n\n\n\n
\u201cOur longest [integration with Workato] took one to two weeks\u2026 [On MuleSoft] the same initial build took somewhere around eight to ten weeks. That is a tremendous amount of time for the MuleSoft build compared to how quickly we implement the same solution with the Workato recipes.\u201d<\/p>\n\n\n\n
Workato is Cloud-Native, Serverless, and Scalable<\/strong><\/h2>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe migration wasn\u2019t just about speed. It was about embracing Workato’s powerful serverless architecture:<\/p>\n\n\n\n
\u201cWe went from cloud optimized [with MuleSoft], to cloud native [with Workato]\u2026 The whole management of virtual machines is gone. Everything is microservices-based, and therefore, much faster and more efficient from the engineering perspective. We have a serverless implementation on Workato, so we\u2019re not spending on infrastructure at all.\u201d<\/p>\n\n\n\n
Turning Skeptics Into “Believers”<\/strong><\/h2>\n\n\n\nChange is never easy, especially for engineers deeply invested in a legacy platform.<\/p>\n\n\n\n
\u201cI have over 100 years of MuleSoft [experience] on my team\u2026 It wasn’t easy to tell them, \u2018Okay, you\u2019re gonna move on to this new platform, something totally different that you\u2019ve never seen, never done before.’\u201d<\/p>\n\n\n\n
But even the those with deep allegiance to MuleSoft quickly discovered the power of Workato’s modern enterprise platform:<\/p>\n\n\n\n
\u201cAs someone who spent 10 plus years using MuleSoft, [my principal integration architect] admits that he was very skeptical at the beginning, but after some time working with Workato, first hand, he\u2019s a believer.\u201d<\/p>\n\n\n\n
\n\n\n\nCLIMBING TO NEW HEIGHTS WITH WORKATO<\/strong><\/h4>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccording to Shrujal Patel, Manager of Data Integrations at Samsara, “What did it for me was the speed of development, the scalable costs, and the pace of the Workato Product Team’s innovation. [Workato] is a modern platform and a vendor that delivers.”<\/p>\n\n\n\n
\u201cAs someone who spent 10+ years using MuleSoft, I admit that I was skeptical at the beginning but after some time working with Workato first hand, now I\u2019m a believer.”<\/strong><\/p>\n\n\n\n
\n\n\n\nExtensible Recipes, Observability, and Zero Failures<\/strong><\/h2>\n\n\n\nWorkato \u201crecipes\u201d were a revelation:<\/p>\n\n\n\n
\u201cThe recipe\u2019s business logic is completely decoupled from Workato execution runtime\u2026 so you don\u2019t have to worry about server availability. Here, we are completely decoupled, so there are no conflicts.\u201d<\/p>\n\n\n\n
Fully Embracing Cloud Native<\/strong><\/h2>\n\n\n\nWorkato leverages container technology thereby providing a lightweight, portable, and consistent environment for running the application, making it easier to manage and scale. This architecture allows developers to focus on business logic implementation with key operational concerns like guaranteed delivery and high availability handled by a robust distributed runtime, all deployed within containerized environments.<\/p>\n\n\n\n
WORKATO’S MICROSERVICES-BASED RUNTIME ARCHITECTURE<\/h4>\n\n\n\n<\/a><\/figure>\n\n\n\nVaishali went on to share \u201cnow that we\u2019ve embraced Workato\u2019s cloud-native platform, we are not limited by \u2018server-affinity.\u2019\u201d<\/p>\n\n\n\n
As with legacy platforms, server affinity between an application and runtime transfers the operational burden <\/strong>to the application developer, to consider factors like sizing, peak load estimation, performance, etc. Avoiding server affinity<\/strong> creates an auto-scalable infrastructure<\/strong> that constantly monitors the availability of “idle workers” to ensure the timely execution of every application event.<\/p>\n\n\n\nWORKATO’S AUTO-SCALABLE INFRASTRUCTURE<\/h4>\n\n\n\n<\/a><\/figure>\n\n\n\nExtensible Recipes, Observability, and Zero Failures<\/strong><\/h2>\n\n\n\nWorkato\u2019s \u201crecipes\u201d were a game changer:<\/strong><\/p>\n\n\n\n\u201cThe recipe\u2019s business logic is completely decoupled from Workato execution runtime\u2026 so you don\u2019t have to worry about server availability. Here, we are completely decoupled, so there are no conflicts.\u201d<\/p>\n\n\n\n
WORKATO RECIPES DECOUPLE BUSINESS LOGIC FROM EXECUTION RUNTIME<\/h4>\n\n\n\n<\/a><\/figure>\n\n\n\nWorkato’s<\/strong> Observability was another win:<\/strong><\/p>\n\n\n\n\u201cThere is quite a bit of auditing out of the box\u2026 job history and job entries, zero downtime, connector upgrades\u2026 We are also taking these logs and pushing them into Splunk and creating additional data accuracy dashboards.\u201d<\/p>\n\n\n\n
And the reliability?<\/strong><\/p>\n\n\n\n\u201cWe have deployed nearly a dozen projects in Workato\u2026 We have not had a single failure. Critical projects like implementing a brand new payroll system. We\u2019re not talking about something that is trivial. We\u2019re talking about something that impacts the entire organization. And we have not had a single failure period, not technically, not recipe-wise.\u201d<\/p>\n\n\n\n
2x Faster Development and Self-Service<\/strong><\/h2>\n\n\n\nThe impact on productivity was dramatic:<\/p>\n\n\n\n
\u201c[Workato is] two times faster [than MuleSoft], and it has given us the equivalent of three FTE\u2026 The biggest selling point for me, for Workato, was the ease of use and the speed of development from an engineering perspective.\u201d<\/p>\n\n\n\n<\/a><\/figure>\n\n\n\nWorkato\u2019s intuitive interface enabled self-service across teams:<\/p>\n\n\n\n
\u201cThese folks, these engineers, had never used an integration tool, period\u2026 The GTMS team also has two additional developers\u2026 and the corporate system has one person who\u2019s working on Workato as well.\u201d<\/p>\n\n\n\n
Looking Ahead: Workato One and the Agentic Future<\/strong><\/h2>\n\n\n\nAs Samsara looks to the future, Vaishali and her team are eager to build on their success by exploring the next generation of automation and Agentic AI with the Workato One platform.<\/p>\n\n\n\n
\u201cWe want to go forward with having a Workato platform that serves multi-purpose across Samsara,\u201d Vaishali shared. \u201cMy AI team is already scoping POCs for Workato One and the Agentic AI platform. We\u2019re excited to see how these innovations can help us deliver even more value, faster, and empower teams across the business.\u201d<\/p>\n\n\n\n<\/a><\/figure>\n\n\n\nWith Workato One, Samsara aims to take on new levels of automation, intelligence, and self-service, enabling teams across Integrations, Data Engineering, GTM, Support, IT, and Finance to move from integration to orchestration and from automation to true business agility.<\/p>\n\n\n\n
The scale of the existing MuleSoft implementation would be no small feat to migrate:<\/p>\n\n\n\n
\u201cWe had 48 integrated pipelines from point to point for all of our transactions, our order-to-cash being the most complex\u2026 1 million plus order-to-cash transactions, 3.26 million distinct transactions.\u201d<\/p>\n\n\n\n
But the team was up to the challenge and results were eye opening:<\/p>\n\n\n\n
\u201cOur longest [integration with Workato] took one to two weeks\u2026 [On MuleSoft] the same initial build took somewhere around eight to ten weeks. That is a tremendous amount of time for the MuleSoft build compared to how quickly we implement the same solution with the Workato recipes.\u201d<\/p>\n\n\n\n
Workato is Cloud-Native, Serverless, and Scalable<\/strong><\/h2>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe migration wasn\u2019t just about speed. It was about embracing Workato’s powerful serverless architecture:<\/p>\n\n\n\n
\u201cWe went from cloud optimized [with MuleSoft], to cloud native [with Workato]\u2026 The whole management of virtual machines is gone. Everything is microservices-based, and therefore, much faster and more efficient from the engineering perspective. We have a serverless implementation on Workato, so we\u2019re not spending on infrastructure at all.\u201d<\/p>\n\n\n\n
Turning Skeptics Into “Believers”<\/strong><\/h2>\n\n\n\nChange is never easy, especially for engineers deeply invested in a legacy platform.<\/p>\n\n\n\n
\u201cI have over 100 years of MuleSoft [experience] on my team\u2026 It wasn’t easy to tell them, \u2018Okay, you\u2019re gonna move on to this new platform, something totally different that you\u2019ve never seen, never done before.’\u201d<\/p>\n\n\n\n
But even the those with deep allegiance to MuleSoft quickly discovered the power of Workato’s modern enterprise platform:<\/p>\n\n\n\n
\u201cAs someone who spent 10 plus years using MuleSoft, [my principal integration architect] admits that he was very skeptical at the beginning, but after some time working with Workato, first hand, he\u2019s a believer.\u201d<\/p>\n\n\n\n
\n\n\n\nCLIMBING TO NEW HEIGHTS WITH WORKATO<\/strong><\/h4>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccording to Shrujal Patel, Manager of Data Integrations at Samsara, “What did it for me was the speed of development, the scalable costs, and the pace of the Workato Product Team’s innovation. [Workato] is a modern platform and a vendor that delivers.”<\/p>\n\n\n\n
\u201cAs someone who spent 10+ years using MuleSoft, I admit that I was skeptical at the beginning but after some time working with Workato first hand, now I\u2019m a believer.”<\/strong><\/p>\n\n\n\n
\n\n\n\nExtensible Recipes, Observability, and Zero Failures<\/strong><\/h2>\n\n\n\nWorkato \u201crecipes\u201d were a revelation:<\/p>\n\n\n\n
\u201cThe recipe\u2019s business logic is completely decoupled from Workato execution runtime\u2026 so you don\u2019t have to worry about server availability. Here, we are completely decoupled, so there are no conflicts.\u201d<\/p>\n\n\n\n
Fully Embracing Cloud Native<\/strong><\/h2>\n\n\n\nWorkato leverages container technology thereby providing a lightweight, portable, and consistent environment for running the application, making it easier to manage and scale. This architecture allows developers to focus on business logic implementation with key operational concerns like guaranteed delivery and high availability handled by a robust distributed runtime, all deployed within containerized environments.<\/p>\n\n\n\n
WORKATO’S MICROSERVICES-BASED RUNTIME ARCHITECTURE<\/h4>\n\n\n\n<\/a><\/figure>\n\n\n\nVaishali went on to share \u201cnow that we\u2019ve embraced Workato\u2019s cloud-native platform, we are not limited by \u2018server-affinity.\u2019\u201d<\/p>\n\n\n\n
As with legacy platforms, server affinity between an application and runtime transfers the operational burden <\/strong>to the application developer, to consider factors like sizing, peak load estimation, performance, etc. Avoiding server affinity<\/strong> creates an auto-scalable infrastructure<\/strong> that constantly monitors the availability of “idle workers” to ensure the timely execution of every application event.<\/p>\n\n\n\nWORKATO’S AUTO-SCALABLE INFRASTRUCTURE<\/h4>\n\n\n\n<\/a><\/figure>\n\n\n\nExtensible Recipes, Observability, and Zero Failures<\/strong><\/h2>\n\n\n\nWorkato\u2019s \u201crecipes\u201d were a game changer:<\/strong><\/p>\n\n\n\n\u201cThe recipe\u2019s business logic is completely decoupled from Workato execution runtime\u2026 so you don\u2019t have to worry about server availability. Here, we are completely decoupled, so there are no conflicts.\u201d<\/p>\n\n\n\n
WORKATO RECIPES DECOUPLE BUSINESS LOGIC FROM EXECUTION RUNTIME<\/h4>\n\n\n\n<\/a><\/figure>\n\n\n\nWorkato’s<\/strong> Observability was another win:<\/strong><\/p>\n\n\n\n\u201cThere is quite a bit of auditing out of the box\u2026 job history and job entries, zero downtime, connector upgrades\u2026 We are also taking these logs and pushing them into Splunk and creating additional data accuracy dashboards.\u201d<\/p>\n\n\n\n
And the reliability?<\/strong><\/p>\n\n\n\n\u201cWe have deployed nearly a dozen projects in Workato\u2026 We have not had a single failure. Critical projects like implementing a brand new payroll system. We\u2019re not talking about something that is trivial. We\u2019re talking about something that impacts the entire organization. And we have not had a single failure period, not technically, not recipe-wise.\u201d<\/p>\n\n\n\n
2x Faster Development and Self-Service<\/strong><\/h2>\n\n\n\nThe impact on productivity was dramatic:<\/p>\n\n\n\n
\u201c[Workato is] two times faster [than MuleSoft], and it has given us the equivalent of three FTE\u2026 The biggest selling point for me, for Workato, was the ease of use and the speed of development from an engineering perspective.\u201d<\/p>\n\n\n\n<\/a><\/figure>\n\n\n\nWorkato\u2019s intuitive interface enabled self-service across teams:<\/p>\n\n\n\n
\u201cThese folks, these engineers, had never used an integration tool, period\u2026 The GTMS team also has two additional developers\u2026 and the corporate system has one person who\u2019s working on Workato as well.\u201d<\/p>\n\n\n\n
Looking Ahead: Workato One and the Agentic Future<\/strong><\/h2>\n\n\n\nAs Samsara looks to the future, Vaishali and her team are eager to build on their success by exploring the next generation of automation and Agentic AI with the Workato One platform.<\/p>\n\n\n\n
\u201cWe want to go forward with having a Workato platform that serves multi-purpose across Samsara,\u201d Vaishali shared. \u201cMy AI team is already scoping POCs for Workato One and the Agentic AI platform. We\u2019re excited to see how these innovations can help us deliver even more value, faster, and empower teams across the business.\u201d<\/p>\n\n\n\n<\/a><\/figure>\n\n\n\nWith Workato One, Samsara aims to take on new levels of automation, intelligence, and self-service, enabling teams across Integrations, Data Engineering, GTM, Support, IT, and Finance to move from integration to orchestration and from automation to true business agility.<\/p>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\nThe migration wasn\u2019t just about speed. It was about embracing Workato’s powerful serverless architecture:<\/p>\n\n\n\n
\u201cWe went from cloud optimized [with MuleSoft], to cloud native [with Workato]\u2026 The whole management of virtual machines is gone. Everything is microservices-based, and therefore, much faster and more efficient from the engineering perspective. We have a serverless implementation on Workato, so we\u2019re not spending on infrastructure at all.\u201d<\/p>\n\n\n\n
Turning Skeptics Into “Believers”<\/strong><\/h2>\n\n\n\nChange is never easy, especially for engineers deeply invested in a legacy platform.<\/p>\n\n\n\n
\u201cI have over 100 years of MuleSoft [experience] on my team\u2026 It wasn’t easy to tell them, \u2018Okay, you\u2019re gonna move on to this new platform, something totally different that you\u2019ve never seen, never done before.’\u201d<\/p>\n\n\n\n
But even the those with deep allegiance to MuleSoft quickly discovered the power of Workato’s modern enterprise platform:<\/p>\n\n\n\n
\u201cAs someone who spent 10 plus years using MuleSoft, [my principal integration architect] admits that he was very skeptical at the beginning, but after some time working with Workato, first hand, he\u2019s a believer.\u201d<\/p>\n\n\n\n
\n\n\n\nCLIMBING TO NEW HEIGHTS WITH WORKATO<\/strong><\/h4>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccording to Shrujal Patel, Manager of Data Integrations at Samsara, “What did it for me was the speed of development, the scalable costs, and the pace of the Workato Product Team’s innovation. [Workato] is a modern platform and a vendor that delivers.”<\/p>\n\n\n\n
\u201cAs someone who spent 10+ years using MuleSoft, I admit that I was skeptical at the beginning but after some time working with Workato first hand, now I\u2019m a believer.”<\/strong><\/p>\n\n\n\n
\n\n\n\nExtensible Recipes, Observability, and Zero Failures<\/strong><\/h2>\n\n\n\nWorkato \u201crecipes\u201d were a revelation:<\/p>\n\n\n\n
\u201cThe recipe\u2019s business logic is completely decoupled from Workato execution runtime\u2026 so you don\u2019t have to worry about server availability. Here, we are completely decoupled, so there are no conflicts.\u201d<\/p>\n\n\n\n
Fully Embracing Cloud Native<\/strong><\/h2>\n\n\n\nWorkato leverages container technology thereby providing a lightweight, portable, and consistent environment for running the application, making it easier to manage and scale. This architecture allows developers to focus on business logic implementation with key operational concerns like guaranteed delivery and high availability handled by a robust distributed runtime, all deployed within containerized environments.<\/p>\n\n\n\n
WORKATO’S MICROSERVICES-BASED RUNTIME ARCHITECTURE<\/h4>\n\n\n\n<\/a><\/figure>\n\n\n\nVaishali went on to share \u201cnow that we\u2019ve embraced Workato\u2019s cloud-native platform, we are not limited by \u2018server-affinity.\u2019\u201d<\/p>\n\n\n\n
As with legacy platforms, server affinity between an application and runtime transfers the operational burden <\/strong>to the application developer, to consider factors like sizing, peak load estimation, performance, etc. Avoiding server affinity<\/strong> creates an auto-scalable infrastructure<\/strong> that constantly monitors the availability of “idle workers” to ensure the timely execution of every application event.<\/p>\n\n\n\nWORKATO’S AUTO-SCALABLE INFRASTRUCTURE<\/h4>\n\n\n\n<\/a><\/figure>\n\n\n\nExtensible Recipes, Observability, and Zero Failures<\/strong><\/h2>\n\n\n\nWorkato\u2019s \u201crecipes\u201d were a game changer:<\/strong><\/p>\n\n\n\n\u201cThe recipe\u2019s business logic is completely decoupled from Workato execution runtime\u2026 so you don\u2019t have to worry about server availability. Here, we are completely decoupled, so there are no conflicts.\u201d<\/p>\n\n\n\n
WORKATO RECIPES DECOUPLE BUSINESS LOGIC FROM EXECUTION RUNTIME<\/h4>\n\n\n\n<\/a><\/figure>\n\n\n\nWorkato’s<\/strong> Observability was another win:<\/strong><\/p>\n\n\n\n\u201cThere is quite a bit of auditing out of the box\u2026 job history and job entries, zero downtime, connector upgrades\u2026 We are also taking these logs and pushing them into Splunk and creating additional data accuracy dashboards.\u201d<\/p>\n\n\n\n
And the reliability?<\/strong><\/p>\n\n\n\n\u201cWe have deployed nearly a dozen projects in Workato\u2026 We have not had a single failure. Critical projects like implementing a brand new payroll system. We\u2019re not talking about something that is trivial. We\u2019re talking about something that impacts the entire organization. And we have not had a single failure period, not technically, not recipe-wise.\u201d<\/p>\n\n\n\n
2x Faster Development and Self-Service<\/strong><\/h2>\n\n\n\nThe impact on productivity was dramatic:<\/p>\n\n\n\n
\u201c[Workato is] two times faster [than MuleSoft], and it has given us the equivalent of three FTE\u2026 The biggest selling point for me, for Workato, was the ease of use and the speed of development from an engineering perspective.\u201d<\/p>\n\n\n\n<\/a><\/figure>\n\n\n\nWorkato\u2019s intuitive interface enabled self-service across teams:<\/p>\n\n\n\n
\u201cThese folks, these engineers, had never used an integration tool, period\u2026 The GTMS team also has two additional developers\u2026 and the corporate system has one person who\u2019s working on Workato as well.\u201d<\/p>\n\n\n\n
Looking Ahead: Workato One and the Agentic Future<\/strong><\/h2>\n\n\n\nAs Samsara looks to the future, Vaishali and her team are eager to build on their success by exploring the next generation of automation and Agentic AI with the Workato One platform.<\/p>\n\n\n\n
\u201cWe want to go forward with having a Workato platform that serves multi-purpose across Samsara,\u201d Vaishali shared. \u201cMy AI team is already scoping POCs for Workato One and the Agentic AI platform. We\u2019re excited to see how these innovations can help us deliver even more value, faster, and empower teams across the business.\u201d<\/p>\n\n\n\n<\/a><\/figure>\n\n\n\nWith Workato One, Samsara aims to take on new levels of automation, intelligence, and self-service, enabling teams across Integrations, Data Engineering, GTM, Support, IT, and Finance to move from integration to orchestration and from automation to true business agility.<\/p>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\nAccording to Shrujal Patel, Manager of Data Integrations at Samsara, “What did it for me was the speed of development, the scalable costs, and the pace of the Workato Product Team’s innovation. [Workato] is a modern platform and a vendor that delivers.”<\/p>\n\n\n\n
\u201cAs someone who spent 10+ years using MuleSoft, I admit that I was skeptical at the beginning but after some time working with Workato first hand, now I\u2019m a believer.”<\/strong><\/p>\n\n\n\n Workato \u201crecipes\u201d were a revelation:<\/p>\n\n\n\n \u201cThe recipe\u2019s business logic is completely decoupled from Workato execution runtime\u2026 so you don\u2019t have to worry about server availability. Here, we are completely decoupled, so there are no conflicts.\u201d<\/p>\n\n\n\n Workato leverages container technology thereby providing a lightweight, portable, and consistent environment for running the application, making it easier to manage and scale. This architecture allows developers to focus on business logic implementation with key operational concerns like guaranteed delivery and high availability handled by a robust distributed runtime, all deployed within containerized environments.<\/p>\n\n\n\n Vaishali went on to share \u201cnow that we\u2019ve embraced Workato\u2019s cloud-native platform, we are not limited by \u2018server-affinity.\u2019\u201d<\/p>\n\n\n\n As with legacy platforms, server affinity between an application and runtime transfers the operational burden <\/strong>to the application developer, to consider factors like sizing, peak load estimation, performance, etc. Avoiding server affinity<\/strong> creates an auto-scalable infrastructure<\/strong> that constantly monitors the availability of “idle workers” to ensure the timely execution of every application event.<\/p>\n\n\n\n Workato\u2019s \u201crecipes\u201d were a game changer:<\/strong><\/p>\n\n\n\n \u201cThe recipe\u2019s business logic is completely decoupled from Workato execution runtime\u2026 so you don\u2019t have to worry about server availability. Here, we are completely decoupled, so there are no conflicts.\u201d<\/p>\n\n\n\n Workato’s<\/strong> Observability was another win:<\/strong><\/p>\n\n\n\n \u201cThere is quite a bit of auditing out of the box\u2026 job history and job entries, zero downtime, connector upgrades\u2026 We are also taking these logs and pushing them into Splunk and creating additional data accuracy dashboards.\u201d<\/p>\n\n\n\n And the reliability?<\/strong><\/p>\n\n\n\n \u201cWe have deployed nearly a dozen projects in Workato\u2026 We have not had a single failure. Critical projects like implementing a brand new payroll system. We\u2019re not talking about something that is trivial. We\u2019re talking about something that impacts the entire organization. And we have not had a single failure period, not technically, not recipe-wise.\u201d<\/p>\n\n\n\n The impact on productivity was dramatic:<\/p>\n\n\n\n \u201c[Workato is] two times faster [than MuleSoft], and it has given us the equivalent of three FTE\u2026 The biggest selling point for me, for Workato, was the ease of use and the speed of development from an engineering perspective.\u201d<\/p>\n\n\n\n Workato\u2019s intuitive interface enabled self-service across teams:<\/p>\n\n\n\n \u201cThese folks, these engineers, had never used an integration tool, period\u2026 The GTMS team also has two additional developers\u2026 and the corporate system has one person who\u2019s working on Workato as well.\u201d<\/p>\n\n\n\n As Samsara looks to the future, Vaishali and her team are eager to build on their success by exploring the next generation of automation and Agentic AI with the Workato One platform.<\/p>\n\n\n\n \u201cWe want to go forward with having a Workato platform that serves multi-purpose across Samsara,\u201d Vaishali shared. \u201cMy AI team is already scoping POCs for Workato One and the Agentic AI platform. We\u2019re excited to see how these innovations can help us deliver even more value, faster, and empower teams across the business.\u201d<\/p>\n\n\n\n With Workato One, Samsara aims to take on new levels of automation, intelligence, and self-service, enabling teams across Integrations, Data Engineering, GTM, Support, IT, and Finance to move from integration to orchestration and from automation to true business agility.<\/p>\n\n\n\n
\n\n\n\nExtensible Recipes, Observability, and Zero Failures<\/strong><\/h2>\n\n\n\n
Fully Embracing Cloud Native<\/strong><\/h2>\n\n\n\n
WORKATO’S MICROSERVICES-BASED RUNTIME ARCHITECTURE<\/h4>\n\n\n\n
<\/a><\/figure>\n\n\n\nWORKATO’S AUTO-SCALABLE INFRASTRUCTURE<\/h4>\n\n\n\n
<\/a><\/figure>\n\n\n\nExtensible Recipes, Observability, and Zero Failures<\/strong><\/h2>\n\n\n\n
WORKATO RECIPES DECOUPLE BUSINESS LOGIC FROM EXECUTION RUNTIME<\/h4>\n\n\n\n
<\/a><\/figure>\n\n\n\n2x Faster Development and Self-Service<\/strong><\/h2>\n\n\n\n
<\/a><\/figure>\n\n\n\nLooking Ahead: Workato One and the Agentic Future<\/strong><\/h2>\n\n\n\n
<\/a><\/figure>\n\n\n\n