Mira Plugin List

Get all plugins from Mira App Server

Mira Plugin List

AI-generated

Overview

This node, named "Mira Plugin List," retrieves a list of all plugins available from the Mira App Server. It is useful when you want to programmatically fetch and work with the current set of plugins installed or available on your Mira server instance. For example, you might use this node to display plugin information in a dashboard, audit installed plugins, or trigger workflows based on the presence or absence of certain plugins.

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 (required if token source is from input).
Access Token The access token for authentication, provided directly or via input data (required if token source is from input).
  • Token Source options:
    • From Credentials: Use the token stored in Mira API credentials.
    • From Input Data: Use the token provided dynamically in the input data or entered directly.

Output

The node outputs JSON data with the following structure:

{
  "plugins": [ /* array of plugin objects retrieved from the Mira server */ ],
  "count": 0,              // Number of plugins returned
  "timestamp": "ISO8601",  // Timestamp of when the data was fetched
  "operation": "list"      // Indicates the operation performed
}
  • plugins: An array containing plugin details as returned by the Mira App Server's /api/plugins endpoint.
  • count: The total number of plugins in the array.
  • timestamp: The ISO string timestamp marking when the data was retrieved.
  • operation: A string indicating the operation type, here always "list".

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 from stored credentials or provided dynamically.
  • No additional external services are needed beyond the Mira App Server.
  • The node depends on internal helper modules for HTTP requests and token handling (bundled within the node).

Troubleshooting

  • Common issues:

    • Invalid or missing access token will cause authentication failures.
    • Incorrect Server URL or network issues may prevent connecting to the Mira App Server.
    • If the server does not respond with the expected plugin list, verify the server status and API availability.

  • Error messages:

    • Authentication errors typically indicate invalid tokens; ensure the token is correct and has necessary permissions.
    • Network errors suggest connectivity problems; check firewall, URL correctness, and server uptime.
    • Unexpected response formats may indicate server-side changes or incompatibility; verify API version compatibility.

Links and References

  • Mira App Server API documentation (for /api/plugins endpoint) — consult your Mira server API docs for detailed plugin data schema and authentication requirements.
  • n8n documentation on creating custom nodes and using credentials for API authentication.

Discussion