I've a customer workflow that looks like this:

This back-and-forth Google Sheets workflow is partially supported, but requires some workarounds since Clay doesn't have native periodic file monitoring. What works today: • Clay can read from Google Sheets using the "Lookup row" action [clay.com • Clay can write enriched data back to Google Sheets using "Add row" or "Lookup, add, or update row" actions • Google Apps Script can push data to Clay via webhooks Cleanest implementation approach: 1. Initial data flow: Use Google Apps Script to send standardized data to Clay via webhook (instead of Clay reading files) 2. Enrichment & export: Clay enriches data and writes back to Google Sheets automatically 3. Manual column sync: After your sales team adds the manual column, use another Google Apps Script trigger to detect changes and push updated rows back to Clay via webhook 4. Final processing: Clay processes the updated data and sends to Marketo This webhook-based approach is more reliable than trying to monitor Drive folders. The Google Apps Script can handle the file detection and change monitoring, while Clay handles the enrichment and downstream processing. Before diving into the technical setup, I'd recommend trying our built-in AI tool Sculptor (top-right corner) to help design this workflow - it's free and great for complex automations like this. Let me know if Sculptor helps or if you need more specific implementation details!