Get Submission Relation Node
The Get Submission Relation node retrieves the related conversation ID from relation storage based on the submission ID passed to TellUs.
Node is used exclusively for TellUs.
Use Case
Use the Get Submission Relation node when:
- You need to retrieve the conversation ID associated with a submission that was previously stored in relation storage.
- You want to access the history and context of a previous conversation based on a received submission ID.
UI Examples
- TellUs
- WebChat
Only output, no UI
Not applicable
Behavior
- Blocking: non blocking node
- Produces output: creates
conversationIdoutput based on submission ID input - Supports validation: can be marked as required/optional
Node Metadata
| Property | Description |
|---|---|
| Node class | GetSubmissionRelationNode |
| MessageType | 46 |
| CanBeEdited | True |
| CanBeProcessedOnce | False |
| RequireUserResponse | No |
Input Properties
| Property | Description |
|---|---|
| submissionId | Submission ID |
| defaultValidationMessage | The default error message shown when the input is invalid or missing. This is used if no custom validation message is provided.
|
| sectionId | Groups this node visually under a specific section in TellUs. When multiple nodes share the same |
| defaultValue | The initial value that is prefilled into the input field when the node is rendered. Useful for suggesting defaults or pre-populating known data. |
| isRequired | Determines whether the user must provide a value before continuing. If set to
|
| isRequiredValidationMessage | The error message shown when a required field is left empty. This overrides the default validation message when
|
Output Properties
| Property | Description |
|---|---|
| conversationId | Conversation ID |
Editor Example
This link opens a prebuilt flow using this node in context. You can inspect how it's configured, how it's connected, and how it behaves in a real editor environment.
