01 / The existing evidence
A mapping is not a delivery receipt
The example shows the field translation. No data was transferred here.
- Mapping
- Example
- Arrival in the workspace
- Not checked
Peak CRM · Integrations
Which Peak apps and inboxes hand data to Peak CRM, what does that require, and what is only planned? This shows the data path, not just a logo.
Start Peak CRM for freeExample mapping · no connection is made
Peak BookingThe booking
Peak CRMThe target fieldperson.emailA readable field path as an example. No transfer.
| Peak Booking | Peak CRM property |
|---|---|
person.email | |
| Tên | person.name |
| Company | company.name |
| Cuộc họp | event.starts_at |
| Source | lead.source |
The mapping shows the translation. Only a test in your workspace shows what actually arrives.
02 / Requirements before promises
A connection needs a clear owner, authorised access and a test.
Proven, planned or unknown: every connection has its own state.
You connect inboxes and accounts yourself in the product.
Only a test in your workspace shows what actually arrives.
Trust needs clarity
01 / The existing evidence
The example shows the field translation. No data was transferred here.
02 / Your check
No account is linked on this page. Access is granted only in the product.
03 / The clear limit
Peak apps, inboxes and planned connections are different states and are named one by one.
The next step
Start Peak CRM and check in the product which connections are available to you.
Start Peak CRM for freeCheck in your workspace what actually arrived.
No. You set up connections in the product. Nothing is linked or transferred here.
Peak apps work with the same contact instead of copies. You check how that looks in your case with test data in your workspace.
You see that in the product. Every connection has its own state: proven, planned or unknown.