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 "Update Transformation" operation in the Google Tag Manager (GTM) node allows users to update an existing transformation within a GTM workspace. Transformations in GTM are used to modify or manipulate data before it is sent to tags, triggers, or variables, enabling more flexible and powerful tag management.
This operation is beneficial when you need to programmatically change the configuration of a transformation, such as updating its rules, parameters, or other settings, without manually editing it in the GTM interface. For example, you might automate updates to transformations based on changing business logic or integrate GTM transformation updates into a larger automated workflow.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the GTM Account where the transformation exists. |
| Container ID | The unique identifier of the GTM Container that holds the workspace with the transformation. |
| Workspace ID | The unique identifier of the GTM Workspace containing the transformation to update. |
| Transformation ID | The unique identifier of the specific GTM Transformation to update. |
| Optional Query Parameters | Additional optional parameters for the API request, such as allowUserPermissionFeatureUpdate, fingerprint, etc. These control specific behaviors or features during the update. |
| Request Body | A JSON object representing the updated properties of the transformation. This contains the new configuration details to apply. |
Output
The output is a JSON array containing the updated transformation object returned by the GTM API. This object reflects the current state of the transformation after the update, including all its properties and metadata.
If the operation succeeds, the output will include the full details of the updated transformation entity.
Dependencies
- Requires valid Google Tag Manager API credentials with OAuth2 authentication.
- The node must be configured with these credentials to authorize API requests.
- Network access to the Google Tag Manager API endpoint (
https://www.googleapis.com/tagmanager/v2).
Troubleshooting
- Missing Required IDs: Errors will occur if any of the required identifiers (Account ID, Container ID, Workspace ID, Transformation ID) are missing. Ensure all these fields are correctly filled.
- Invalid Credentials: If the OAuth2 credentials are missing or invalid, the node will throw an error indicating missing or unauthorized credentials.
- API Errors: Any errors returned from the GTM API (e.g., permission denied, invalid request body) will be surfaced with messages prefixed by "Error calling GTM API". Review the message and stack trace for details.
- Fingerprint Mismatch: If providing a fingerprint in optional query parameters, it must match the stored fingerprint; otherwise, the update will fail.
- Incorrect Request Body: The JSON in the request body must conform to the expected structure of a GTM transformation. Invalid JSON or incorrect fields may cause API errors.
Links and References
- Google Tag Manager API Documentation - Transformations
- Google Tag Manager Concepts
- n8n Documentation - Google Tag Manager Node
This summary focuses specifically on the "Update Transformation" operation of the GTM node, describing its purpose, inputs, outputs, dependencies, and common troubleshooting points based on static analysis of the provided source code and property definitions.