Hands-on tested: These problems were encountered while building and testing Gmail → Google Drive workflows in Make.
A Gmail attachment automation can look correct but still fail because a filter uses the wrong field, a Router branch does not match, or Google Drive is mapped incorrectly.
Select a text field such as Gmail Subject first, then choose Text operators → Contains. If it remains unavailable, recreate the incomplete condition after selecting the source field.
Check the filter immediately after the Router. Our Invoice route used Subject → Contains → invoice; the Report route used Subject → Contains → report.
Test conditions separately: attachment/PDF condition, sender condition, then subject condition. Use one simple test email with one PDF while debugging.
Google Drive Upload a File needs both the attachment Filename and its binary Data. They are separate mappings.
Verify both the Router filter and each Drive destination. The route label alone does not select the Google Drive folder.
Save after every confirmed working stage. We encountered a missing Router structure and rebuilt the two branches before continuing.
Send one controlled test email and inspect which modules execute. If Gmail runs but Drive does not, inspect the intervening filter/Router. If Drive runs but the result is wrong, inspect folder, Filename, and Data.
Affiliate disclosure: Some links may be affiliate links. We may receive a commission at no additional cost to you.