UiPath Adds Two-Way Snowflake Automation Integration
Snowflake can trigger UiPath work while UiPath can read governed Snowflake data without copying it, but operating results remain unproven.
Edited by Tyronne Panaino
UiPath announced a two-way integration with Snowflake on September 30, connecting Snowflake data to UiPath automations and allowing work to be triggered from Snowflake. The release targets joint enterprise customers that want AI agents and workflows to operate against governed data without first copying it into another platform.
The change matters because it extends an existing UiPath connection to Snowflake Cortex AI into reciprocal operational paths. The UiPath announcement establishes the integration and current marketplace availability, but it does not provide independent evidence about performance, security outcomes or adoption.
Snowflake data can feed UiPath without a copy
UiPath says Data Fabric can read and model data directly from Snowflake while the underlying records remain in Snowflake. Enterprise context can then flow into the UiPath platform for agents and automations. The company describes existing access controls, policies and auditability as continuing to govern that data path.
That architecture is more specific than a generic data connector. It is meant to let a workflow use current Snowflake context without creating another data copy that can drift out of date. For administrators, however, avoiding a copy does not eliminate access risk. Teams still need to verify which Snowflake objects are visible, which identities authorize each request, and whether UiPath's audit trail captures the actions their controls require.
Automation can also start from Snowflake
The reciprocal path lets Snowflake trigger UiPath automations. UiPath also names native Snowflake Cortex connectivity in Integration Service, with Delegate and Cartographer using Snowflake data during automation discovery and design.
Snowflake CoCo gains another route through the integration. Customers running CoCo can call skills from UiPath's agentic library to execute automation, while those skills remain provided through the integration rather than being built into CoCo itself. This creates a practical boundary for buyers: availability of CoCo does not by itself establish access to every UiPath skill, configuration or governed workflow.
The combination could reduce handoffs between a data platform and an automation platform. That is an architectural implication of the documented paths, not a measured productivity result. The announcement supplies no comparison of latency, task completion, operating cost or failure rates before and after the integration.
Marketplace availability does not answer every deployment question
UiPath is now listed in the Snowflake Marketplace, giving existing Snowflake customers a direct discovery and procurement route for the orchestration platform. The announcement also places UiPath Maestro around actions performed by agents, robots and people, presenting the integration as part of a governed operating layer rather than a standalone data export.
Important implementation details remain open. The fetched evidence does not specify pricing, plan eligibility, supported regions, exact deployment prerequisites or the full permission model for each named surface. It also does not include independent security testing or customer results. Enterprises evaluating the release should test read and trigger permissions separately, confirm what happens when a policy blocks an action, and verify whether audit records span both platforms in the form their compliance process expects.
What changed from the prior UiPath platform release
Earlier UiPath updates established Data Fabric as a context layer and described broader governance and connectivity features. The September 30 event adds a named Snowflake implementation with two directions of operation: Snowflake data can enter UiPath workflows, and Snowflake can initiate UiPath automation. CoCo access to UiPath skills and the marketplace listing are also part of this specific release.
The next useful evidence will be detailed product documentation, eligibility tables, customer deployment reports and measured behavior under realistic workloads. Those checkpoints will show whether the integration reduces duplicated data and manual handoffs without weakening access boundaries or creating new operational dependencies.
Status
Confirmed. UiPath's official release establishes the September 30 integration, the reciprocal data and automation paths, named product surfaces and marketplace availability. Internal confidence is medium because the evidence is first-party and this run found no independent performance, security or production evaluation.
Sources
Update note: Last reviewed 2026-10-03. We will revise this post if the companies publish detailed eligibility, independent evaluations or material changes to the integration.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.