ormuz
Home/Orchestration/Nodes Core/Collect user name and email
User actionStable

Collect user name and email

Collects a participant's full name and email address in one interaction, with prefill from a contact draft.

Presented context
Collect user name and email
User Journey
User response

Vue d’ensemble

Collects a participant's full name and email address in one interaction, with prefill from a contact draft.

Exemple

Collect the minimum details for a representative before email verification or contact creation.

Key point A user action suspends the instance until the interaction is resolved. The User Journey presents the action; the node remains the orchestration contract determining its inputs and outputs.

Parameters 8

contact_draftOptionnelContact draft
Optional contact draft used to prefill fields. The node produces a new enriched draft without modifying this input value.
titleRequisstring
Main title presented to the participant for this action in the User Journey.
descriptionOptionnelstring
Optional supporting text shown under the title to explain what is expected from the participant.
readonly_full_name_if_prefilledOptionnelboolean
Locks the full name when it is already present in the supplied draft.
readonly_email_if_prefilledOptionnelboolean
Locks the email address when it is already present in the supplied draft.
skip_if_prefilledOptionnelboolean
Allows the step to complete automatically without interaction when all required values are already available.
allow_replay_from_hereOptionnelboolean
Allows a participant to restart a replay from this interaction when the process enables that capability. Disable it when repeating the action would be dangerous or misleading.
replay_boundaryOptionnelboolean
Marks this interaction as a replay point of no return to bound earlier steps that can be replayed or reused.

Outputs 1

contactContact draft
platform.contact draft produced or enriched by the interaction, ready for use by a later node or explicit submission.

Behavior

Both fields may be prefilled and locked independently. The step can be skipped when required values are already available. The node then returns a contact draft enriched with the retained name and email.

Limits and responsibilities

  • A syntactically valid address is not proof of control of the mailbox; use OTP verification when that guarantee is required.
  • The enriched draft remains non-persisted until explicitly submitted.