n8n Workflow Demo: Use workflowStaticData() for Tokens

Keep your n8n access tokens across runs—using workflowStaticData()

This n8n workflow demo shows exactly how to use the built-in workflowStaticData() function to store variables that persist within workflow executions—perfect for managing expiring access tokens without losing state.

What this workflow does

Built as a practical reference, the workflow demonstrates storing and reusing token-related data via workflowStaticData(). The core idea is to keep a record of an access token and its expiry time, then base your logic on that stored information.

• Fetch an access token (optional): The workflow includes an HTTP Request node to request an access token from your API.
• Store token data with staticData: Using workflowStaticData(), it shows how to save the token and expiry as variables that persist across executions.
• Run with the correct execution type: It explains that Static Data persists only across production executions (triggered by Webhooks or Schedule Triggers, not manual runs). The workflow must be activated.
• Test via webhook: After activation, you can test using the webhook production link and verify the static data population in the single executions.

Use cases

• SaaS operators maintaining API integrations where access tokens expire periodically.
• Automation engineers needing stateful token handling to avoid unnecessary re-authentication.
• n8n users learning how to implement persistent workflow variables for reliable automation.

Technical details

• Built-in function: workflowStaticData() (from the n8n code cookbook)
• Nodes / components: if, code, no op, Webhook, HTTP Request, and supporting elements like sticky note.

Note: For static data persistence, activate the workflow and test using the webhook production link—manual execution will not persist Static Data.