Actions26
- Board Actions
- Docs Actions
- Folder Actions
- Group Actions
- Item Actions
- Updates Actions
- Users Actions
Overview
This node interacts with the Monday.com API to manage documents ("Docs") within a Monday.com workspace. Specifically, the "Get" operation retrieves detailed information about a single document by its ID. This is useful when you want to fetch and use the content or metadata of a specific doc in your workflow, for example, to display it, analyze it, or pass it on to other systems.
Practical examples:
- Automatically retrieving a project specification document from Monday.com to include in a report.
- Fetching a knowledge base article stored as a doc to send via email or chat.
- Using the doc content to trigger further automation based on its data.
Properties
| Name | Meaning |
|---|---|
| Doc ID | The unique identifier of the doc to retrieve. This is required to specify which document to get. |
Output
The output is a JSON object representing the retrieved document. It typically includes all available details about the doc such as its ID, name, kind (e.g., private or public), workspace association, folder if any, and potentially its content blocks if applicable.
No binary data output is indicated for this operation.
Example output structure (simplified):
{
"id": "123456789",
"name": "Project Plan",
"kind": "private",
"workspaceId": "987654321",
"folderId": "1122334455",
"contentBlocks": [
{
"type": "text",
"content": "Document introduction..."
},
...
]
}
Dependencies
- Requires an API authentication token credential for Monday.com.
- The node uses the Monday.com API version specified in credentials or defaults to "2023-10".
- No additional external services are needed beyond Monday.com's API.
Troubleshooting
Common issues:
- Invalid or missing Doc ID will cause the request to fail.
- Insufficient permissions or invalid API token may result in authorization errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- If the doc does not exist or the ID is wrong, the node may throw an error indicating the doc was not found.
- Authentication errors will mention invalid credentials or access denied.
Resolutions:
- Verify the Doc ID is correct and exists in Monday.com.
- Ensure the API token credential has sufficient permissions to read docs.
- Check network connection and retry.