Skip to content
Nappai Documentation

Set Session ID

The Set Session ID component lets you give a unique identifier to a user’s session.
When you set this ID, all other components in the same project will see it, so they can keep track of the conversation history and share data that belongs to that particular session.

How it Works

The component simply stores the ID you provide in the dashboard’s internal graph.
No external services are called.
When you click Run, the component writes the ID into the graph’s session store and returns the same ID as its output.
Other components that need to know the current session can read this value from the graph.

Inputs

  • Session ID:
    Sets a unique ID for the user session. This ID is shared across all components in the project to ensure they operate within the same session and maintain conversation history.

Outputs

  • Session ID Set (Text):
    The component returns the session ID that was just stored. You can use this output to confirm the ID or feed it into other components that require the session value.

Usage Example

  1. Add the component to the start of your workflow.
  2. Enter a session ID (e.g., user_12345).
  3. Connect the output (Session ID Set) to any component that needs to know the current session, such as a chatbot or a data‑retrieval component.
  4. When the workflow runs, the session ID is saved and all connected components will use the same ID, keeping the conversation history intact.
  • Get Session ID – Retrieves the current session ID for use in other parts of the workflow.
  • Clear Session ID – Removes the session ID from the graph, useful when starting a new conversation.
  • Chatbot – Uses the session ID to pull the correct conversation history.

Tips and Best Practices

  • Use a consistent naming scheme (e.g., user_ + user number) so you can easily identify sessions.
  • Keep the session ID short and alphanumeric to avoid accidental truncation.
  • If you need to support multiple users simultaneously, generate a unique ID for each user before adding the component to the workflow.

Security Considerations

  • The session ID is stored only in the dashboard’s internal graph; it is not sent to external services.
  • Avoid using personally identifiable information (PII) directly as the session ID.
  • If the session ID is exposed in logs or UI, ensure it is masked or removed to protect user privacy.