Skip to content

Monday.com - Add Update

↩ Part of the Monday.com integration.

This module posts an update — what Monday calls the comments in an item’s activity feed — with the create_update GraphQL mutation:

mutation($item_id: ID!, $body: String!) {
create_update(item_id: $item_id, body: $body) { id }
}

Updates are the natural place to leave an automated trace: what the workflow did, when, and with what result, without touching any column.

FieldTypeRequiredDescription
credentials_idcredentialsYesMonday credential
item_idtextYesNumeric item id
bodytextareaYesUpdate / comment text

This module requires a Monday credential.

FieldDescription
tokenPersonal API token (Avatar → Developers → My access tokens)
timeoutOptional. Request timeout in milliseconds (default 20000)
{
"nextModule": null,
"data": { "id": "445566778" },
"_meta": {
"moduleVersion": "1.0.0",
"success": true,
"id": "445566778",
"totalMs": 214
}
}

Note that _meta.id here is the id of the new update, not the id of the item.

{
"credentials_id": 8,
"item_id": "{{data.id}}",
"body": "Invoice {{data.invoice}} issued for {{data.amount}} EUR on {{data.date}}."
}
{
"credentials_id": 8,
"item_id": "987654321",
"body": "The sync failed: {{data.error.message}}. The workflow will retry automatically."
}
  • The update is posted by the owner of the token, so it shows up under that user’s name in the item feed. Consider a dedicated integration user if you do not want it attributed to a person.
  • body accepts basic HTML, which is how Monday renders updates. Plain text works fine too.
  • Both item_id and body are required. If either resolves to an empty value the node fails before calling Monday.
  • Notifications and mentions follow Monday’s own rules: subscribers of the item get notified about the new update.