Actions20
Overview
The Plutio - Comment: Get operation node retrieves comments from the Plutio platform based on a specified entity. This is useful for automating workflows that need to fetch and process comments related to tasks, conversations, or files within Plutio. For example, you might use this node to:
- Aggregate all comments on a specific task for reporting.
- Monitor new comments on a file for notifications.
- Retrieve conversation comments for archiving or analysis.
Properties
| Name | Type | Meaning |
|---|---|---|
| Entity ID | String | The unique identifier of the entity (task, conversation, or file) whose comments you want to retrieve. |
| Entity Type | Options | The type of entity associated with the comment. Options are: File, Conversation, Task. |
Output
The output will be an array of JSON objects, each representing a comment retrieved from Plutio. Each object typically contains fields such as:
entityId: The ID of the related entity.entityType: The type of entity (file, conversation, or task).- Other comment details (e.g., comment body, author, timestamps).
Note: The exact structure of each comment object depends on the Plutio API response, but it will always include at least the entity identification and comment content.
Dependencies
- External Service: Requires access to the Plutio API.
- API Credentials: You must configure valid Plutio API credentials in n8n under the name
plutioApi.
Troubleshooting
- Missing or Invalid Entity ID: If the provided Entity ID does not exist or is incorrect, no comments will be returned or an error may occur.
- Incorrect Entity Type: Ensure the Entity Type matches the actual type of the entity; otherwise, the query may fail or return no results.
- Authentication Errors: If your API credentials are missing or invalid, you will receive authentication errors. Double-check your n8n credential setup.
- Common Error Messages:
"Entity not found": Check that both Entity ID and Entity Type are correct."Invalid credentials": Update your Plutio API credentials in n8n.