Mira Plugin Info
AI-generatedOverview
The "Mira Plugin Info" node retrieves detailed information about a specific plugin from the Mira App Server. It is useful when you need to programmatically access metadata or status details of plugins managed by the Mira platform, such as for monitoring, auditing, or integration purposes.
Typical use cases include:
- Fetching plugin details before performing further automated operations.
- Displaying plugin information in dashboards or reports.
- Validating plugin existence and properties during deployment workflows.
Properties
| Name | Meaning |
|---|---|
| Token Source | Choose where to get the access token from: either from stored credentials or directly from input data. Options: "From Credentials", "From Input Data". |
| Server URL | The base URL of the Mira App Server to which the request will be sent. Required if token source is "From Input Data". |
| Access Token | The access token used for authentication with the Mira App Server. Can be provided directly or via expressions. Required if token source is "From Input Data". |
| Plugin ID | The unique identifier of the plugin whose information you want to retrieve. This is mandatory. |
Output
The node outputs JSON data containing the following fields:
pluginId: The plugin ID requested.pluginInfo: The detailed information object returned from the Mira App Server about the specified plugin.timestamp: The ISO timestamp when the data was retrieved.operation: A string indicating the operation performed, here always"getInfo".
This output allows downstream nodes to consume plugin metadata for further processing or decision-making.
Dependencies
- Requires access to a Mira App Server instance reachable at the specified Server URL.
- Requires an access token for authenticating API requests to the Mira App Server. This token can be supplied either via n8n credentials or directly through input data.
- Uses HTTP GET requests to the
/api/plugins/{pluginId}endpoint on the Mira App Server.
Troubleshooting
- Missing Plugin ID: The node throws an error if the Plugin ID property is empty. Ensure this field is filled with a valid plugin identifier.
- Authentication Errors: If the access token is invalid or missing, the API call will fail. Verify that the token is correct and has sufficient permissions.
- Server Connectivity Issues: If the Server URL is incorrect or the Mira App Server is unreachable, the node will not be able to fetch plugin info. Confirm network connectivity and server availability.
- Invalid Token Source Configuration: Make sure the Token Source property matches how you provide the token (credentials vs input). Mismatches can cause authentication failures.
Links and References
- Mira App Server API documentation (for
/api/plugins/{pluginId}endpoint) – consult your Mira platform docs for detailed API specs. - n8n documentation on using credentials and HTTP request nodes for custom integrations.