To schedule a weekly report in Kaer Workflows, describe it in chat, run it once, add an approval step before the send, and publish it on a timetable. The approval step waits for your decision, and if nobody answers, the default you chose applies.
What does a weekly report need before you build it?
Two things, and Kaer's guide asks for both before you start. The first is where the numbers come from: a connected app, a mailbox, a spreadsheet or a website. The second is what the finished report looks like and who receives it. Write both down in a few lines.
How do you set up a weekly report in Kaer?
Six steps, in order. The order matters: the test run comes before the schedule, and the approval step comes before publishing.
- Create the workflow. Open Workflows, choose Create a workflow, then give it a name and say what it does.
- Describe it in the chat. Open the workflow's chat and explain the goal as you would to a new starter: where the numbers come from, the format, and who receives it. Kaer builds the steps from that.
- Run it once. From the ⋯ menu, choose Test run (safe) or Run now, and check the output before anything is on a schedule.
- Add the approval step. Ask for an approval step before anything goes out.
- Schedule it and publish. Set a schedule, such as every Monday at 09:00 in your timezone, then click Publish.
- Check the runs. Each run appears on the workflow's Runs tab.
Where should the approval step go, and what happens if nobody answers?
Put the approval step before the part that matters, which for a report is the send, so the send waits for a decision. The approval asks you and then waits for the hours you set, 72 by default. If nobody decides in that time, the step is treated as rejected or approved, whichever you chose when you set it up.
Anything waiting on you shows in Workflow Hub under Waiting for your approval.
The same rule covers mail. Sending from Kaer Mail or Gmail waits for a person by default, and the email is held with a preview of what will go out. The security page lists the other channels that wait in the same way.
A sequence that works: one test run, then the approval, then the schedule. The order matches the scheduling guide. Kaer's guide to chasing overdue invoices also says to keep the approval in once a run becomes a weekly workflow.
What can start a weekly workflow besides a schedule?
A schedule is the usual start for a report, but Kaer's workflows page lists four others: an email arriving, another system calling the workflow's web address, a chat command, and a Run button you press yourself. Whichever one starts it, the run is handled the same way, with the same approvals and the same run history.
That matters for a report because the start and the send are separate decisions. The schedule decides when the report is written.
How do Kaer and Manus compare on scheduling?
On scheduling alone the two are close. Both run a job at a set time, both let you test before you rely on it, and both keep a list of runs. The differences are in the table, taken from each product's own page.
| Question | Kaer Workflows | Manus automations |
|---|---|---|
| What starts a run | A schedule, an email arriving, another system calling a web address, a chat command, or a Run button | A schedule, a triggered event from a connected app or a webhook, or an advanced automation built from a request |
| Test before it runs | Test run (safe), or Run now | Test run, also after you change timing, conditions, instructions or the connected account |
| Where you see runs | The Runs tab on each workflow, and items waiting on you in Workflow Hub | Updates, grouped by date, with status and a short result summary |
| Timing | The timezone you set on the schedule | A time and timezone you set; the page advises a specific time and timezone when timing matters |
If your report depends on an event in another app, check the trigger list before you choose. Manus's trigger picker names app events such as GitHub pull requests, Shopify refunds and calendar events.
How does Manus schedule the same report?
Manus's automations documentation lists a Schedule as the type for time-based work, and names daily briefs and weekly reports among its uses. You set the timing, then describe the result you want in plain language. The page advises naming a specific time and timezone when timing matters, rather than something loose like the end of the day.
Manus also says to run a test before relying on a new automation, and again after you change its timing, conditions, instructions or connected account. Each automation card has a More actions menu with pause, test, edit and delete. Updates lists the latest runs by date, with a status and a short summary of each.
Manus also has an advanced automation type, marked as beta, that turns a natural-language request into a workflow. For a report that combines several sources and conditions, that is the part to test first.
What does a first weekly report look like?
Take a hypothetical five-person lettings agency that wants a Monday note on last week's enquiries and viewings, read by the partners before the rest of the team sees it. A workable description in chat could be this:
Every Monday, read last week's enquiry mail and the viewings in our spreadsheet. Write a short note: what came in, what was viewed, and what needs a reply. Send it to me first, and to the team list only after I approve it.
The description names the sources, the format and the recipients, the same points the guide's requirements cover. Run it once on last week's mail, then correct the chat until the note reads the way you want. Only then should the Monday schedule go on.
Frequently asked questions
What does each scheduled run cost?
The publish screen shows the credits each run uses and runs its readiness checks before you publish. Current rates are on Kaer's usage pricing page.
Can I change a weekly schedule after it is live?
Yes. Ask in the workflow's chat or edit its schedule. Schedules run in the timezone you set.
