Chuyển đến nội dung

Peak Automations · Field mapping

The right value in the right field.
Without duplicate contacts.

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 cleanly

Illustrative example · sample data · nothing is transferred

EXAMPLE / LIVE PREVIEW

One check.
The fitting step.

Peak Automations / Sample flowLOCAL EXAMPLE

01 / Example value

Does the trigger deliver an email address?

02 / What Peak Automations showsThe sample form only asks for a name, not 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

One example. Two paths.
The check
decides the next step.
Compare both paths below ↓

Two example inputs

Does the trigger deliver an email address?

Schematic example. In the product the check lists missing required values one by one before the test.

Missing/ 10No key
Add the required valueEXAMPLE PATH
The sample form only asks for a name, not an email address.
Then

anna@example.com arrives, and a contact with this address already exists.

The check flags the gap · add the field or change the step

Present/ 10With key
Contact foundEXAMPLE PATH
anna@example.com arrives, and a contact with this address already exists.

The existing contact is completed · no duplicate

Trust needs clarity

What mapping does, and what it does not.

01 / The existing evidence

An example, no transfer

The values on this page are made up. The test run in your workspace shows what really arrives.

Peak Automations / Example pathsEXAMPLE
  1. Missing/10
    The sample form only asks for a name, not an email address.The check flags the gap · add the field or change the step
  2. Present/10
    anna@example.com arrives, and a contact with this address already exists.The existing contact is completed · no duplicate

02 / Your check

No free canvas

You edit mappings by sentence or in the flow view. A freely movable canvas is planned.

4 / 1010 / 10

Compare both paths and their reasons.

03 / The clear limit

Connected apps only

Targets outside Peak only go through connections your workspace made itself.

ExampleNothing runs

The next step

Map once, file it right every time.

Start Peak Automations and check the mapping of your first automation in a test run.

Pass data on cleanly
Peak Automations · Field mappingWhat arrives?

Illustrative example · sample data · nothing is transferred

Frequently asked questions

Does it create duplicate contacts?

No. A contact is found by email address; if it exists, it is completed instead of created again.

What if a required value is missing?

The check flags the gap before the test. You add the field or change the step.

Is there a freely movable canvas?

No. You edit by sentence or in the flow view. A free canvas is planned.