Why does my Google Drive Trigger only return the latest file and not trigger on folder changes?

Below are some points to consider for each of your issues:

---

1. Scheduled Trigger Not Running Every Minute

• Verify the Cron Expression/Interval:
  If you’re using the Schedule Trigger node with a custom cron expression, ensure that your expression is valid for running every minute. For example, a valid expression for every minute is:

  * * * * *
  

  Note that n8n may require you to remove any seconds column. Double-check the syntax against the n8n cron examples documentation or on crontab guru.

• Timezone Considerations:
  If the trigger isn’t firing at the expected local time, it might be a timezone issue. For self-hosted instances, set the global timezone via the GENERIC_TIMEZONE environment variable, or adjust the timezone at the workflow level via the workflow’s settings.

• Environment and Proxy Settings:
  Although websocket proxying is more often a concern with trigger nodes that listen to events (like Google Sheets Trigger), it may still be worth checking your network and reverse proxy configuration (if any) to ensure no interference with scheduled executions.

---

2. Testing Returns Only One Item Instead of Six

• Manual Execution vs. Activation Behavior:
  Keep in mind that for many trigger nodes—including the Google Drive Trigger node—manual execution (via the Test button) will typically return only the latest event that matches the search criteria. The documentation notes that upon a manual run, only the most recent event is returned and, in some cases, an error will be thrown if no matching event is found.
  When the workflow is activated, however, the node regularly checks for events and will trigger the workflow for each new event (i.e. each file change) that occurs.

• Real-World Testing:
  To see behavior that aligns with your expectations (i.e. processing all six items), it may be necessary to let the workflow run in production mode (with activation enabled) and then create or update files in the monitored folder. This will allow the trigger to capture the events as they occur over time rather than relying solely on the manual test output.

• Double-Check Configuration:
  If you intended to load all existing six files at once, note that the node is designed to return the single most recent event in manual mode. For processes involving multiple files or to obtain a full list, consider using a combination of the Google Drive node with a search operation and then processing the list (for example, by sorting and optionally limiting results as detailed in the documentation).

---

By verifying your cron expression and timezone settings for the schedule trigger and understanding the difference between manual testing and activated workflows for event retrieval, you should be able to resolve these issues. Let me know if you need further assistance or clarification on any of these points!