Q3 2025

Control Components in Workflows: Conditional Split & Success/Error Split

August 12th, 2025

New Workflows

We’ve added two new control components to CARTO Workflows that make it easier to control how your workflows execute and respond to different scenarios.

• Conditional Split – Direct your workflow into If and Else branches based on a condition you define. Build the condition with a simple UI (column + aggregation + operator + value) or use a custom SQL expression for more complex logic. Some usage examples:

  • “If the count of underserved households in a service area is greater than 500, trigger a fiber expansion workflow; otherwise plan for wireless coverage.”

  • “If the average property value in a high-risk flood zone is above $1M, apply the high-risk pricing model; otherwise, use the standard pricing model.”

• Success/Error Split – Branch execution depending on whether the previous step ran successfully or failed. Some usage examples:

  • “If network quality metrics fail to load, send an alert; otherwise continue with churn prediction.”

  • “If address geocoding fails, switch to a backup geocoder; otherwise proceed with claims analysis.”

These components let you build workflows that adapt to your data, add robust error-handling, and reduce the need for manual monitoring — helping teams act faster on reliable insights.

Separation of working locations for improved data governance

August 5th, 2025

Improvement Workspace

We have introduced a clearer separation of datasets/schemas that CARTO creates and manages in connected data warehouses. This change improves data governance and prevents persistent objects from being stored alongside temporary workflow tables.

New locations per connection:

• CARTO temp location – stores only temporary tables created during workflow execution.

• CARTO Workspace location – stores persistent objects related to workflows, such as API stored procedures and imported files.

• CARTO Extensions location – stores Extension Package resources, including shared stored procedures and metadata. Only for BigQuery and Snowflake.

Additional notes:

• For connections shared requiring Viewer Credentials, carto_temp_<user> and carto_workspace_<user> are created per user.

• The Extensions location is always shared across all users in a connection, ensuring consistent access to installed packages.

• Default names can be overridden in the connection’s advanced options.

• Locations are automatically created as needed (CREATE IF NOT EXISTS).

This update applies to all supported warehouses. Find specific documentation on the Advanced settings section for each warehouse in the Connections section of the documentation.

Support for adding sources without associated layer in Builder

July 29th, 2025

New Builder

Editor users can now add data sources to a Builder map without displaying associated layers. These sources can be used to power widgets, SQL parameters, and even be used by AI Agents to generate insights.

This is especially useful when a dataset is needed for interactivity or calculations, but not for visualization. It helps keep your maps cleaner, more focused, and easier to maintain.

Organization Governance Settings for Admins

July 17th, 2025

New Workspace

Admins can now set up custom governance policies through the new Governance section in Settings. These controls give you the tools to manage data access, sharing, and feature usage across your organization with precision.

Control who can create new Data Warehouse connections with granular settings for providers and authentication methods. Manage connection sharing, disable the CARTO Data Warehouse, and fine-tune Builder features like Download PDF report, export viewport data, and more!

To see all the new settings, check our section on Organization Governance.

Support for Widgets linked to Raster sources in Builder

July 15th, 2025

Improvement Builder

You can now use Widgets with raster sources in Builder — just like you already can with vector sources. This improvement allows for richer exploration and analysis of raster sources stored in your data warehouse directly from the map.

Use the Formula Widget to calculate metrics like tree coverage in your current view. Leverage Category and Pie Widgets to list distinct values in your raster layer, or use the Histogram Widget to explore data distributions such as precipitation.

These widgets can also be used for filtering, letting you interactively refine what’s shown on the map and extract insights more effectively.

Learn more in our documentation.

Audit all queries with the CARTO SQL audit trails

July 8th, 2025

New Workspace

When a map or workflow is opened, CARTO launches a set of SQL queries to your data warehouse to visualize your data and run your analysis. And from now on, each of those SQL queries will contain a rich audit trail in the form of SQL comments at the beginning or the end of the query.

This audit information allows data warehouse administrators to monitor CARTO and answer questions such as: How many queries did CARTO run in a period of time? Which workflows or maps have processed more data? What are some common performance or cost patterns?

To start using this information in your audits, check our Auditing SQL queries documentation.