Demo Workflow - How to Use workflowStaticData()

This workflow demonstrates how to use the `workflowStaticData()` function to set any type of variable that will persist within workflow executions. [https://docs.n8n.io/code/cookbook/builtin/get-workflow-static-data/](https://docs.n8n.io/code/cookbook/builtin/get-workflow-static-data/) This can be useful, for example, when working with access tokens that expire after a certain time period. Using `staticData`, we can keep a record of that access token and the expiry time and build our workflow logic around it. ## Important Static Data only persists across **production** executions, i.e., triggered by Webhooks or Schedule triggers (not manual executions!). For this, the workflow will have to be activated. ## Setup - Configure HTTP Request node to fetch access token from your API (optional) - Activate workflow - Test the workflow with the webhook production link - You can check the population of the static data in the single executions ### Feedback If you found this useful or want to report some missing information - I'd be happy to hear from you at [ria@n8n.io](mailto:ria@n8n.io)

Platform
n8n
Category
Data & Analytics
Price
$9.99
Creator
Ria

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Data & Analytics workflows

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.