Prepare contact rows
Create consistent full-name and email columns for a handoff.
Original starter · no credentials · manual execution
The sample transformation is tested against the output below. Import and execution in your specific n8n version still need verification.
When to use it
Shape records to an explicit output contract before adding a destination node.
What is in the workflow?
- Manual Trigger: start a test deliberately.
- Sample data: synthetic rows in a Code node.
- Prepare contact rows: a Code node with the transformation.
- Read first: a Sticky Note with setup and limitations.
Sample input
[
{
"firstName": "Alex",
"lastName": "Rivera",
"email": "alex@example.com"
},
{
"firstName": "Sam",
"lastName": "Lee",
"email": "sam@example.com"
}
]Expected output
Two fields per record: fullName and email.
[
{
"fullName": "Alex Rivera",
"email": "alex@example.com"
},
{
"fullName": "Sam Lee",
"email": "sam@example.com"
}
]Import and adapt
- Download the JSON and use Import from File in your n8n editor.
- Review the Code nodes, then execute manually with the included sample.
- Compare the final output to the example above.
- Replace Sample data with your own source only after reviewing the input contract.
Before using real data
Other source fields are intentionally omitted. Adjust the mapping before using it with real contact data.
This template does not send messages or contact external services. Adding a source or destination changes its behavior; test the complete workflow in your instance.