İçeriğe geç
Peak Atlas

Peak Automations / Approval template

Automatic up to the line.
Then a person decides.

Not everything should go out unseen. In Peak Automations a low-risk step simply runs, a send to the outside waits for a confirmation, and a risky step needs an owner or admin approval. This template shows three flows where the approval is built in on purpose.

For which occasion?

Change the trigger. The preview next to it reacts instantly.

Edit all texts and details ↗Test the automation locally ↗
Local demo with sample data
Automation · previewPreview reacts instantly
Peak AutomationsLocal demo with sample data

When a new response to [survey] arrives in Typeform

let an AI step draft a short reply and prepare it through Gmail to the given address.

Use sample data only.

Stays in this browser. Nothing is sent, nothing is saved automatically.

Edit your draft in detailText, details & next action
01

Your sample automation

Make it yours.

Additional details

Name, e-mail and occasion are always part of the trigger as sample data in this demo.

JSON file for your local draft. Not an import into Peak Automations.

01 / Anatomy of the automation

Prepare, pause,
approve.

The steps prepare everything Peak may prepare. At the approval the run pauses, and the Inbox shows exactly what is about to happen. Only after the decision does it continue.

01 / The contextYour current draft

A beginning
that fits the flow.

Peak Automations · local preview
When a new response to [survey] arrives in Typeform

let an AI step draft a short reply and prepare it through Gmail to the given address.

Context → Details → Next action

The trigger says when the automation starts.

02 / The details
4visible details
01Ad02E-mail03Request04Company
03 / The next actionText preview

And then?
A clear next action.

Test run first. The e-mail waits in the Inbox for your confirmation, Peak does not send it on its own.

Test the flow in the preview directly above.

02 / Three lines

Mail, CRM,
application.

Choose the point where a person should look at it in your case. The kind of approval follows the risk of the step.

Another example replaces the current demo draft.

  • 01 / ConfirmationSelected

    The draft waits for you.

    AI draft, sent only after a click.

    Reply to Typeform

    „When a new response to [survey] arrives in Typeform“

    4 details · Company
  • 02 / Owner/admin approvalSample draft

    Change external data, not in passing.

    Change in another CRM with approval.

    HubSpot after a lost deal

    „When a deal with Example Ltd is lost in Peak CRM“

    4 details · Company
  • 03 / ConfirmationSample draft

    Friendly, but not blind.

    Peak Recruit reports a new application.

    Application acknowledgement

    „When an application for [role] arrives in Peak Recruit“

    4 details · Timing

03 / Move on deliberately

Control without manual work.

In Peak Automations you describe the flow in one sentence or pick the template. Peak checks connections and permissions, shows the flow as boxes and arrows, and you start a test run. Only then do you activate it. Every change becomes a new version, and the run history explains in plain language what happened.

Your context, your details and your next action — as one connected draft.

Please fill in the draft texts before you take them along.

Stays in this browser. Nothing is sent, nothing is saved automatically.

Frequently asked questions

Which steps need an approval?

Low-risk steps simply run. A send to the outside waits for a confirmation, a risky step needs an owner or admin approval.

Does an approval expire after a deadline?

No. The run waits visibly as “waiting for approval” and does not continue on its own.

When does the template actually run?

Only once you have taken it over in Peak Automations, tested it with sample data and then activated it. No automation can be activated without a passed test of the current version.

More in Peak Automations