Worktables Webhook

Triggers workflows when an event occurs in Monday.com

Overview

This node implements a webhook trigger for Monday.com events. It listens for incoming HTTP POST requests from Monday.com when specific events occur, allowing workflows to be triggered automatically based on those events. This is useful for automating processes that depend on changes or actions within Monday.com, such as updating records, sending notifications, or syncing data with other systems.

For example, you could use this node to start a workflow whenever a new item is created in a Monday.com board or when the status of a task changes.

Properties

Name	Meaning
Webhook Path	Define a custom path segment for the webhook URL. The default value is "monday-webhook". This path is appended to the base webhook URL to form the full endpoint that Monday.com will call.

Output

The node outputs JSON data representing the payload received from Monday.com via the webhook. Specifically:

The json output field contains an array with one element: the parsed JSON body of the incoming webhook request.
If the incoming request includes a challenge property (used by Monday.com to verify the webhook), the node responds with the challenge value and does not emit workflow data.

No binary data output is produced by this node.

Dependencies

Requires an HTTP POST webhook endpoint accessible by Monday.com.
No external API keys or credentials are required for this node itself.
The user must configure Monday.com to send webhook events to the generated webhook URL, which includes the customizable webhook path.

Troubleshooting

Webhook Not Triggering: Ensure that Monday.com is correctly configured to send webhooks to the exact URL including the custom webhook path. Verify that the n8n instance is publicly accessible.
Challenge Verification Fails: Monday.com sends a challenge parameter during webhook setup. The node handles this by responding with the challenge value. If verification fails, check that the node is deployed and reachable.
Unexpected Payloads: The node logs the received webhook payload. If the workflow does not behave as expected, inspect these logs to confirm the structure of incoming data matches expectations.