Actions20
Overview
The Plutio - Comment: Update operation node allows you to update an existing comment in your Plutio workspace. This is useful for workflows where you need to programmatically modify the content of a comment, such as correcting information, updating status messages, or appending additional details based on automation triggers.
Practical examples:
- Automatically update a comment when a related task's status changes.
- Edit comments to include new information from another system.
- Correct typos or outdated information in previously posted comments.
Properties
| Name | Type | Meaning |
|---|---|---|
| Comment ID | String | The unique identifier of the comment you want to update. Required to locate the comment. |
| Body | String | The new content (HTML) for the comment body. Required; this replaces the old comment. |
Output
The output will be a JSON object representing the updated comment. While the exact structure depends on the Plutio API response, it typically includes fields such as:
{
"_id": "string",
"bodyHTML": "string",
"entityId": "string",
"entityType": "string",
"createdAt": "string",
"updatedAt": "string",
// ...other comment fields
}
_id: The comment's unique identifier.bodyHTML: The updated HTML content of the comment.entityIdandentityType: Reference to the entity (e.g., task, project) the comment belongs to.createdAt,updatedAt: Timestamps for creation and last update.
Dependencies
- External Service: Requires access to the Plutio API.
- API Credentials: You must configure n8n with valid Plutio API credentials (
plutioApi). - n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid Comment ID: If the provided Comment ID does not exist, the node will return an error indicating that the comment could not be found.
- Missing Required Fields: Both Comment ID and Body are required. Omitting either will result in an error.
- Authentication Errors: Invalid or missing API credentials will cause authentication failures.
- API Rate Limits: Excessive requests may trigger rate limiting by Plutio.
Error messages and resolutions:
"Comment not found": Ensure the Comment ID is correct and exists in your Plutio workspace."Missing required parameter: _id or bodyHTML": Double-check that both fields are filled in the node configuration."Authentication failed": Verify your Plutio API credentials in n8n.
