carto-create-workflow

CARTO Workflows is a visual DAG authoring app that compiles to warehouse SQL. Each workflow runs inside a connected warehouse — no CARTO compute is involved at execution time. This skill covers the full lifecycle: building the DAG (the bulk of this file), operating it via the CLI (CRUD, schedules), and cross-profile copy (dev → prod promotion, customer-segregated workspaces via carto workflows copy) — see the references below.

Workflows vs Builder — distinct apps. This skill targets Workflows (CARTO's DAG/orchestration app, /workflows/<id> in the URL). Builder is the separate map-authoring app (/builder/<id>). When this skill mentions "the Workflows canvas", "in Workflows", or "the DAG view", that is never Builder — they're different products that share an org and connections but nothing else. Workflow output (a result table with geometry) is typically visualised in Builder afterward; that's the only place the two apps connect.

For one-off ad-hoc SQL, use carto-query-datawarehouse — workflows are for repeatable, scheduled, multi-step DAGs.

Access-path routing. The interactive lifecycle maps to MCP tools on an OAuth-authenticated MCP session: create_workflow, update_workflow (method=update|share|unshare|publish|unpublish), validate_workflow (method=validate|verify|to_sql), read_workflows (method=list|get|list_mcp_tools|get_mcp_tool), run_workflow (method=run|status|results), schedule_workflow (method=add|update|remove), and read_workflow_components (method=list|get — the component catalog). The phases below apply on either path — where a step names a carto workflows command, substitute the matching MCP tool (e.g. verify-remote → validate_workflow method=verify). Stay on the CLI for scripting/CI, bundle-schema introspection (carto workflows schema — no MCP equivalent), cross-profile copy (carto workflows copy — CLI-only), and usage-log auditing (carto activity query — CLI-only). Fall back to the CLI when the server isn't attached, or when the MCP session is token-authenticated — authoring/admin tools are hidden there; only run_workflow and validate_workflow remain. Detection signals: carto-basics/references/access-paths.md.

Bundle structure, component schemas, input formats, and gotchas are all served live — by the CLI (carto workflows schema / components) or, on the MCP path, by read_workflow_components (method=list|get). Never hardcode or assume them. Live introspection is the source of truth.

Live introspection (use before reaching for any reference file). On MCP, read_workflow_components (method=list|get) covers the component rows; the bundle/DAG schema sections are CLI-only.