Weekly report to a team
When to use it
Section titled “When to use it”- A team acts on new sign-ups, enquiries or form entries and wants the week's list in their inbox.
- Leaders want a short monthly summary without opening the dashboard.
- You want a warning when nothing came in, because that usually means data entry was missed.
Where the data comes from
Section titled “Where the data comes from”| How | What |
|---|---|
| A form people fill in | Whatever records your key event: an Origamy form (onboarding.submitted), a sheet or CSV imported as events, or your app. |
What it sets up
Section titled “What it sets up”| Kind | Name | What it does | Lands |
|---|---|---|---|
| Team | Operations | Gets the weekly report. | Empty |
| Team | Leadership | Gets the monthly summary. | Empty |
| Question | Report: new people | How many people the key event brought in the report's period. | Ready |
| Question | Report: new people (list) | The list of new people, one row per event. | Ready |
| Question | New people per week | New people per week, for the monthly summary. | Ready |
| Report | Weekly: new people | The week's new people, with a warning when there were none, and the task summary. | Off |
| Report | Monthly: summary | Last month's numbers compared with the month before, without names. | Off |
The questions it asks
Section titled “The questions it asks”| # | Question | Default | Fills in |
|---|---|---|---|
| 1 | Which team gets the weekly report? | Operations | team_name |
| 2 | Which event counts as a new person for this report? (a form submission, a sign-up…) Pick from your workspace's events. Forms send onboarding.submitted. | onboarding.submitted | key_event |
| 3 | Which details should the weekly list show? (event properties, not phone numbers) | first_name, last_name | list_columns |
| 4 | When should it arrive? | 0 8 * * 1 | weekly_cron |
| 5 | Should leaders also get a monthly summary? Who? | Yes | monthly_summary |
Other settings
Section titled “Other settings”These have defaults. Change any that don’t fit.
| Setting | Default | Key |
|---|---|---|
| Monthly summary team | Leadership | leaders_team |
| Time zone for the schedule | ‹workspace timezone› | timezone |
| Monthly send time | 0 9 1 * * | monthly_cron |
Timings
Section titled “Timings”- Weekly report: 0 8 * * 1 in ‹workspace timezone›, covering the last 7 days.
- Monthly summary: 0 9 1 * *, covering the previous month and compared with the month before.
Channels
Section titled “Channels”| Channel | Needed for | Before it can send |
|---|---|---|
| The reports themselves | Nothing extra. Reports come from Origamy to the team members' own sign-in addresses. |
What you need to do
Section titled “What you need to do”- Add people to the Operations team (and Leadership for the summary). A report to an empty team reaches nobody.
- Open each report and press Send now once to check it looks right.
- Switch the reports on.
- The list includes names. Reports only go to team members inside your workspace; keep it that way.
- Names in email. The list section sends names in the email body (
pii_in_email). Without it, recipients open a link to see the rows. Reports only go to people in your teams. - The zero alert is how the real build caught Sundays when nobody typed in the paper cards.
- A report sent from a follow-up (a
send_reportstep) is skipped while the report is off.
Copilot eval
Section titled “Copilot eval”The request used to test the copilot on this playbook (a live eval):
Every Monday morning, email our operations team a list of everyone who signed up in the last week, and warn them if nobody did. Once a month send the managers a summary compared with the month before.
It passes when every piece is a valid draft and everything lands off, with at least: report.