01 / The existing evidence
Registered events only
Triggers exist only for events Peak has registered. Triggers for changes to any field, inactivity or thresholds are planned.
Field mapping
- Mapping
- Example
- Arrival in the target
- Not tested
Peak Automations · Native integrations
Your Peak apps trigger.
The same objects, no copies.
A won deal in Peak CRM, a form response in Peak Forms, a signed agreement in Peak Sign: events from Peak One start automations directly. The tasks, contacts and notes they create are the same objects as in the apps, not synced copies.
Connect Peak apps automaticallyExample mapping · no connection is made
Peak FormsThe responsePeak CRMThe contact fieldPeak CRM · Example mapping
One mapping in detail
01 / Peak FormsEmail
02 / Fictional test valuealex@example.com
03 / Peak CRM
Identity (email)A readable field path as an example. No run.
View all 5 mappings
| Peak Forms | Field on the contact |
|---|---|
Identity (email) | |
| First name | First name |
| Last name | Last name |
| Company | Company |
| Message | Note |
Example mapping
No run
No run
Nothing is connected on this page. A person in the workspace sets up connections under Settings → Integrations.
One concrete targetPeak CRMArrival in the targetNot tested yet
Map fields. Keep the source.
Peak CRMArrival in the targetNot tested yetThe mapping shows which value from the trigger goes into which step. Only a test run in your workspace shows what actually arrives.
02 / Why native is simpler
No syncing, because there is only one truth.
Peak triggers and Peak actions work on Peak One's shared data. There is nothing that can drift apart.
- 01 / Trigger
Triggers from Peak
Task created, completed or overdue, deal won or lost, contact created, form submitted, meeting outcome, invoice, agreement, application, conversation and more.
Where does the event come from?Peak CRMPeak FormsPeak Sign - 02 / Action
Actions in Peak
Notify, create or complete a task, create or update a contact or company, note, record a decision, start a workflow.
What is created?TaskContactInbox notice - 03 / Object
Same rights
An automation only sees and changes what the person who owns it may. Before every step Peak checks workspace and role.
Where does it live?V Peak OneOne recordSame rights
Trust needs clarity
What native does not mean.
Field mapping02 / Your check
Contacts without duplicates
A contact is found by email address. If it is missing, Peak asks while building instead of creating a second contact.
- Connection
- Not connected here
- Rights
- Roles in the workspace
03 / The clear limit
No run on this page
The mapping above is an example. Nothing is connected, created or run here.
- Peak trigger
- Peak action
- AI step
- Planned
The next step
Your apps work together, not side by side.
Start Peak Automations and pick an event from a Peak app as the trigger.
Connect Peak apps automatically→Check in a test run of your workspace what actually arrived.
Frequently asked questions
Is data copied between apps?
No. A contact stays the same person and a task the same task in every app.
Do I need a connection for this?
No. Peak triggers and actions run inside your workspace without an external connection.
Which permissions apply?
The same as yours. Before each step Peak checks workspace and role.