Portainer icon

Portainer

Interact with Portainer via API

Actions190

Edge Stacks → Edge Stack Status Update

AI-generated

Overview

The "Edge Stack Status Update" operation in the Edge Stacks resource allows updating the status of a specific Edge Stack by sending a status payload. This node is useful for scenarios where you need to programmatically report or modify the current state of an Edge Stack within Portainer, such as signaling deployment progress, health checks, or other runtime status updates.

Practical examples include:

  • Automatically updating the status of an Edge Stack after a deployment script runs.
  • Reporting health or error states from monitoring tools back to Portainer.
  • Integrating with CI/CD pipelines to reflect the real-time status of edge deployments.

Properties

Name Meaning
Id The unique identifier (number) of the Edge Stack whose status you want to update.
Body The status payload (string) containing the details of the Edge Stack status update. This should be a JSON string representing the status information to send.

Output

The node outputs the response from the Portainer API after attempting to update the Edge Stack status. The output is structured as JSON data reflecting the result of the update operation, which typically includes confirmation of the update or any error messages returned by the API.

This node does not output binary data.

Dependencies

  • Requires an active connection to a Portainer instance via its API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL of the Portainer API must be provided in the credentials configuration.

Troubleshooting

  • Invalid Id: If the provided Edge Stack Id does not exist or is incorrect, the API will return an error. Verify the Id before running the node.
  • Malformed Body: The Body property must be a valid JSON string. Invalid JSON will cause the request to fail. Use JSON validation tools to ensure correctness.
  • Authentication Errors: Missing or invalid API credentials will prevent the node from connecting to Portainer. Ensure the API key/token and URL are correctly set.
  • Network Issues: Connectivity problems between n8n and the Portainer server can cause timeouts or failures. Check network access and firewall settings.
  • API Version Mismatch: Using incompatible Portainer API versions may lead to unexpected errors. Confirm that the API version matches what the node expects.

Links and References

Discussion