I've a customer workflow that looks like this:

Did that answer your question?

For 50+ separate tables: Your Google Apps Script can dynamically create new webhook tables by calling Clay's API. Each event gets its own webhook URL and table. [clay.com For Google Sheets column matching: Yes, Clay can write enriched data back to specific rows using the "Lookup, add, or update row" action based on matching criteria like email or ID. [documentation For Marketo automation: You can pre-configure Marketo actions in each table template, then use conditional formulas to only run when the program endpoint is populated. This allows zero-touch activation once endpoints are set. [documentation The main challenge is the "zero human intervention" requirement - someone still needs to set Marketo program endpoints for each event table. Consider using Sculptor to help design this multi-table automation workflow.

1. We're talking about 50+ events/ year, so its easily 50+ files that needs to be processed into clay. But the caveat is, customer doesn't want to process all those into one clay table, they want leads from each event into separate clay table. So how can Webhook calls handle this use case?
2. Clay has the enriched data in columns, so can those be passed to google sheet as column for matching rows?
3. They may not know the marketo program end point until they create it, so I assume for each table at once leads are ready to be activated, customer has to manually set marketo program endpoint for push? They are looking for a solution with 0 human intervention at all stages

If you still need help with setting up your Google Sheets workflow or have questions about using Sculptor, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific challenges you’re facing?

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!