Actions11
- Event Actions
- Element Actions
- Listing Actions
- Event Template Actions
Overview
The "Get Elements" operation of the Monterosa Automation node retrieves elements associated with a specified Monterosa project. This operation is useful for workflows that need to fetch and process content elements such as events, listings, or other custom data types managed within a Monterosa project.
Typical use cases include:
- Synchronizing content elements from Monterosa into another system.
- Filtering elements by their state (e.g., current, future, cancelled) to trigger specific automation based on element lifecycle.
- Fetching localized versions of elements for multi-language content management.
- Including statistical data about elements to analyze usage or performance.
For example, you might use this node to get all currently active event elements in a project to update an external calendar or to retrieve non-scheduled elements for editorial review.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of your Monterosa project. |
| Localization | The localization setting for custom fields; can be set to "all" or a specific locale code. |
| Event ID | (Optional) The ID of a specific event to filter elements related to that event. |
| Filter Elements by State | Filter elements by one or more states: Cancelled, Current, Future, Non Scheduled, On Demand, Past, Revoked. Default is "Non Scheduled". |
| Include in Latest Results | Boolean flag indicating whether to include only elements that are part of the latest results. |
| Include Stats | Boolean flag indicating whether to include statistical data about each element in the response. |
Output
The output is an array of JSON objects representing the retrieved elements. Each object contains the element's data fields as provided by the Monterosa API, including metadata and optionally statistics if requested.
If the "Include Stats" property is enabled, additional statistical information about each element will be included in the output.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Monterosa Control API.
- Needs the Project ID to identify which Monterosa project to query.
- Network access to Monterosa API endpoints.
- Proper configuration of environment (e.g., environment selection for API URL) via credentials.
Troubleshooting
- Invalid Project ID or Credentials: If the Project ID is incorrect or the API key is invalid/expired, the node will fail to fetch elements. Verify the Project ID and ensure the API key has proper permissions.
- No Elements Returned: If filters are too restrictive (e.g., filtering by states that have no matching elements), the output may be empty. Adjust filter settings accordingly.
- API Rate Limits or Network Issues: Temporary network failures or rate limiting by the Monterosa API can cause errors. Retry after some time or check network connectivity.
- Localization Not Found: Specifying a localization that does not exist in the project may result in missing or empty data. Confirm available localizations in your project.
Links and References
- Monterosa Control API Documentation (general reference for API endpoints and data structures)
- Monterosa Project Management Guide (for understanding projects, elements, and states)
- n8n Documentation on Custom Nodes and API Integration