Mira Plugin Start

Start a plugin in Mira App Server

Mira Plugin Start

AI-generated

Overview

The "Mira Plugin Start" node is designed to start a specific plugin on a Mira App Server. It sends a POST request to the server's API endpoint responsible for initiating the plugin identified by its ID. This node is useful in automation workflows where you need to programmatically control the lifecycle of plugins within the Mira environment, such as triggering a plugin to begin processing based on external events or conditions.

Practical examples:

  • Automatically starting a data processing plugin when new data arrives.
  • Triggering a monitoring plugin at scheduled intervals.
  • Integrating Mira plugins into larger automation pipelines that require dynamic control over plugin execution.

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 Data").
Access Token The access token used for authentication, can be provided directly or via input data.
Plugin ID The unique identifier of the plugin to start (required).
  • Token Source options:
    • From Credentials: Use the token stored in the node's configured credentials.
    • From Input Data: Use a token provided dynamically via input data or entered manually.

Output

The node outputs JSON data with the following structure:

{
  "started": true,
  "pluginId": "<the plugin ID provided>",
  "response": "<raw response from the Mira server>",
  "timestamp": "<ISO timestamp of when the operation was performed>",
  "operation": "start"
}
  • started: A boolean indicating the plugin start request was sent.
  • pluginId: The ID of the plugin that was requested to start.
  • response: The raw response returned by the Mira App Server after the start request.
  • timestamp: The exact time when the start operation was executed.
  • operation: The string "start" indicating the type of operation performed.

The node does not output binary data.

Dependencies

  • Requires access to a Mira App Server with an API endpoint to start plugins.
  • Needs an access token for authentication, which can be supplied either via credentials configured in n8n or dynamically through input data.
  • The node depends on HTTP communication with the Mira server; thus, network connectivity and correct server URL configuration are essential.

Troubleshooting

  • Missing Plugin ID: If the "Plugin ID" property is empty, the node will throw an error stating that the Plugin ID is required. Ensure this field is filled correctly.
  • Authentication Errors: If the access token is invalid or missing, the Mira server may reject the request. Verify that the token is correct and properly supplied according to the selected token source.
  • Server Connectivity Issues: If the server URL is incorrect or the server is unreachable, the node will fail to send the request. Confirm the server URL and network accessibility.
  • Unexpected Server Responses: If the Mira server returns an error or unexpected response, check the server logs and ensure the plugin ID exists and is valid.

Links and References

  • Mira App Server API documentation (for plugin management endpoints) — consult your Mira server's official API docs.
  • n8n documentation on creating and using credentials and HTTP request nodes for further customization.

Discussion