How can I modify an n8n Telegram workflow to save photos, videos, and documents to Google Drive?

Below is some advice that helped when others modified workflows like the Telegram-to-Google Drive template to handle other file types:

1. Review the Data from Telegram:
   Make sure the payload from Telegram includes the same properties for documents, photos, and videos. Sometimes images or video files are returned with slightly different field names or MIME types. Use a “Set” or “Function” node to inspect the incoming data.

2. Adjust the Condition Node Logic:
   When checking file types, ensure that your condition node correctly evaluates the field that holds the MIME type or file extension. Instead of a single value check, you may need to use an “OR” logic similar to:

   JSONCopied
   {
     "conditions": [
       {
         "field": "mime_type",
         "operation": "contains",
         "value": "application"
       },
       {
         "field": "mime_type",
         "operation": "contains",
         "value": "image"
       },
       {
         "field": "mime_type",
         "operation": "contains",
         "value": "video"
       }
     ],
     "logic": "OR"
   }

   If you’re matching on file extensions instead, verify that the match is case insensitive or that you’ve normalized the file names before the check.

3. Test Each Branch Independently:
   If possible, split your workflow and test each condition branch (document, photo, video) to ensure that each is correctly triggering the subsequent Google Drive node.

4. Examine the Error Details:
   The error you encountered might be due to a mismatched field or missing data when processing another file type. Click into the error on the execution details to see what field is failing to map properly. It could be related to using an incorrect expression in the node (for instance, passing an undefined ID to the Google Drive node).

5. Debug Using Intermediate Nodes:
   Insert a “NoOp” or “Set” node between your condition node and your Google Drive node to log out the payload. This can help ensure that the file ID, MIME type, or any other necessary information is correctly passed along.

6. Review the Google Drive Node Requirements:
   Ensure that the data you’re sending (for example, when selecting the file by ID using an expression like {{ $json.id }}) is valid. Any alterations upstream might affect these values when handling a wider range of file types.

By inspecting the payload and carefully adjusting the conditions to cover all expected file types, you can usually resolve the error. If you continue to face issues, you can enable debug logging in n8n or share the specific error message in the community forum for more targeted assistance.

Hope this helps you get your workflow running smoothly for documents, photos, and videos!