Can't use Variable acess/token on headers value on Call API column

Ask for Help
1

The headers of the CALL API column is just allowing me to use a custom value on the headers I am setting up. The problem is that I need to use different access/token when calling the API, depending on the Company I’m trying to reach. The field “Headers” can be variable, but the value is custom only. How can I solve it?

2

That function was removed to secure the header, and I’m not sure they would bring that back. Like you, I have a few services where my token is expiring after a certain amount of time, and I have had no solutions for it.

3

Thank you very much for your answer. It will defininetively limit a lot tha capacity of system construction. I really need it to build a multi-company platform, since the payments come from different payments solutions. Do you know any way to solve it?

4

I think you would have to resort to the JavaScript column to do something like that.

5

I’ll do some research and see if I can figure out how to do this. If I find some solution I let you know here too. Thank you very much for your help

1 Like
6

Thanks a lot!

7

JavaScript wouldn’t be secure, because it’s executed client side, which means the tokens would be on the client device. I think the only way to do it securely is via Make.

1 Like
8

Ah yes… Would be better if we don’t need a third-party service, but it is what it is.

9

it makes sense. How would you do this key management via Make?

10

Use a Webhook action to send relevant info from Glide to Make.com when needed, make a HTTP call over there, take the results and bring that back to Glide (either using the Glide API or Google Sheets/Airtable depending on your backend).

11

Keep all your tokens in a Make Data Store, then include a company identifier in the webhook from Glide, so that you can retrieve and send the correct token.

1 Like
12

Glide just added dynamic headers values hahah It keeps getting better

13

But they made it exclusively Business/Enterprise…

14

@ThinhDinh @Darren_Murphy
Is there a tutorial/example floating around anywhere for this Glide Webhook > Make > API Call > Glide using the Make Data Store?

I’m trying to deal with an expiring access token, similar to the below post

15

If they have an expiring access token, I would think they have a way to regenerate that token when needed.

I would just generate a token every time I need to call that API, then pass that to the actual call for authentication. Is that a valid approach?

16

That’s exactly what I do.

2 Likes
17

That should work. To do this are you storing the token in a column for the duration of the API Call and then clearing it as the final step in the action?

1 Like
18

Yes, I would store it in a user-specific column, then build out a template for the header if needed (say if you need something like Bearer XXX).

Then as the last action of your chain, clear the user-specific column.

2 Likes
19

I’m building something similar. Originally I planned on just having a backend connected to a DB to call an API and pass the data to the glide app’s connected Google sheet. But that’s not an option anymore, so I’m going to be using Glide’s call API.

Could I store a company_secret and the refresh_token inside of Glide using the secret variable or would I need to store it in made like was mentioned previously?

20

Couldn’t you just do this?