by Noel Maniraguha on October, 2024
This automation adds a client folder to Clay and links the folder ID to your PJM tool for future automations.
This automation has 2 components.
1. Adding a client folder to Clay
2. Adding your Clay folder ID into your PJM tool (for future automations)
I recommend combining this automation with Smartlead client onboarding SOPs.
Pre-requisite: You must have a way to initiate the automation while providing the required fields.
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
Client Database
- Download the Smartlead client database and simply add a field called "Clay folder ID"
- This ID will be useful when you create other Clay automations, that duplicate and move tables.
Set a schedule
I recommend choosing a "daily" occurrence for this automation
