by Noel Maniraguha on December, 2025
This automation adds Clay table data to Google Sheets, making it easy for you to map tables to campaigns.
This automation has 3 components.
1. Adding a Clay table data to sheets. Copy the sheets file here.
2. Helping you map campaigns to Clay tables, to streamline list-building SOPs
3. Helping you review table hygiene (are tables names, in folders, with descriptions, etc?)
Insert the blueprint in make (new scenario)
Manual Changes
Clay Undocumented API
This will give you your Clay token. This token will be used in the modules following the Clay log-in, for example:
Click "inspect element" ➝ go to the "Network" tab ➝ click the "Fetch/XHR" button
Look for the request headers section
When you open this tab, there will be a section called "Cookie". This Cookie has 2 parts, the first part will remain static and it is what we will paste in the automation for ({INSERT_COOKIE_DETAILS}
The 2nd section is dynamic, and that's what we get from logging in (the token)... If you're unsure where the split occurs, simply run your Make module (Get Clay Token) and look at the output as it will contain a token; now you can take the first half from the header cookies, excluding your token
Workspace ID
Input this number within the "Get All Tables" module
Google Sheets Connection
If you make a copy of the Gsheets document and then make changes to the title or sheet name, you may get an error. To avoid this: ensure that the "Spreadsheet ID" and "Sheet Name" are spelled correctly.
IMPORTANT: If you get a "Runtime error" - check the spelling as described above!
Set a schedule
I recommend choosing a "daily" or "on-demand" occurrence for this automation... Depends on your use case.
