Actions102
- Account Actions
- Built-In Variable Actions
- Client Actions
- Container Actions
- Destination Actions
- Environment Actions
- Folder Actions
- Google Tag Configuration Actions
- Tag Actions
- Template Actions
- Transformation Actions
- Trigger Actions
- User Permission Actions
- Variable Actions
- Version Actions
- Workspace Actions
- Zone Actions
Overview
The "Resolve Conflict Workspace" operation in the Google Tag Manager (GTM) node is designed to resolve merge conflicts within a GTM workspace entity. When multiple changes are made to the same workspace entity, conflicts can arise that need manual resolution. This operation updates the conflicted entity with a resolved version provided in the request, effectively merging changes and allowing the workspace to proceed without conflict.
This node operation is beneficial in scenarios where teams collaborate on GTM container workspaces and need to programmatically handle merge conflicts during development or deployment workflows. For example, if two users modify the same tag or variable in a workspace, this operation helps automate the conflict resolution process by applying the resolved entity state.
Properties
| Name | Meaning |
|---|---|
| Account ID | The GTM Account ID where the workspace exists. |
| Container ID | The GTM Container ID containing the workspace. |
| Workspace ID | The GTM Workspace ID where the conflict needs to be resolved. |
| Optional Query Parameters | Additional optional parameters for the API call (e.g., allowUserPermissionFeatureUpdate). |
| Request Body | JSON object representing the resolved entity data to update the conflicted workspace entity with. |
Output
The output is a JSON object representing the updated workspace entity after resolving the conflict. It contains the current state of the entity as stored in GTM following the resolution.
No binary data is involved in this operation.
Dependencies
- Requires an active Google Tag Manager API OAuth2 credential configured in n8n.
- The node makes authenticated HTTP requests to the Google Tag Manager API endpoint:
https://www.googleapis.com/tagmanager/v2. - Proper permissions on the GTM account, container, and workspace are necessary to perform conflict resolution.
Troubleshooting
- Missing Required IDs: Errors will occur if Account ID, Container ID, or Workspace ID are not provided. Ensure these are correctly set.
- Invalid or Missing Credentials: The node requires valid OAuth2 credentials for Google Tag Manager API access. Verify credentials are configured and authorized.
- Conflict Resolution Failure: If the request body does not correctly represent the resolved entity or if the fingerprint/version is outdated, the API may reject the update. Make sure the resolved entity data is accurate and up-to-date.
- API Errors: Any errors returned from the Google Tag Manager API will be surfaced with messages prefixed by "Error calling GTM API". Review the error message and stack trace for details.