Peak Automations / Customer onboarding template

Signed is not the same as started.
The first step comes along.

Between the yes and the first meeting a week often gets lost because nobody kicks off the start. This template ties the customer start to an event Peak already knows: the signature in Peak Sign, a Stripe payment or the outcome of a meeting in Peak Booking.

For which occasion?

Your first line

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 the agreement with Nordwind Studio GmbH (example) is fully signed in Peak Sign

start the “customer start” workflow, create the task “Plan kickoff” for [account manager] and report it in the project lead's Inbox.

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

Edit your draft in detailText, details & next action

Your sample automation

Make it yours.

Trigger83/90Steps132/220

Additional details

CompanyPhoneTiming

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

Test & approval110/180

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

01 / Anatomy of the automation

Trigger, steps,
check.

At the top is the event that starts it. Below come the steps Peak carries out, and last what is tested before activation and what is confirmed every time.

01 / The contextYour current draft

A beginning
that fits the flow.

Peak Automations · local preview

When the agreement with Nordwind Studio GmbH (example) is fully signed in Peak Sign

start the “customer start” workflow, create the task “Plan kickoff” for [account manager] and report it in the project lead's Inbox.

Context → Details → Next action

The trigger says when the automation starts.

02 / The details

4visible details

01Имя02E-mail03Request04Company

03 / The next actionText preview

And then?
A clear next action.

Test run with sample data, then activate. It then runs without further questions because no step goes outside.

Test the flow in the preview directly above.

02 / Three starting points

Same customer start.
Different trigger.

Choose how you recognise the start: by the signature, by the incoming payment or by the kickoff that took place. The steps stay similar, only the occasion changes.

Another example replaces the current demo draft.

01 / Agreement signedSelected
From agreement to kickoff.
Peak Sign reports the last signature.
Start after signature
„When the agreement with Nordwind Studio GmbH (example) is fully signed in Peak Sign“
4 details · Company
02 / Payment receivedSample draft
Paid, so let's go.
Through the connected Stripe connection.
Start after Stripe payment
„When a payment for [package] arrives through Stripe“
5 details · Company + Timing
03 / Kickoff heldSample draft
Lose nothing after the kickoff.
Peak Booking: meeting outcome set.
After the meeting
„When the outcome “Kickoff held” is set in Peak Booking“
5 details · Company + Timing

03 / Move on deliberately

From yes to the first meeting.

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.

Good to know

Clear answers.
Before the next step.

What you should know

Does Peak write to the customer by itself?

No. A welcome e-mail is created as a Gmail step through the connected mailbox and waits for your confirmation. Without confirmation it stays a draft.

What is the “customer start” workflow?

A workflow from the workflow engine with fixed steps and due dates that you define yourself. The automation only starts it, it does not change it.

Does this template already run in my workspace?

No. The demo here only runs on this page. In Peak Automations you pick a template or describe the flow in one sentence, Peak shows it as a sentence and as a flow, you start a test run, and only after the current version passes its test can it be activated.

Does Peak connect my accounts by itself?

No. A person connects Slack, Gmail, Google Calendar, HubSpot, Typeform, Stripe and the other services in Settings → Integrations. The connections belong to the workspace, and Peak only uses those. The template list shows first what fits your connected apps.

Are the names in the example real?

No. “Nordwind Studio GmbH”, “Example Ltd” and every person are made up. You replace placeholders in square brackets with your own details.

Frequently asked questions

How does the template recognise a new customer?

By an event you choose: the fully signed agreement in Peak Sign, a payment through Stripe or the outcome “Kickoff held” in Peak Booking.

Does Peak send e-mails without me?

No. Every e-mail to the outside goes through your connected mailbox and waits in the Inbox for your confirmation. Risky steps also need an owner or admin approval.

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.