Actions29
- Board Actions
- Item Actions
- Update Actions
- Team Actions
- User Actions
- Query Actions
Overview
This node integrates with Monday.com (referred to as "Worktables" in the code) and allows users to interact with various Monday.com resources such as boards, items, updates, teams, and users via GraphQL API calls. Specifically for the Update resource with the Upload operation, the node enables uploading a file to an update on Monday.com.
Common scenarios where this node is beneficial include:
- Automating project management workflows by attaching files directly to updates on Monday.com items.
- Enhancing collaboration by programmatically adding relevant documents or images to updates.
- Integrating Monday.com with other systems to synchronize files or reports as part of task updates.
Practical example:
- A user wants to upload a PDF report automatically to a specific update on a Monday.com item whenever a new report is generated in another system.
Properties
| Name | Meaning |
|---|---|
| Board Name or ID | Select the Monday.com board where the item exists. Choose from the list or specify an ID via expression. Required. |
| Item Name or ID | Select the item within the chosen board to which the update belongs. Choose from the list or specify an ID via expression. Required. |
Note: The provided properties JSON only includes these two inputs relevant to the Update Upload operation, but the full node supports many more depending on resource and operation.
Output
The node outputs a JSON object representing the response from the Monday.com API after attempting the file upload to the update. This typically includes confirmation data such as the uploaded file's ID or related metadata.
If binary data is involved (e.g., the file to upload), it is expected to be provided as input binary property (not explicitly shown in the provided properties but implied by typical upload operations). The node processes this binary data to send it as a file attachment in the mutation request.
Dependencies
- Requires an API key credential for Monday.com (referred generically as "an API key credential").
- Uses Monday.com's GraphQL API endpoint:
https://api.monday.com/v2. - The node uses HTTP POST requests with appropriate authorization headers.
- For file uploads, the node expects binary data input in a specified binary property.
Troubleshooting
Common Issues
- Missing API Key: The node throws an error if the API key credential is not found or invalid.
- Invalid Board or Item ID: If the board or item ID is missing or incorrect, the API call will fail.
- No Binary Data Found: When uploading a file, if no valid binary data is found in the input, the node will throw an error indicating the binary property is undefined.
- Unsupported Operation: If an unsupported operation is selected, the node throws an error specifying the unsupported operation.
Error Messages and Resolutions
"API Key not found": Ensure that the Monday.com API key credential is configured correctly in n8n."Board ID is required."or"Item ID is required.": Verify that the correct board and item IDs are provided."Binary property \"<propertyName>\" is undefined.": Confirm that the input contains binary data under the specified binary property name."Unsupported operation: uploadFile"(or similar): Check that the operation is supported and spelled correctly.
Links and References
Summary of the execute() logic for Resource=Update, Operation=Upload
- Retrieves the API key credential.
- Reads parameters: boardId and itemId (required).
- Extracts binary file data from input using the specified binary property.
- Constructs a GraphQL mutation to upload the file to the update associated with the item.
- Sends the request to Monday.com API.
- Returns the API response as JSON output.