Score Node

Compute a composite score from weighted criteria and optionally assign tiers

Last updated 24 Jun 2026

The Score node adds a numeric score column to each record, computed as a weighted combination of one or more criteria. Each criterion can be normalized and directed independently, and the resulting score can drive an optional tier label.

When to Use

Use Score to build lead scores, risk scores, or priority rankings from existing record fields. Feed the output column into a downstream Condition or Switch node to route records by score or tier.

Configuration

Field	Type	Description
`criteria`	array	List of scoring criteria (see below)
`outputField`	string	Column to write the composite score to (default: `score`)
`tiersEnabled`	`false` \| `true`	Whether to assign a tier label from the score (default: `false`)
`tierField`	string	Column to write the tier label to when tiers are enabled (default: `tier`)
`boundaries`	array	Tier boundaries (`label` + `minScore`), used when tiers are enabled

Criterion Properties

Property	Type	Description
`field`	string	Record field to score
`weight`	number	Relative weight of this criterion's contribution
`normalize`	`none` \| `min-max` \| `z-score`	Normalization applied to the field before weighting (default: `none`)
`direction`	`higher-is-better` \| `lower-is-better`	Whether higher or lower raw values score better (default: `higher-is-better`)

Example

Score leads by engagement and recency, then bucket into tiers:

criteria:
  - field: email_opens_30d
    weight: 0.5
    normalize: min-max
    direction: higher-is-better
  - field: days_since_last_contact
    weight: 0.5
    normalize: min-max
    direction: lower-is-better
outputField: lead_score
tiersEnabled: "true"
tierField: lead_tier
boundaries:
  - label: High
    minScore: 0.7
  - label: Medium
    minScore: 0.4

Notes

Weights are relative; normalize per-criterion (min-max or z-score) when fields are on different numeric scales.
direction: lower-is-better inverts a criterion so that smaller raw values produce higher scores.
Non-numeric or unparseable field values are excluded from that criterion's contribution.
Tier boundaries are matched by descending minScore — a record gets the first tier whose minScore it meets.

Node Reference Complete reference for all automation node types, organized by category Transform Node Reshape records with map, aggregate, deduplicate, sort, and limit operations Condition Node Branch automation execution on field conditions, routing records to Match or No Match outputs

Still stuck? Browse the FAQ or contact us.

When to Use

Configuration

Criterion Properties

Example

Notes

Related articles