Inputs
Output
Type:Dict
Returns {resolved: true} on success (the API returns an empty body).Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Resolves one merge conflict in a Google Tag Manager workspace by submitting the entity in its desired resolved state
| App | Google Tag Manager |
| Operation ID | gtm_resolve_workspace_conflict |
| Type | Action |
| Connection | gtm (required) |
| Credits per run | 1 |
| Agent / MCP tool | Yes |
| Requires approval | Yes (write operation) |
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
account | DynamicAccount | Yes | - | Select the Google Tag Manager account. |
container | DynamicAccount | Yes | - | Select the container. |
workspace | DynamicAccount | Yes | - | Select the workspace with the merge conflict. |
entity_payload | object or string | Yes | - | Resolved Entity (object or JSON string) matching the Google Tag Manager API v2 Entity spec: exactly one entity key (tag, trigger, variable, folder, client, transformation, zone, gtagConfig, or builtInVariable) holding the entity in its desired resolved state, plus changeStatus. Take the entity from a mergeConflict entry returned by gtm_sync_workspace or gtm_get_workspace_status, edit it to the state you want, and pass it here. |
fingerprint | string | No | - | Optional fingerprint of the entity_in_workspace from the mergeConflict entry. When provided, the resolve only succeeds if the workspace entity has not changed since. |
Dict
Returns {resolved: true} on success (the API returns an empty body).