← ClaudeAtlas

gtm-apilisted

Execute Google Tag Manager API operations - create, update, delete, and manage tags, triggers, variables, and containers. Use when working with GTM programmatically, generating API calls, validating GTM configurations, publishing container versions, or automating tag management workflows.
produtoramaxvision/maxvision-utilities · ★ 0 · AI & Automation · score 58
Install: claude install-skill produtoramaxvision/maxvision-utilities
# Google Tag Manager API Execute GTM API operations with validation, error handling, and proper workflow patterns. ## Quick Start ### 1. Understand the Hierarchy ``` Account └── Container ├── Environments (deployment targets) ├── Versions (immutable snapshots) └── Workspaces (mutable, where changes happen) ├── Tags ├── Triggers └── Variables ``` **Critical rule:** All changes happen in workspaces; publishing creates versions. ### 2. Four Steps for Every Operation 1. **Read algorithm** → [instructions.md](references/instructions.md) 2. **Copy template** → [request-templates.md](references/request-templates.md) 3. **Validate** → [validation-rules.md](references/validation-rules.md) 4. **Execute** with error handling → [workflows.md](references/workflows.md) --- ## Core Execution Workflow ### Step 1: Validate Inputs ``` BEFORE any API call: 1. Validate required fields present 2. Validate field types (strings, arrays, etc.) 3. Verify entity references exist (trigger IDs, variable names) 4. Check OAuth scopes sufficient 5. Confirm container type supports operation ``` ### Step 2: Get or Create Workspace ``` workspaces = GET /accounts/{account_id}/containers/{container_id}/workspaces IF workspaces is empty: workspace = POST /workspaces with {"name": "Default Workspace"} ELSE: workspace = workspaces[0] Store: workspace_id, workspace_path ``` ### Step 3: Execute Operation Use the appropriate reference file: - **Creati