Skip to content
Nappai Documentation

Set Conversation ID

The Set Conversation ID component lets you give a name or number to the current chat or workflow session.
By assigning a unique ID, all other components in the same project can recognize that they belong to the same conversation, making it easier to keep track of messages, responses, and data that belong together.

How it Works

When you drop this component into your dashboard, you type a Conversation ID into the field.
The component then tells the Nappai system to remember that ID for the rest of the session.
Any other component that needs to know which conversation is active can read this ID from the system.
No external services are called – everything happens inside Nappai’s local workflow engine.

Inputs

Input Fields

  • Conversation ID: A text value that uniquely identifies the conversation.
    This ID is shared across all components in the project so they all operate within the same conversation context.

Outputs

  • Conversation ID Set: The same ID that was entered, confirming that it has been stored.
    You can use this output to feed into other components that need to reference the current conversation.

Usage Example

  1. Drag the Set Conversation ID component onto your workflow canvas.
  2. In the Conversation ID field, type ProjectAlpha-Session1.
  3. Connect the Conversation ID Set output to any component that requires the conversation ID (for example, a “Get Conversation History” component).
  4. Run the workflow. The system now knows that all actions belong to ProjectAlpha-Session1.
  • Get Conversation ID – Reads the current conversation ID so you can display it or use it in logic.
  • Conversation History – Retrieves all messages that have been part of the current conversation.
  • Clear Conversation ID – Resets the ID when you want to start a new session.

Tips and Best Practices

  • Keep the ID short and memorable; avoid spaces or special characters that might cause confusion.
  • Use a consistent naming convention (e.g., ProjectName-SessionNumber) so you can quickly identify sessions later.
  • If you have multiple users, include a user identifier in the ID to prevent overlap.
  • Always verify that the ID is set before running components that depend on it; otherwise, they may fail or use the wrong data.

Security Considerations

  • The Conversation ID is plain text, so avoid putting sensitive personal data or passwords in it.
  • If the ID is used in URLs or logs, ensure that your dashboard’s privacy settings mask or restrict access to those logs.
  • When sharing workflows, double‑check that the ID does not reveal internal project names or structures that should remain confidential.