Monday.com icon

Monday.com

Interact with Monday.com API
Join our community

Actions26

Overview

This node integrates with the Monday.com API to manage documents ("Docs") within a Monday.com workspace. Specifically, the "Delete" operation for the "Docs" resource allows users to delete a document by its ID. This is useful in scenarios where you want to automate cleanup of outdated or unnecessary documents in your Monday.com environment.

Practical examples include:

  • Automatically deleting project documentation when a project is archived.
  • Removing temporary or test documents created during workflow automation.
  • Cleaning up documents based on certain triggers or conditions in your workflow.

Properties

Name Meaning
Doc ID The unique identifier of the document to delete. This is required to specify which document should be removed.

Output

The output JSON contains an object with two fields:

  • success: A boolean indicating whether the deletion was successful (true if deleted).
  • docId: The ID of the document that was requested to be deleted.

Example output JSON:

{
  "success": true,
  "docId": "123456789"
}

This confirms the document identified by the given ID has been deleted successfully.

Dependencies

  • Requires an API authentication token credential for Monday.com to authorize requests.
  • Uses the Monday.com API client internally to perform the deletion.
  • The node expects the Monday.com API version (defaulting to "2023-10") and supports auto-upgrade of the API client.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Doc ID will likely cause the deletion to fail.
    • Missing or incorrect API credentials will prevent the node from authenticating with Monday.com.
    • Network connectivity issues can cause request failures.

  • Error messages:

    • If the document does not exist or cannot be found, the node may throw an error indicating failure to delete.
    • Authentication errors will occur if the API token is invalid or expired.

  • Resolutions:

    • Verify the Doc ID is correct and corresponds to an existing document.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Check network connectivity and retry if transient errors occur.
    • Use the node's "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion