Actions26
- Board Actions
- Docs Actions
- Folder Actions
- Group Actions
- Item Actions
- Updates Actions
- Users Actions
Overview
This node operation allows you to create a reply to an existing update on Monday.com. It is useful when you want to programmatically respond to updates or comments within Monday.com items, enabling automated conversations or notifications in workflows.
A practical example would be automatically replying to a status update on a task with additional information or confirmation, or responding to user comments with follow-up instructions.
Properties
| Name | Meaning |
|---|---|
| Parse User Mentions | Whether to automatically parse @userid mentions in the reply text and convert them into user tags. |
| Update ID | The unique identifier of the update to which this reply will be posted. |
| Reply Text | The content of the reply message. Supports @userid format to mention users (e.g., "Hello @12345678"). |
Output
The output JSON contains the created reply update object as returned by the Monday.com API client. This typically includes details such as the reply's ID, text content, author, timestamps, and any parsed user mentions.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential for Monday.com.
- Uses Monday.com API version defaulting to "2023-10" unless overridden.
- Utilizes an internal utility to parse user mentions asynchronously by resolving user IDs via the Monday.com API.
Troubleshooting
Common issues:
- Invalid or missing Update ID will cause failure to post a reply.
- Incorrect formatting of user mentions (
@userid) may result in mentions not being converted properly if parsing is enabled. - Network or authentication errors with the Monday.com API can prevent reply creation.
Error messages:
- Errors from the Monday.com API are propagated; typical messages include "User with ID not found" if mention parsing fails.
- If the node is set to continue on fail, errors will be included in the output JSON under an
errorfield for the respective item.
Resolutions:
- Ensure the Update ID corresponds to an existing update.
- Verify that the API token credential is valid and has sufficient permissions.
- Format mentions correctly and enable parsing if you want automatic conversion.