Mira Library List
AI-generatedOverview
The node "Mira Library List" retrieves a list of all libraries from the Mira App Server. It is designed to fetch library data via an HTTP GET request to the server's /api/libraries endpoint. This node is useful in scenarios where you need to integrate or synchronize library information from the Mira platform into your workflows, such as inventory management, reporting, or automation tasks involving library data.
Practical examples:
- Automatically fetching and processing the list of available libraries for display or further processing.
- Integrating Mira library data with other systems like CMS, ERP, or custom dashboards.
- Triggering downstream actions based on the current state or contents of the Mira libraries.
Properties
| Name | Meaning |
|---|---|
| Token Source | Choose where to get the access token from: either from stored credentials or from input data. |
| Server URL | The URL of the Mira App Server to connect to (required if token source is from input). |
| Access Token | The access token used for authentication, can be provided directly or via input data (required if token source is from input). |
- Token Source options:
- From Credentials: Use the token stored in the node’s configured API credentials.
- From Input Data: Use a token provided dynamically via input data or entered manually.
Output
The node outputs JSON data containing the list of libraries retrieved from the Mira App Server. The structure corresponds to the response from the /api/libraries endpoint, typically an array of library objects with their respective properties.
No binary data output is produced by this node.
Dependencies
- Requires access to a Mira App Server instance reachable at the specified Server URL.
- Requires an access token for authentication, either provided via credentials or input data.
- The node depends on an HTTP helper utility internally to perform the GET request.
Troubleshooting
Common issues:
- Invalid or missing access token: Ensure the token is correctly provided either through credentials or input.
- Incorrect Server URL: Verify that the URL points to a valid Mira App Server and is accessible.
- Network connectivity problems: Confirm network access to the Mira server.
Error messages:
- Authentication errors likely indicate invalid or expired tokens; refresh or provide a valid token.
- Connection timeouts or failures suggest server URL misconfiguration or network issues.
Resolving these usually involves verifying credentials, server URL, and network connectivity.
Links and References
- Mira App Server API documentation (for
/api/librariesendpoint) — consult the official Mira API docs for detailed response schema and usage. - n8n documentation on using credentials and HTTP requests for further customization.