workspace_resolve_conflict
Resolve merge conflicts in a GTM workspace by providing the resolved entity body and its type; the API automatically wraps it in the correct envelope.
Instructions
Resolve a merge conflict for a workspace entity. You supply the resolved entity body plus its type; the GTM API wraps it in an Entity envelope ({ "tag": {...} } / { "trigger": {...} } / …), which this tool builds for you. NOTE: This is a complex operation — review the GTM UI conflict resolution first.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | Yes | Must be true to confirm this write operation. | |
| accountId | Yes | The GTM account ID. | |
| entityJson | Yes | JSON string of the RAW entity body (e.g. the tag object itself), NOT the Entity envelope — it is wrapped under entityType for you. If you pass an already-wrapped { "<entityType>": {...} } object it is used as-is. | |
| entityType | Yes | Which Entity slot the resolved body fills. The resolve_conflict API takes an Entity envelope, so a resolved tag is sent as { "tag": {...} }, a trigger as { "trigger": {...} }, etc. | |
| containerId | Yes | The GTM container ID. | |
| fingerprint | Yes | The workspace fingerprint at the time of conflict resolution. | |
| workspaceId | Yes | The GTM workspace ID. | |
| changeStatus | No | How the resolved entity changed relative to the base version (added/deleted/modified/none). Optional. |