by Noel Maniraguha on December, 2025
This automation makes it easy for you to duplicate the Master campaign table. Ensuring that you can create new campaigns quickly.
This automation has 2 components.
1. Duplicating a Clay table via the API.
2. Renaming that table and moving it to a client folder.
I recommend combining this automation with: Duplicate Clay master campaign table
Disclaimer: This automation is a small component in a bigger project (campaign creation SOPs)... If you want to create campaigns quickly while streamlining your operations, then this will be extremely valuable. This is not a copy/paste solution.
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
Implement into Campaign Creation SOPs (advanced)
The webhook doesn't come from any particular location, so you'll have to determine how the information is gathered... You'll need these fields: original campaign table ID, client folder ID, and the new table name. These fields will be added in the URL/request content of the HTTP modules:
I typically store this information in a Clickup task. And the trigger for the webhook is a status change. Depending on your SOPs, you may implement this differently.
Set a schedule
I recommend choosing an "immediate" occurrence for this automation.
