Actions11
- Event Actions
- Element Actions
- Listing Actions
- Event Template Actions
Overview
This node interacts with the Monterosa Control API to manage various resources within a Monterosa project. Specifically, for the Element resource and the Delete Element operation, it deletes an element identified by its unique ID from a specified Monterosa project.
Typical use cases include:
- Automating cleanup of unused or obsolete elements in a content management workflow.
- Integrating element deletion into larger automation pipelines where elements need to be programmatically removed based on external triggers or conditions.
- Managing content lifecycle by removing elements that are no longer relevant or needed.
For example, you might use this node to delete a specific content element after it has been archived or replaced, ensuring your project stays organized and up-to-date.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of your Monterosa project where the element exists. |
| Localization | Specifies the localization context for custom fields; defaults to "all" if not specified. |
| Element ID | The unique identifier (UUID) of the element to delete (e.g., 123e4567-e89b-12d3-a456-426614174000). |
Output
The node outputs a JSON object representing the result of the delete operation. Typically, this will confirm whether the element was successfully deleted or provide error details if the deletion failed.
No binary data output is expected from this operation.
Dependencies
- Requires an active connection to the Monterosa Control API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The user must provide a valid Project ID and Element ID.
- Network access to Monterosa's API endpoints is necessary.
Troubleshooting
- Invalid Project ID or Element ID: If these IDs are incorrect or do not exist, the API will return an error. Verify the IDs before running the node.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to delete elements.
- Network Issues: Failures to connect to the API endpoint may occur due to network problems or incorrect environment configuration.
- Localization Parameter: While optional, specifying an invalid localization might cause unexpected behavior; use "all" or valid localization codes.
- Common Error Messages:
- "Failed to fetch project data" — Check Project ID and API credentials.
- "Element not found" — Confirm the Element ID exists in the specified project.
- "Unauthorized" — Verify API token validity and permissions.
Resolving these typically involves verifying input parameters, checking credentials, and ensuring network connectivity.
Links and References
- Monterosa Control API Documentation (general reference for API endpoints and authentication)
- n8n Documentation on creating and using API credentials
- UUID format reference for Element ID validation