Get Policies Node
The Get Policies node retrieves motor policy information for Norway based on the provided policy number, vehicle registration number, and incident date. This non-visual node queries the service in the background and returns comprehensive policy details including policy holder information, coverage dates, business area, and product information for use by subsequent nodes in the flow.
To display policy information to the user, use the Show Policies node after retrieving the data with the Get Policies node.
Use Case
Use the Get Policies node when you want to:
- Retrieve comprehensive motor policy information for a Norway customer based on policy number, vehicle registration number, or incident date.
- Fetch policy holder details, coverage dates, business area, and product information for use in downstream processing.
- Query policy data in the background to support claims handling, policy inquiries, or incident reporting workflows.
Don't use it when:
- The policy is not from Norway; this node is specific to Norway motor policies.
- You lack the required inputs (policy number or vehicle registration number and incident date).
UI Examples
- TellUs
- WebChat
Only output, no UI
Only output, no UI
Behavior
- Non-blocking: the node executes in the background without user interaction.
- Requires input: expects policy number or vehicle registration number, and incident date from node properties.
- Produces output: returns policy information (policy number, policy holder details, coverage dates, business area, product name, etc.) stored in the value bag.
- Renders: no UI elements.
- Validation: throws an error if incident date is invalid or both policy number and vehicle registration number are missing.
- Output handling: returns
Okstatus with policy data if successful,Notstatus if policy not found (404), orExceptionstatus if an error occurs.
Node Metadata
| Property | Description |
|---|---|
| Node class | GetPoliciesNode |
| MessageType | 103 |
| CanBeEdited | False |
| CanBeProcessedOnce | False |
| RequireUserResponse | No |
Input Properties
| Property | Description |
|---|---|
| incidentDate | The date of the incident used for retrieving the policy at that time. |
| vehicleRegistrationNumber | The vehicle registration number to use for retrieving policy information. |
| policyNumber | The policy number to use for retrieving policy information. |
| 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 |
|---|---|
| policy | The complete policy object containing all policy information retrieved from the service. |
| policySystem | The system or backend that manages the policy. |
| fullPolicyNumber | The complete policy number for the retrieved policy. |
| policyType | The type of the policy. |
| groupPolicyNumber | The group policy number if the policy is part of a group. |
| validFrom | The date from which the policy is valid. |
| validTo | The date until which the policy is valid. |
| businessArea | The business area associated with the policy. |
| lineOfBusiness | The line of business associated with the policy. |
| productName | The name of the insurance product associated with the policy. |
| country | The country where the policy is registered. |
| holderName | The name of the policy holder. |
| holderEmail | The email address of the policy holder. |
| holderPhone | The phone number of the policy holder. |
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.
