Actions100
- Activity Actions
- Asset Actions
- Authentication Actions
- Collection Actions
- Extension Actions
- Field Actions
- File Actions
- Folder Actions
- Item Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
This node is designed to create a new activity entry, specifically a comment, on an item within a specified collection. It is useful in scenarios where users want to programmatically add comments or notes to items managed in a system that supports collections and activities (such as project management tools, content management systems, or databases with activity tracking). For example, you might use this node to automatically add status updates or feedback comments to tasks or projects as part of an automated workflow.
Properties
| Name | Meaning |
|---|---|
| Item | The primary key (ID) of the item to which the comment will be added. |
| Comment | The content of the comment to add. Supports Markdown formatting for rich text comments. |
| Collection Name | The name of the collection where the target item resides (e.g., "projects"). |
| JSON/RAW Parameters | Whether to provide body parameters as structured UI fields or as raw JSON input. |
| Body Parameters | When using JSON/RAW mode, the full set of body parameters provided as JSON or raw text. |
| Additional Fields | Optional extra fields; currently supports specifying metadata to return in the response. |
Output
The node outputs a JSON object representing the newly created activity (comment) entry. This typically includes details such as the comment content, associated item ID, collection name, timestamps, and any metadata requested. If binary data were involved, it would be summarized here, but this node focuses on JSON data output only.
Dependencies
- Requires access to the target system's API that manages collections and activities.
- Needs appropriate authentication credentials (e.g., an API key or token) configured in n8n to authorize requests.
- The node dynamically loads available collections via a method named
getCollectionsto populate the collection selection dropdown.
Troubleshooting
- Common Issues:
- Providing an invalid or non-existent item ID will likely result in an error from the API indicating the item was not found.
- Incorrect collection names or lack of permissions to access the collection can cause authorization or resource-not-found errors.
- Malformed JSON in the "Body Parameters" field when using JSON/RAW mode will cause parsing errors.
- Error Messages:
- "Item not found": Verify the item ID exists in the specified collection.
- "Unauthorized" or "Forbidden": Check API credentials and permissions.
- "Invalid JSON": Ensure the JSON syntax in the raw input is correct.
Links and References
- Refer to the API documentation of the system managing collections and activities for detailed information on required fields and metadata options.
- Markdown syntax guides for formatting comments effectively.