Mira Library Stop

Stop a library service in Mira App Server

Mira Library Stop

AI-generated

Overview

The "Mira Library Stop" node is designed to stop a specific library service running on the Mira App Server. It sends a request to the server to halt the operation of the identified library. This node is useful in automation workflows where you need to programmatically control the lifecycle of services managed by Mira, such as stopping a library before maintenance or redeployment.

Practical examples:

  • Automatically stopping a library service at the end of a business day.
  • Integrating with other workflow steps that require the library to be stopped before proceeding.
  • Managing resource usage by stopping unused libraries dynamically.

Properties

Name Meaning
Library ID The ID of the library to stop. This is a required string input specifying which library service should be halted.

Output

The node outputs a JSON object for each input item containing the following fields:

  • stopped: A boolean value (true) indicating the library stop request was initiated.
  • libraryId: The ID of the library that was requested to stop.
  • response: The raw response from the Mira App Server API after attempting to stop the library. This typically contains status or confirmation details.
  • timestamp: An ISO 8601 formatted timestamp marking when the stop operation was executed.
  • operation: A string literal "stop" indicating the type of operation performed.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests against the Mira App Server.
  • The node uses an HTTP POST request to the endpoint /api/libraries/{libraryId}/stop on the Mira App Server.
  • Proper network access and permissions to communicate with the Mira App Server are necessary.

Troubleshooting

  • Missing Library ID: If the "Library ID" property is empty or not provided, the node will throw an error stating that the Library ID is required. Ensure this field is correctly set.
  • Authentication errors: If the API key or authentication token is invalid or missing, the HTTP request will fail. Verify that the credential is properly configured and has sufficient permissions.
  • Network issues: Failure to reach the Mira App Server due to network problems or incorrect URL configuration will cause the node to error out. Check connectivity and server availability.
  • API errors: If the specified library ID does not exist or cannot be stopped (e.g., already stopped), the server may return an error response. Review the response output for details and adjust inputs accordingly.

Links and References

  • Mira App Server API documentation (for the /api/libraries/{libraryId}/stop endpoint) — consult your Mira App Server API docs for detailed information on the stop operation.
  • n8n HTTP Request node documentation — for understanding how authenticated HTTP requests work within n8n workflows.

Discussion