Actions11
- Event Actions
- Element Actions
- Listing Actions
- Event Template Actions
Overview
The "Get Events" operation of the Monterosa Automation node retrieves event data from a specified Monterosa project. It allows users to query events filtered by their state (e.g., future, current, past), control pagination, sorting order, and optionally include related data such as event statistics or project details. This node is useful for automating workflows that require up-to-date event information, such as syncing event calendars, generating reports, or triggering actions based on event schedules.
Practical examples:
- Fetching all upcoming events in a project to display on a website.
- Retrieving past events with statistics for analytics dashboards.
- Getting current events sorted by start time to notify users in real-time.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of your Monterosa project. |
| Filter by State | Filter events by their state. Options: Future, Current, On Demand, Past. |
| Only Listings | Boolean flag to retrieve only events that are included in listings. |
| Include Relations | Additional related data to include in the response. Options: Stats (event statistics), Project (project details). |
| Page Cursor | Pagination cursor string to fetch the next page of results. |
| Results Per Page | Number of events to retrieve per request (1 to 100). |
| Sort Order | Order events by start time. Options: Newest First, Oldest First. |
| Localization | Localization setting for custom fields; defaults to "all". |
Output
The output is an array of JSON objects representing events retrieved from the Monterosa API. Each event object contains standard event properties such as identifiers, timestamps, and metadata. If requested via the "Include Relations" property, additional nested objects for event statistics or project details may be present.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Monterosa Control API.
- Needs the Project ID to specify which project's events to query.
- Network access to Monterosa's API endpoints.
- Proper configuration of environment (e.g., API base URL) through node credentials.
Troubleshooting
- Invalid Project ID or Credentials: Errors fetching project or app data indicate incorrect project ID or expired/invalid API token. Verify credentials and project ID.
- Pagination Issues: Using an invalid or expired page cursor may result in empty or error responses. Ensure cursors are used as provided by previous responses.
- API Rate Limits or Network Errors: Temporary failures fetching data might occur due to network issues or rate limiting. Retry after some time.
- Incorrect Filter or Sort Values: Providing unsupported filter states or sort options can cause errors. Use only the documented options.
- Missing Required Fields: Omitting the required Project ID will prevent execution.
Links and References
- Monterosa Control API Documentation (general reference for API endpoints and data structures)
- n8n Documentation on Custom Nodes and API Integration (for configuring credentials and usage)