08 · data
Shape the item — add, rename, or hardcode fields before the next node.
When to use it
Anytime the next node needs cleaner field names or defaults. Cheap insurance before Switch/IF/CRM.
Writeup
Shape the item — add, rename, or hardcode fields before the next node. Anytime the next node needs cleaner field names or defaults. Cheap insurance before Switch/IF/CRM.
Step by step — how to wire it
01
Add Set after the trigger
Webhook → Set is the usual pattern for intake flows.
02
Define fields
intent, email, tier — map from {{$json.body.*}} or temporary literals for testing.
03
Remove demo literals
Before production, replace hard-coded sales / lead@example.com with expressions.
04
Hand off
Connect Set → Switch / IF / HTTP so those nodes see the clean fields.
How it functions
Assignments
Manual mode: name + value (literal or expression like {{$json.body.email}}).
Passes an item forward
Downstream nodes read the new shape — old raw body may still exist depending on options.
Used for
Used for 1
Normalizing webhook payloads
Used for 2
Demo defaults (intent=sales) while wiring CRM
Used for 3
Building Slack message strings
Tips
Prefer expressions over literals the moment the form is real.
Keep PII field names consistent across workflows for ops sanity.