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 "actions" available in the system. Specifically, the "Get Many" operation under the "Action" resource fetches a list of actions, optionally filtered by a search term. It supports returning all results or limiting the number of returned items.
Common scenarios where this node is beneficial include:
- Automating workflows that need to process or analyze available actions from Infomaniak.
- Integrating Infomaniak action data into other systems or dashboards.
- Filtering and retrieving specific sets of actions based on search criteria for reporting or decision-making.
For example, you might use this node to get all actions related to a particular keyword or to fetch a limited number of recent actions for review.
Properties
| Name | Meaning |
|---|---|
| Search | A string term to filter the list of actions by matching relevant fields. |
| Return All | Boolean flag indicating whether to return all matching actions or limit the results. |
| Limit | Maximum number of actions to return if "Return All" is false. Must be at least 1. |
Output
The output is an array of JSON objects representing individual actions retrieved from the Infomaniak API. Each object contains the details of one action as provided by the API.
- The
jsonfield contains the action data. - There is no binary data output for this operation.
If the API call fails or no actions are found, the node throws an error unless configured to continue on failure.
Dependencies
- Requires an API authentication token credential for Infomaniak API access.
- Makes HTTP GET requests to the endpoint:
https://api.infomaniak.com/1/actions. - The node expects the API token to be provided via credentials configured in n8n.
Troubleshooting
- Failed to retrieve actions: This error indicates the API request did not succeed. Check your API token validity and network connectivity.
- Empty result set: If no actions match the search term, the output will be empty. Try broadening the search or removing the filter.
- Limit vs Return All: If "Return All" is false but the limit is set too low, you may receive fewer results than expected.
- API rate limits or permissions: Ensure the API token has sufficient permissions and that you are not hitting rate limits imposed by Infomaniak.
Links and References
- Infomaniak API Documentation (general reference for endpoints and authentication)
- n8n documentation on HTTP Request Node for understanding how HTTP calls are made within nodes