跳到内容
Peak Atlas

Peak Automations / Weekly report template

The same look every Monday.
Without anyone having to remember.

A weekly report rarely fails on the numbers, but because nobody kicks it off this week. This template sets a schedule, creates the review task, asks for the review in the team channel and summarises recorded decisions. You keep reading the numbers themselves in the apps they come from.

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

Every Monday at [time] (schedule)

create the task “Check weekly numbers” for [management] due the same day and report it in the Inbox.

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

Schedule, task,
review.

The trigger is a point in the calendar or a fixed interval. The steps remind, ask and record. Only what belongs in your connected Slack workspace goes outside.

01 / The contextYour current draft

A beginning
that fits the flow.

Peak Automations · local preview
Every Monday at [time] (schedule)

create the task “Check weekly numbers” for [management] due the same day and report it in the Inbox.

Context → Details → Next action

The trigger says when the automation starts.

02 / The details
4visible details
01姓名02E-mail03Request04Timing
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 beats

Start of week, end of week,
every decision.

Choose whether the rhythm starts on Monday, on Friday or with every new decision. You can use all three side by side.

Another example replaces the current demo draft.

  • 01 / Start of weekSelected

    Monday, nine o'clock, check numbers.

    Schedule: every Monday.

    Review task on Monday

    „Every Monday at [time] (schedule)“

    4 details · Timing
  • 02 / End of weekSample draft

    Friday asks the team.

    Schedule: every Friday.

    Review in Slack

    „Every Friday at [time] (schedule)“

    4 details · Timing
  • 03 / 决策Sample draft

    Decisions in brief for everyone.

    Peak Log reports a new decision.

    Summary per decision

    „When a decision is recorded in Peak Log“

    4 details · Company

03 / Move on deliberately

A rhythm that comes by itself.

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

Does Peak create the report with all numbers?

No, this template does not. It reminds, asks and summarises decisions. You read key figures in the apps they come from.

Can I set the schedule myself?

Yes, as a calendar time or a fixed interval with its own time zone. Runs are protected against firing twice.

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