anna@example.com arrives, and a contact with this address already exists.
The check flags the gap · add the field or change the step
Peak Automations · Field mapping
When a form is submitted, every value lands where it belongs: the email address on the contact, the request in the task. Peak suggests the mapping and shows it in readable form. A contact is found by its email address and never created twice.
Pass data on cleanlyIllustrative example · sample data · nothing is transferred
01 / Example value
Does the trigger deliver an email address?
The check flags the gap · add the field or change the step
Change the example value. The next step follows the check.
Sample data · nothing runs
Two example inputs
Schematic example. In the product the check lists missing required values one by one before the test.
anna@example.com arrives, and a contact with this address already exists.
The check flags the gap · add the field or change the step
The existing contact is completed · no duplicate
Trust needs clarity
01 / The existing evidence
The values on this page are made up. The test run in your workspace shows what really arrives.
02 / Your check
You edit mappings by sentence or in the flow view. A freely movable canvas is planned.
Compare both paths and their reasons.
03 / The clear limit
Targets outside Peak only go through connections your workspace made itself.
The next step
Start Peak Automations and check the mapping of your first automation in a test run.
Pass data on cleanlyIllustrative example · sample data · nothing is transferred
No. A contact is found by email address; if it exists, it is completed instead of created again.
The check flags the gap before the test. You add the field or change the step.
No. You edit by sentence or in the flow view. A free canvas is planned.