Actions11
- Event Actions
- Element Actions
- Listing Actions
- Event Template Actions
Overview
The "Create Event" operation of the Monterosa Automation node allows users to create new events within a specified Monterosa project. This is useful for automating event scheduling and management workflows, such as launching marketing campaigns, scheduling content releases, or coordinating timed activities in digital projects.
Typical use cases include:
- Creating an event that starts manually when triggered.
- Scheduling an event to start at a specific time with a defined duration.
- Adding custom metadata fields to events for enhanced tracking or integration with other systems.
For example, a user might automate the creation of a promotional event that starts at a fixed clock time and lasts for 2 hours, including custom tags or notes relevant to the campaign.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of your Monterosa project where the event will be created. |
| Event Name | The name/title of the event to be created. |
| Event Start Mode | How the event start time is determined; options are: "manual" (start triggered manually) or "clock" (start at scheduled time). |
| Event Start At | The planned start timestamp of the event (required if start mode is "clock"). |
| Event End Time | The planned end timestamp of the event (optional, used if start mode is "clock"). |
| Duration | Duration of the event in minutes (used if start mode is "manual"). |
| Custom Fields | A collection of custom key-value pairs to add additional metadata or information to the event. |
| Localization | Specifies localization context for the custom fields; default is "all". |
Output
The node outputs JSON data representing the newly created event object as returned by the Monterosa Control API. This typically includes details such as event ID, name, start and end times, status, and any custom fields set during creation.
If the node supports binary data output (not indicated here), it would represent associated files or media related to the event, but this operation primarily deals with JSON event data.
Dependencies
- Requires an active API authentication token credential for the Monterosa Control API.
- Needs a valid Project ID corresponding to a Monterosa project accessible by the authenticated user.
- Network access to Monterosa's API endpoints.
- Proper configuration of environment (e.g., production or staging) via the API credential settings.
Troubleshooting
- Invalid Project ID: If the provided Project ID is incorrect or inaccessible, the API call will fail. Verify the Project ID and ensure the API token has permissions for that project.
- Missing Required Fields: The event name and project ID are mandatory. Omitting these will cause errors.
- Incorrect Date/Time Format: When using "clock" start mode, ensure that the "Event Start At" and "Event End Time" fields are valid ISO 8601 timestamps.
- API Authentication Errors: Ensure the API token credential is valid and not expired.
- Network Issues: Connectivity problems can cause fetch failures; check network and proxy settings.
Common error messages usually relate to authorization failures, invalid parameters, or resource not found, and can be resolved by verifying credentials, input values, and project existence.
Links and References
- Monterosa Control API Documentation (general reference for API endpoints and data models)
- n8n Documentation on creating custom nodes and using API credentials
- ISO 8601 Date and Time Format Reference (for correct timestamp formatting)