I see Harish - Since we don't support this currently, I went ahead and flag this to our team so they can better evaluate things and see if/where this might fit into the roadmap as a future improvement.
Since you can't do it like this, here's how to handle the authentication and job posts:
1. Create two separate HTTP requests:
First request to get the access token
Second request for the job posts using that token
2. For implementation:
Run the token request row first
Copy the received token
Paste it into your HTTP API column for the job posts request
Run those rows
3. For ongoing management:
After 24h, use table filters to hide completed rows
Only show/run rows that need processing
This prevents re-running old rows when the token refreshes.
Note: Since the token gets saved as a new version, this workflow helps avoid stale data issues when using the "run rows with errors" option.
.png&w=3840&q=75){kind=logo}
