> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lindy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Variable

> Store temporary data during task execution that can be referenced and updated throughout your workflow

<div style={{ display: 'flex', justifyContent: 'center', margin: '2rem 0' }}>
  <div className="video-card">
    <video src="https://lindy-docs-content.nyc3.digitaloceanspaces.com/Human%20in%20Loop.mp4" width="600" autoPlay muted loop playsInline style={{ display: 'block', width: '100%', borderRadius: '16px' }} />
  </div>
</div>

## Overview

Set Variables lets you store temporary data during task execution. Perfect for:

* **Temporary storage** — hold data that doesn't need to be in global context
* **Data passing** — share information between different parts of your workflow
* **Variable updates** — overwrite existing variables with new values
* **Clean organization** — keep your workflow organized with named references

Variables are scoped to the current task and automatically cleaned up when the task completes.

## Set Variable Action

* **What it does**: Creates or updates a variable that can be referenced throughout your current task execution.

<Frame>
  <img src="https://mintcdn.com/lindyai/Pb4BV8JAHp4lkO2R/lindy-brand-assets/set-variable.png?fit=max&auto=format&n=Pb4BV8JAHp4lkO2R&q=85&s=ddc6c32a9547b9e2707a24c5af237315" alt="Setting variables for workflow organization" width="1744" height="1054" data-path="lindy-brand-assets/set-variable.png" />
</Frame>

### Inputs

* **Name**: The variable name that will be used for referencing (becomes the reference key)
* **Value**: The data to store — can be set manually, using prompts with context, or auto mode

### Outputs

* **Variable Reference**: The stored value can be referenced as an output in other actions
* **Updated Variable**: If using the same name, it overwrites the existing variable

<Tip>
  Pro tip: Rename the Set Variable action to the actual variable name (like "Set Customer ID") for better organization when selecting output references from the menu.
</Tip>

## When to Use Variables

### Common Use Cases

* Store important data before clearing context
* Pass data between different workflow phases
* Keep track of counters, IDs, or status values
* Hold temporary calculations or processed results

### Variable Updates

* Use the same variable name to overwrite existing values
* Update variables as your workflow progresses
* Maintain state across different actions and conditions

## Best Practices

<AccordionGroup>
  <Accordion title="Variable Naming">
    * Use clear, descriptive names for easy identification
    * Rename the action to match the variable name
    * Use consistent naming conventions across your workflow
    * Avoid generic names like "temp" or "data"
  </Accordion>

  <Accordion title="Variable Management">
    * Store essential data in variables before clearing context
    * Update variables rather than creating duplicates
    * Use variables for data that doesn't need global context access
    * Keep variable scope limited to what's actually needed
  </Accordion>

  <Accordion title="Workflow Organization">
    * Group related variables near each other in the workflow
    * Use descriptive action names for better output reference selection
    * Document complex variables with clear action names
    * Clean up unused variables by not referencing them
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="Context" icon="database" href="/skills/lindy-utilities/context">
    Manage global memory and prioritized information
  </Card>

  <Card title="Memories" icon="database" href="/skills/lindy-utilities/memories">
    Store persistent knowledge across all task executions
  </Card>

  <Card title="Observability" icon="magnifying-glass" href="/skills/lindy-utilities/observability">
    Access advanced monitoring and observability features
  </Card>

  <Card title="LLM Call" icon="database" href="/skills/lindy-utilities/llm-call">
    Make direct AI requests with controlled context
  </Card>
</CardGroup>