Implementing auto-refresh for short-lived tokens in custom app for API

How To
1

I’m developing a custom app in Make.com for the API, which uses access tokens with a very short lifespan (5-10 minutes).

But I’m struggling to find an efficient way to handle these short-lived tokens within Make’s custom app framework.

Currently, I’m using a Basic Connection to store the API key and secret, but I need to refresh the token frequently. Here are the challenges I’m facing:

  1. There’s no built-in way to automatically refresh tokens before each request.
  2. The Connection’s ‘Verify’ feature requires manual intervention, which isn’t practical for such short-lived tokens.
  3. Make.com custom apps don’t allow adding custom functions that could handle token refresh.

Given these limitations, I’m wondering about the best approach to handle this situation. Some questions I have:

  1. Is there a way to implement a token refresh mechanism within Make’s custom app framework?
  2. How can I ensure that each module uses a fresh token without manual intervention?
  3. Are there any workarounds or best practices for dealing with such short-lived tokens in Make.com?
  4. Should I consider a different connection type or structure for this API?

I would greatly appreciate any insights, experiences, or suggestions from those who have dealt with similar scenarios in Make.com custom apps. How have you handled APIs with very short token lifespans?

Thank you in advance for your help and expertise!

Reference of API
https://developers.imweb.me/getstarted/token