Product · Automations
Describe the task once and choose what starts it: an email arriving, a message in Slack or Teams, a meeting coming up, a webhook from another system, or a schedule. Sherpa does the work and sends the result to your inbox or your team’s channel.
Open KPI_tracker.xlsx and read the latest completed week, Monday to Sunday. For revenue, gross margin, operating cash and qualified pipeline, compare the week with the week before and with plan. Show each figure with its unit and period.
Explain every movement larger than 5% in one sentence, citing the tab and row it came from.
List any input that is missing or older than seven days rather than estimating it.
Keep last week’s figures in memory so the next run can check they were not restated.
When an email from FP&A says the tracker changed mid-week, run again and lead with what was restated.
Slack: #leadershipBrief it the way you would brief a colleague and get a draft automation to check and adjust.
An email, a Slack or Teams message, a meeting or a webhook can start a run, and so can a schedule in your timezone.
Each automation remembers what it found last time, so every run builds on the one before.
Plain language
Write what the automation should do the way you would brief a colleague. Altitude turns it into a draft automation for you to check and adjust before it runs.
Open KPI_tracker.xlsx and read the latest completed week, Monday to Sunday. For revenue, gross margin, operating cash and qualified pipeline, compare the week with the week before and with plan. Show each figure with its unit and period.
Explain every movement larger than 5% in one sentence, citing the tab and row it came from.
List any input that is missing or older than seven days rather than estimating it.
Keep last week’s figures in memory so the next run can check they were not restated.
Triggers and tools
Add the triggers the work needs: a new email in Outlook or Gmail, a message in a Slack or Teams channel, a meeting coming up, a webhook or notification, or a schedule. Conditions narrow each one to the sender, channel or meeting you mean.
Then choose what a run may use: your files, web search, memory and the model. The History tab lists every run with what started it and what it sent, and opens the chat that shows each step.
Read Q3_close_checklist.xlsx and the trial balance in Close / September. List every task still open, who owns it and how many days it has left.
Check each reconciliation against the trial balance and name any difference over $5,000 with the account it sits in.
When someone asks in Teams, answer in the thread with the same list and tag the owners of anything overdue.
Memory
Each automation keeps its own memory between runs, separate from your chats. You can read and edit it as Markdown.
Context saved only for this automation, carried from run to run.
Accounts to watch
Carried from run to run. Sherpa adds an account when it slips and drops it when it recovers.
Delivery
Results arrive by email, in Slack or in Microsoft Teams. Pick the channels once and every run reports there.
| Metric | Week 38 | Week 37 | Plan | vs plan |
|---|---|---|---|---|
| Revenue | $2.41m | $2.33m | $2.35m | +2.6% |
| Gross margin | 61.8% | 62.4% | 62.0% | −0.2 pts |
| Operating cash | $14.6m | $15.1m | — | — |
| Qualified pipeline | $9.8m | $8.9m | $9.5m | +3.2% |
You stay in control
An automation runs without you, so you can always see what it did and decide who may change it.
The run history keeps every run, so you can see what Sherpa did and what it sent.
Share an automation with your team, with each person as an owner, editor or viewer.
Admins can turn automations on or off for the whole organization through a team policy.
Presets
Every weekday morning: what changed overnight in the sources you choose, in one email.
Morning_digest_22-Sep.eml
Workflows
Processes your team has built, tested and published. Anyone can run them; they finish in the background.