Keep your API calls running without breaks. The setup stores and renews an access token so your webhooks and scheduled jobs can call external services without failing. It is useful for teams that work with short lived tokens and need steady access.

Two triggers start the flow, a Webhook and a Schedule Trigger. A Code step builds a static store that lives across real runs. An If check decides if the saved token is still fresh using a timestamp. If it is valid, the flow goes straight to a continue step where you can add your real actions. If it is expired, an HTTP Request calls your auth endpoint to get a new token. Another Code step writes the token and the new timestamp into static data. You can also include response headers in the HTTP node if the token comes in headers.

Turn the workflow on so static data persists. Point the HTTP Request node to your real auth URL and map the token field from the response. Set the token lifetime in the If node to match your provider. Expect fewer failed calls, fewer manual updates, and faster handoffs between systems. Good for any API that rotates bearer tokens or session keys on a timer.

• Webhook trigger to start the flow from any external call
• Schedule Trigger to renew tokens on a timer without user input
• Code step to create and manage static data that persists across runs
• If node checks token age and decides whether to reuse or refresh
• HTTP Request fetches a new token from your auth endpoint and can include response headers
• Code step writes the token and timestamp into global static storage
• NoOp step as a safe place to attach your real actions that use the token
• Inline notes guide header handling and explain production persistence

• Reduce failed API calls by up to 90% through reliable token reuse
• Cut token refresh calls from many per day to only when needed
• Lower manual maintenance by removing routine token updates
• Stabilize downstream jobs that depend on constant API access
• Protect rate limits by avoiding extra authentication requests

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. Open the HTTP Request node named get new accessToken and set your real auth URL. Choose the correct method and body or query fields your provider needs. Toggle Include Response Headers and Status if the token comes in headers.
3. In the Code node named 1. initiate static data, confirm the properties that hold accessToken and tokenTimestamp are defined. Keep them as is if they match your needs.
4. Open the If node named if token is valid and set the lifetime that matches your API token. Use the stored timestamp to decide if the token is still fresh before making a new request.
5. In the Code node named 2. set token in static data, map the token from the HTTP response. If your token is in the body, read it from the correct path. If it is in headers, read it from the headers object.
6. Add your real steps after the continue with valid token node. When a node needs the token, set an Authorization header using an expression that reads from workflow static data.
7. Turn the workflow on. Static data only persists for active workflows that run by Webhook or Schedule, not for manual runs.
8. Test the Webhook URL by sending a request from your app or a tool like a REST client. Confirm the first run fetches a token and later runs reuse it while it is valid.
9. If the token is not saved, check the HTTP node response shape and the mapping in the Code step. If static data does not persist, make sure the workflow is active and you triggered it with Webhook or Schedule.
10. Adjust the schedule to refresh slightly before actual expiry if your provider does not allow grace periods.