Peak Automations / Proposal approvals
The proposal is ready.Has anyone looked at it?
A proposal e-mail goes outside and can't be recalled. In Peak Automations, sending an e-mail is a risky step: the automation prepares everything, an AI step drafts the text, and then the run waits in the Inbox for a confirmation or the approval of an owner or admin. Only then does Peak send from your connected Gmail.
Put the goal into words. Add perspectives and timing right below.
Try it on a local sample proposal.
Draft / approval / sending
Where the run pauses.
- Prepare
- Write an e-mail draft with AI
- Pause
- Approval by an owner or admin in the Inbox
- Send
- From the connected Gmail, then a note on the contact
Your approval rule
From three answers to an e-mail with approval.
Fill in the example with a made-up proposal and see how occasion, approval and draft fit together. Nothing is sent.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three questions. An e-mail with approval.
Draft · not yet put together
- The trigger
- Still open
- The approval
- Still open
- The draft
- Still open
From draft to sent e-mail
Prepare. Approve. Send.
The order makes sure nothing goes outside that nobody has seen.
- 01Case
The occasion starts the run.
PrepareWrite an e-mail draft with AI
An analysed call, a won deal or a manual start. Peak gathers the details the e-mail needs.
Trigger → details - 02Action
Approval is a step of its own.
PauseApproval by an owner or admin in the Inbox
The run waits in the Inbox. Whoever approves sees recipient, subject and text. Without approval nothing goes out, and the history says so.
Working tool → approval in the Inbox - 03Result
Sent and traceable.
SendFrom the connected Gmail, then a note on the contact
After approval Peak sends and records a note on the contact. In the local example you get an approval note.
Sample artifact → approval note
The next proof is the product
Test the approval with an e-mail to yourself.
Describe the automation, connect Gmail in settings and start the test run. The test sends nothing; it shows where the run will wait for approval.
Start Peak AutomationsPeak Automations / Your next step
What goes outside, someone sees first.
Try the example with the e-mail where a second look is worth the most.
See the approval flow
Four eyes, one click.
From the connected Gmail, then a note on the contact
Frequently asked questions
Who can approve an e-mail?
Risky steps wait for a confirmation or for approval by an owner or admin, depending on the setting. Approval runs through the Inbox.
Does Peak create the proposal itself?
Not in this automation. It drafts the e-mail and records a note. A continuous chain with Peak Offer is planned.
What happens without approval?
Then nothing goes out, and the history shows the run waited for approval.