Home

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Explore Events
Clay Cup

Powered by Tightknit

Exploring Global Variables for API Token Workflow in Clay | Clay

Exploring Global Variables for API Token Workflow in Clay

·Nov 15, 2025 04:23 AM·

Has clay explored the idea of global variables? Use case i am trying to do

1.
I run an api token generation workflow on a scheduled run once every 30 days.
2.
I want to reference the returned token in the start of an http api request as a source but i dont think u can reference variables there

2 comments

· Sorted by Oldest

Clay Support
APP
·
·
Clay doesn't currently have global variables for storing tokens across workflows. However, you can reference dynamic variables in HTTP API requests using column references. [1]
In the HTTP API integration, you can reference data from other columns using /column notation in headers, query strings, and request bodies. [2] For authentication headers specifically, you'd typically use something like Authorization: Bearer /your_token_column in the headers section.
For your use case with a scheduled token generation, you'd need the token to be stored in a column that your HTTP API requests can reference. The challenge is getting that token from your scheduled workflow into the right place for your other requests to access it.
What's the current setup of your token generation workflow - are you storing the returned token in a specific column that you could potentially reference?
Clay Support
APP
·
·
If you still need help with referencing tokens in your workflows, I’m here to assist. Would you like to provide more details about how you’re currently storing or trying to use the token?