Send Data Node

The Common Send Data node is non-visual node that maps collected user input to the data required by third‑party systems and forwards it. There should be only one Send Data node that is executed in flow.

Use Case

Use the Send Data node when you want to:

• Send collected data to fronten and create customer notification.

Don't use it when:

• You need to send data to third-party systems other than fronten and customer notifications.
• Your use case is tied to a specific country or line of business.
• If you already execute one Send Data node.

UI Examples

TellUs

Only output, no UI

WebChat

Only output, no UI

Behavior

When Send Data node is executed, it starts the following actions:

1. Uploads files
2. Promotes attachments
3. Verifies bank account (only for Norway)
4. Creates fronten activity
5. Sends customer notification

Node Metadata

Property	Description
Node class	SendDataNode
MessageType	32
CanBeEdited	False
CanBeProcessedOnce	True
RequireUserResponse	No

Input Properties

Property	Description
frontenSummaryDefinition	HTML summary for Fronten - needed for Fronten notification Default Values: En:[XXXXX.summaryContentOutput]
frontenHtmlFileName	HTML file name - needed for Fronten notification
frontenBusinessArea	e.g. Private, Commercial, PrivateNO etc. - needed for Fronten notification
frontenCategory	e.g. HEST, NO_INTERNETT_EIENDOM, etc.
frontenDocumentType	eg. SKADEANMALAN, doc1 etc. - needed for Fronten notification
frontenQueue	e.g. NO_PRIVATE_CLAIMS etc. - needed for Fronten notification
frontenClaimHandlerId	needed for Fronten notification
businessArea	e.g. Private, Commercial, etc. - needed for Customer notification
lineOfBusiness	e.g. Undefined, Motor, Property, PersonalInjury, Travel, Boat, Animal, FollowUp, HealthNavigator, CargoAndLiability, Cargo, Liability, Into, OtherProperty etc. - needed for Customer notification
insuredObject	e.g. Undefined, PersonalCar, PersonalComputer, Laptop, MobilePhone, TechnicalDevice, Bicycle, Questionnaire, LegalExpenses, Liability, Tablet, TravelExpenses, ProfAthletes, PersonalInjury, Property, Animal, FollowUp, IfStart, CargoAndLiability, Cargo, Into, Forest etc. - needed for Customer notification
customerNumber	Customer number - needed for backend processes (Optional)
policyNumber	Policy number - needed for backend processes (Optional)
claimNumber	Claim Number - needed for backend processes and Fronten notification (Optional)
claimType	E.g. Horse, None etc. - needed for Customer notification
parentType	e.g. None, SmortCustomer, SmortQuote, SmortInsurance, SkrotClaim, VSGClaim, FenixCustomer, FenixQuote, FenixInsurance, FenixClaim, FinessQuote, CleoQuote, CleoInsurance, CleoClaim, CarSECustomer, CarSEQuote, CarSEInsurance, CarSEClaim, FinessClaim, FinessInsurance, FinessCustomer, FellesKundeCustomer, NorpolInsurance, NorpolQuote, NorskadeClaim, PPAInsurance, PPBClaim, PPTQuote, EuroWizInsurance, IfTilbudQuote, FARActivity, WaypointCustomer, WaypointInsurance, WaypointQuote, WaypointClaim, SibyllaClaimant, WorkItem, CumulativeBilling, LighthouseCustomer, LighthouseInsurance, LighthouseQuote, LighthouseClaim, SibyllaClaim, WaypointPersonalInjury - needed for Fronten notification, if ClaimNumber is provided (Optional)
claimReportName	Claim report name - needed for Fronten notification
country	Country - needed for backend processes
customerEmail	Customer email - needed for Customer notification
customerName	Customer name - needed for Customer notification
customerPhone	Customer Phone - needed for Customer notification
incidentDate	Incident Date - needed for backend processes.
stargateTemplate	Stargate Template - in this you can specify which template to use for customer notification, if left empty, then default one will be used PrivateChatbotMotorConfirmation. To use new template it is still have to be mapped in backend (contact our PO). Currently available templates - PrivateChatbotPropertyConfirmation, PrivateChatbotPersonalConfirmation
vehicleRegistrationNumber	Vehicle registration number
legalNumber	Legal Number
brand	e.g. Undefined, Volvia, Polestar etc.
scenario	e.g. CommercialReporter etc.
stargateUtmTag	e.g. no_if_b2c_claim_animal etc.
bankAccountOwner	Bank account owner - needed for bank account verification
bankAccountNumber	Bank account number - needed for bank account verification
bankAccountOwnerSummaryMessage	Bank account owner summary message - needed for bank account verification Default Values: No:KAR-sjekk utført. [bankAccountNumber] er bekreftet tilhørende fnr. [bankAccountOwner].
notBankAccountOwnerSummaryMessage	Default Values: No:KAR-sjekk utført. [bankAccountNumber] tilhører IKKE fnr. [bankAccountOwner].
bankAccountNotVerifiedSummaryMessage	Default Values: No:KAR-sjekk IKKE utført. Må gjøres av skaderådgiver.
defaultValidationMessage	The default error message shown when the input is invalid or missing. This is used if no custom validation message is provided. Default Values: En:Please type in value No:Skriv noe Dk:Indtast værdi Fi:Kirjoita kenttään Se:Ange värde
sectionId	Groups this node visually under a specific section in TellUs. When multiple nodes share the same sectionId, they are displayed together under a shared header.
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 true, the form will not proceed without input. Default Values: En:true Allowed Values: true false
isRequiredValidationMessage	The error message shown when a required field is left empty. This overrides the default validation message when isRequired is true. Default Values: En:Value is required No:Verdi er påkrevd Dk:Værdi er påkrævet Fi:Arvo vaaditaan Se:Värde krävs

Output Properties

No output properties.

Editor Example

Try it in the Atlas Editor

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.