Plutio icon

Plutio

Consume Plutio API
Join our community

Actions20

Overview

The Plutio - Comment: Create operation node allows you to create a new comment in Plutio, which can be attached to a task, conversation, or file. This is useful for automating the process of adding feedback, notes, or discussions to various entities within your Plutio workspace. For example, you could automatically add a comment to a task when a support ticket is updated, or log a note on a file after it has been processed.

Practical Examples

  • Automatically post a comment to a task when a related event occurs in another system.
  • Add a discussion entry to a conversation as part of a workflow.
  • Attach a note to a file upload for documentation or review purposes.

Properties

Name Type Meaning
Entity ID String The unique identifier of the entity (task, conversation, or file) to which the comment will be attached.
Entity Type Options The type of entity the comment relates to. Possible values: File, Conversation, Task.
Body String The content of the comment, provided in HTML format. This field is required.

Output

The output will be a JSON object representing the newly created comment as returned by the Plutio API. The structure typically includes fields such as:

{
  "_id": "string",
  "entityId": "string",
  "entityType": "string",
  "bodyHTML": "string",
  "createdAt": "string",
  "updatedAt": "string",
  // ...other fields depending on Plutio's API response
}
  • _id: Unique identifier of the comment.
  • entityId: The ID of the associated entity.
  • entityType: The type of entity (file, conversation, or task).
  • bodyHTML: The HTML content of the comment.
  • createdAt, updatedAt: Timestamps for creation and last update.

Dependencies

  • External Service: Requires access to the Plutio API.
  • API Key: You must configure valid Plutio API credentials (plutioApi) in n8n.
  • n8n Configuration: Ensure the Plutio credential is set up in your n8n instance.

Troubleshooting

Common Issues:

  • Missing or Invalid Entity ID: If the Entity ID does not correspond to an existing task, conversation, or file, the API will likely return an error.
  • Incorrect Entity Type: Ensure that the Entity Type matches the actual type of the entity referenced by Entity ID.
  • Empty Body: The Body property is required; leaving it empty will result in an error.
  • Authentication Errors: If the Plutio API credentials are missing or invalid, authentication errors will occur.

Error Messages:

  • "Invalid entityId": Check that the provided Entity ID exists and is correct.
  • "entityType is required": Make sure you have selected the correct entity type.
  • "bodyHTML is required": Provide non-empty comment content.
  • "401 Unauthorized": Verify your Plutio API credentials in n8n.

Links and References

Discussion