Before switching on
New contacts from the CRM should go to HubSpot, but only after an approval.
Your sentenceContact → HubSpot with approval
Every change is a new version. Only a version whose test run passed becomes active.
Peak Automations · Approvals
Risky steps wait.
Until a person says yes.
What has outside effect or changes a lot does not simply run through. Peak holds such steps and puts a confirmation or an owner or admin approval into the Inbox. Only then does the run continue.
Local example · sample data · nothing is approved
SENTENCE BEFORE FLOWYour sentence.
Your sentence.
An automation you can check.
02 / The visible flow3 example steps
Contact → HubSpot with approval
Why: Data leaves Peak One. So the step waits for an approval and only uses your workspace's HubSpot connection.
- 01Trigger: contact created in Peak CRM
- 02Step 1: owner or admin approval in the Inbox
- 03Step 2: create or update the contact in HubSpot
02 / Three layers of control
Test. Approve. Trace.
Control starts before the first run and does not end with switching on.
02 / Visible flow
During the run
- 01Example step
Trigger: contact created in Peak CRM
- 02Example step
Step 1: owner or admin approval in the Inbox
- 03Example step
Step 2: create or update the contact in HubSpot
Afterwards
The run history shows who approved or declined and when. Before every step Peak checks workspace and role again.
Your review is still open.
These marks activate nothing.Proposal and activation stay separate
What approvals do not replace.
No extra rights
An automation may never do more than the person who owns it. An approval does not lift missing permissions.
Your sentence→Fixed rule→Example steps
The sculpture illustrates the flow. It is not a product interface.
The sculpture illustrates the flow. It is not a product interface.No silent pass in the background
If a step waits, the run waits. Peak does not skip an open approval after a deadline.
- Activation
- Only after a passed test
- Rights
- Roles in the workspace
Examples are fixed
The approval cards above are stored examples. Nothing is approved or run on this page.
ProposalActivation
The next step
Automatic where it is safe. With you where it counts.
Start Peak Automations, build a flow with outside effect and see where the approval sits.
Build an automation with approvalPeak Automations · ApprovalsWhat needs no approval?
Local example · sample data · nothing is approved
Frequently asked questions
Who can approve?
Owners and admins of the workspace.
Where do I see pending approvals?
In the Peak One Inbox.
What happens on rejection?
The step does not run, and the run shows the decision in its history.