CARTO Workflows is currently available in beta and it might be subject to changes. We kindly welcome all user feedback to help us deliver you the best possible tool, please use this survey to share with us your experience with Workflows.
The CARTO Workspace includes now a tool that provides a visual language to design and execute multi-step spatial analytics procedures: CARTO Workflows.
With Workflows, our mission is to bring spatial analytics to a broader audience of data analysts and business users, and to democratize access to advanced Location Intelligence.
This tool, as the rest of the platform, is fully cloud native; running on Spatial SQL in your own data warehouse, and leveraging CARTO’s Analytics Toolbox and the other components of our technology stack.
CARTO Workflows reduces the complexity and the high dependence on specialist knowledge. Users can leverage the scalability of cloud data warehouses through the use of spatial SQL without needing to write SQL code yourself. It opens up analytical modeling to all roles and skill levels, through a simple, familiar user interface.
In the Workflows main page, in order to create a new workflow, just click “+ New workflow”. This will open the CARTO Workflows user interface and you can start creating your analysis.
The following are the main sections of the CARTO Workflows user interface (which are also illustrated in the image above):
- 1.Workflow canvas: the area in which you will be adding the different components and data sources and you will connect them in order to build your workflow;
- 2.Components & sources explorer: here you will find all the available resources to build your workflows. To use them, drag and drop them from here to the workflow designer panel;
- 3.Results panel: in this section you will be able to analyze the results generated by the different steps of your workflow. You will also be able to see the messages from the execution logs and the SQL code generated by your workflow;
- 4.Node panel: this section allows the user to enter the different parameters needed to execute some components and it also provides extra information about the elements that have been configured in the workflow.