How can I store user-provided details in variables during a conversation?

Below are a few strategies you can use to capture conversation details (like name, telephone, email, etc.) during a conversation for later use within your workflow:

---

1. Using the Set Node to Pass Variables

The simplest approach is to capture the user's responses and store them in JSON properties. For example, after receiving the user’s response, use a Set node to create fields for each piece of information:

JSONCopied
{
  "name": "John Doe",
  "telephone": "123-456-7890",
  "email": "john.doe@example.com"
}

You can then reference these values in subsequent nodes using expressions like:

{{ $json["name"] }}
{{ $json["telephone"] }}
{{ $json["email"] }}

This method is best when you only need the data for the current workflow execution. It keeps the information alongside your regular flow data, and you can manipulate or pass these values to different integrations.

---

2. Using Workflow Static Data for Persistence

If you need to store data that persists across nodes or even across workflow executions, consider using Workflow Static Data. While custom variables (set via the Variables page) are read-only and globally shared, Workflow Static Data allows you to set and later access custom data during a workflow. You can use a Function node to set data like this:

JAVASCRIPTCopied
// Fetch the workflow static data storage
const data = $getWorkflowStaticData('node');

// Store user details for later use
data.name = $json.name;
data.telephone = $json.telephone;
data.email = $json.email;

return { json: $json };

Later in your workflow, you can retrieve these values using a similar pattern:

JAVASCRIPTCopied
const data = $getWorkflowStaticData('node');

return { json: {
  name: data.name,
  telephone: data.telephone,
  email: data.email
}};

Keep in mind that static data persists for the duration of the workflow execution context and can be useful if you need to accumulate data from several nodes or checkpoints.

---

3. Global Custom Variables (Instance-Level)

n8n also offers custom variables that are configured at the instance level (via the Variables page). However, these variables are:

• Read-only during workflow execution.
• Meant to store values that are shared across workflows.
• Configurable only by the instance owner.

Since your use-case involves updating values during a conversation, the Set node or Workflow Static Data approach is usually more suitable.

---

When to Choose Which Method

• Set Node / Passing Data in JSON:
  Best for temporary storage and manipulation within the same workflow execution.

• Workflow Static Data:
  Great for storing dynamic data that might be needed in multiple parts of a complex workflow, especially when the flow spans several nodes and you might want to modify or access the data at different points.

• Global Custom Variables:
  Ideal for values that need to be consistent and shared across all workflows; however, since they are read-only, they aren’t the best fit for storing dynamic conversation details.

---

By incorporating one of these methods, you can capture the user's input into variables and use them later on in your flow, whether that means sending them to an API, including them in an email, or passing them to another integrated tool.

Feel free to ask if you need more examples on how to implement any of these techniques in your n8n workflows!

Below is an explanation of how you can capture user‑provided data (like name, telephone, email, etc.) and store it for later use in your workflow.

---

Custom Variables vs. Workflow Static Data

n8n provides two main ways to "store" data that can be reused in your workflow:

1. Custom Variables:
   • Designed to hold values that are defined in the UI and shared across the instance.
   • They are read‑only and meant for values that don’t change during workflow execution.

2. Workflow Static Data:
   • Ideal for capturing dynamic data (like user-provided details during a conversation).
   • Allows you to store data at runtime from within your nodes and later retrieve or manipulate it.

Since you need to store values provided during the conversation and update them as the user supplies further details, Workflow Static Data is the method to use.

---

How to Use Workflow Static Data

You can store and retrieve data within your workflow using the Workflow Static Data object. For example, you can use a Code node (or Function node) to set and later get this data.

Example: Storing User Information

In a Code node, you might do something like this:

JAVASCRIPTCopied
// Retrieve the existing static data (or create a new container if none exists)
const staticData = $workflow.getWorkflowStaticData("global");

// Assume the incoming JSON data has fields "name", "telephone", and "email"
staticData.user = {
  name: $json.name,
  telephone: $json.telephone,
  email: $json.email,
};

// Optionally, return something so that downstream nodes can know the data was stored
return { json: { message: "User data stored successfully" } };

Later in your workflow, you can access this stored data using another Code node:

JAVASCRIPTCopied
const staticData = $workflow.getWorkflowStaticData("global");

// Now you can use the user data in your logic
const userName = staticData.user?.name || "Unknown";
const userTelephone = staticData.user?.telephone || "No telephone provided";
const userEmail = staticData.user?.email || "No email provided";

return { json: { userName, userTelephone, userEmail } };

---

Steps to Integrate This in Your Flow

1. Collect the User Data:
   Use your trigger (e.g., Chat Trigger or a custom node) to capture the user's responses.

2. Store the Data:
   Use a Code node as shown above to save these values using getWorkflowStaticData method.

3. Retrieve and Manipulate Later:
   At any point later in your flow, use another Code node to access the data, apply logic, or pass values to other nodes (like notifications, API calls, etc.).

---

By leveraging Workflow Static Data, you’ll be able to capture user details during the conversation and manipulate them throughout your workflow without conflicting with the static, read‑only custom variables available via the UI.

For more details and additional examples on how to work with workflow static data, please check the Workflow static data documentation.