Actions28
- Action Actions
- Country Actions
- Event Actions
- Language Actions
- Product Actions
- Profile Actions
- Task Actions
- Timezone Actions
- User Management Actions
- kSuite Actions
Overview
This node interacts with the Infomaniak API to retrieve multiple events based on various filter criteria. The "Get Many" operation under the "Event" resource allows users to fetch a list of events filtered by date range, event type, status, language locale, and other specific flags such as whether the event is a cyber attack or if automatic events should be shown.
This node is beneficial in scenarios where you want to monitor or analyze events from Infomaniak's system, such as tracking planned or ongoing events, filtering for security-related incidents (cyber attacks), or localizing event descriptions in a preferred language.
Practical examples:
- Fetch all "In Progress" internal events starting from a specific date to monitor current activities.
- Retrieve public events in English that are flagged as cyber attacks for security alerting workflows.
- Include deleted (trashed) events in reports for audit purposes.
Properties
| Name | Meaning |
|---|---|
| Event Filters | A collection of filters to narrow down the events returned. Contains the following options: |
| - Date From | Filter events starting from this date (inclusive). |
| - Date To | Filter events up to this date (inclusive). |
| - Event Type | Filter by event type. Options: Internal, Public, Server, Streaming. |
| - Status | Filter by event status. Options: In Progress, Planned, Reviewed, Terminated. |
| - Locale | Language for event descriptions. Options: German, English, Spanish, French, Italian. |
| - Is Cyber Attack | Boolean flag to filter only cyber attack events. |
| - Show Auto | Boolean flag to include automatic events in the results. |
| - With Trashed | Boolean flag to include deleted (trashed) events in the results. |
| - User ID | Filter events associated with a specific user ID (number). |
Output
The output is an array of JSON objects representing the events retrieved from the Infomaniak API. Each object corresponds to an event and contains all the data fields provided by the API for that event.
The node does not output binary data; it strictly returns JSON-formatted event data.
Dependencies
- Requires an API key credential for authenticating requests to the Infomaniak API.
- The node makes HTTP GET requests to the Infomaniak API endpoint
https://api.infomaniak.com/2/events. - Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing API token will cause authentication failures.
- Incorrect date formats in filters may lead to no results or errors.
- Requesting too many events without pagination might result in timeouts or rate limiting.
Error messages:
"Failed to retrieve events": General failure to get events from the API. Check network connectivity and API token validity."Event with ID ... not found": Occurs if a specific event ID is requested but does not exist.
Resolutions:
- Verify that the API key credential is correctly set and has sufficient permissions.
- Ensure date filters are valid ISO 8601 datetime strings.
- Use the "Return All" option carefully or apply limits to avoid large data loads.
- If encountering rate limits, implement retry logic or reduce request frequency.
Links and References
- Infomaniak API Documentation (general reference for endpoints and parameters)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are made within n8n)
If you need details about other operations or resources, feel free to ask!