Actions50
- Status Actions
- Task Actions
- Calendar Actions
- ClientProfile Actions
- Comment Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
This node interacts with the Scoro API to update an existing comment associated with a specific module and object within that module. It is useful in scenarios where you need to programmatically modify comments on various entities such as tasks, projects, or other modules supported by Scoro.
For example, if you have a task management workflow and want to update the content of a comment attached to a particular task, this node allows you to specify the module (e.g., "tasks"), the object ID (the specific task), and the comment ID to update the comment text accordingly.
Properties
| Name | Meaning |
|---|---|
| Module | The module to which the comment belongs, e.g., "tasks", "projects". |
| Object ID | The unique identifier of the object within the specified module to which the comment is attached. |
| Comment ID | The unique identifier of the comment to be updated. |
| User ID | The ID of the comment owner. Required when using API key authentication. |
| Comment | The new content/text of the comment to replace the existing one. |
Output
The node outputs JSON data representing the updated comment object as returned by the Scoro API. This typically includes fields such as the comment ID, updated text, timestamps, user information, and any metadata related to the comment.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Scoro API.
- Needs credentials including:
- Base URL of the Scoro instance.
- Company account ID.
- An API key for authentication.
- These credentials must be configured in n8n prior to using the node.
Troubleshooting
Common Issues:
- Providing incorrect or missing
Module,Object ID, orComment IDwill cause the update to fail. - Missing
User IDwhen using API key authentication can result in authorization errors. - Network connectivity issues or invalid API keys will prevent successful communication with the Scoro API.
- Providing incorrect or missing
Error Messages:
"Operation 'update' for resource 'comment' is not supported."β This indicates a misconfiguration or unsupported operation; verify the selected resource and operation.- Authentication errors usually indicate invalid or missing credentials; ensure the API key and company account ID are correct.
- Validation errors from the API may occur if required fields are missing or malformed; double-check input property values.
Links and References
- Scoro API Documentation β Official API docs for detailed information on comment updates and other operations.
- n8n Documentation on Creating Custom Nodes for understanding node development concepts.