Monterosa Automation

Interact with Monterosa Control API

Actions11

Overview

The node "Monterosa Automation" integrates with the Monterosa Control API to manage various resources such as Events, Elements, Listings, and Event Templates within a Monterosa project. Specifically, for the Event resource and the Get Event History operation, this node retrieves the historical data or audit trail related to a particular event in a Monterosa project.

This operation is useful when you want to track changes, updates, or actions performed on an event over time. For example, it can help monitor who modified an event, what changes were made, and when these changes occurred, which is valuable for auditing, debugging, or compliance purposes.

Practical examples:

  • Fetching the change history of a marketing campaign event to understand its evolution.
  • Auditing modifications on an event before publishing it live.
  • Debugging issues by reviewing past updates to an event.

Properties

Name Meaning
Project ID The unique identifier of your Monterosa project where the event exists.
Localization Specifies the localization context for custom fields; default is "all" (all localizations).
Event ID The unique identifier of the event whose history you want to retrieve.

Output

The output of the Get Event History operation is a JSON object containing the historical records of the specified event. This typically includes details such as timestamps, user actions, changes made, and possibly metadata about each change entry.

The exact structure depends on the API response but generally provides a chronological list of event modifications.

The node does not output binary data for this operation.

Example output snippet (conceptual):

{
  "eventId": "12345",
  "history": [
    {
      "timestamp": "2024-01-01T12:00:00Z",
      "user": "user@example.com",
      "action": "updated",
      "changes": {
        "fieldName": {
          "oldValue": "Old Value",
          "newValue": "New Value"
        }
      }
    },
    ...
  ]
}

Dependencies

  • Requires an active connection to the Monterosa Control API.
  • Needs a valid API authentication token (provided via credentials) with access rights to the specified project.
  • The Project ID must be valid and correspond to an existing Monterosa project.
  • Network connectivity to Monterosa's API endpoints.
  • No additional external services are required beyond the Monterosa API.

Troubleshooting

  • Invalid Project ID or Event ID: If the provided IDs are incorrect or do not exist, the API will likely return errors or empty results. Verify that the IDs are correct.
  • Authentication Errors: Ensure the API key or token used in credentials is valid and has sufficient permissions.
  • Network Issues: Connectivity problems may cause fetch failures. Check internet connection and API endpoint accessibility.
  • Localization Parameter: Using unsupported localization values might result in incomplete or no data. Use "all" or valid localization codes.
  • API Rate Limits: Excessive requests might lead to throttling; consider adding delays or retries if needed.

Common error messages might include:

  • "Failed to fetch project data" – check Project ID and credentials.
  • "Failed to fetch event history" – verify Event ID and API availability.
  • HTTP status codes like 401 (Unauthorized), 404 (Not Found), or 429 (Too Many Requests).

Resolving these usually involves verifying input parameters, credentials, and network conditions.

Links and References

Discussion