Build a scheduled morning briefing with AIDA skills and cron

A morning briefing is only useful if it answers the same few questions reliably: What is on my calendar? Which tasks need attention? What should I know before I start? AIDA by Autafy can manage calendar events and tasks, create custom AI skills from chat, and schedule recurring tasks through cron automations. Its automated daily briefings can be delivered to messaging platforms.

The practical approach is to define the briefing first, create a skill that describes the work, then ask AIDA to run it on a schedule. AIDA runs on your server and can use a local model through Ollama or an API key. The exact wording of your requests will depend on your workflow; do not assume a prompt replaces connecting the relevant calendar or task service.

1. Decide what the briefing should contain

Keep the first version small. Choose a calendar, task list and delivery destination that AIDA can access. AIDA integrates with Google Workspace and Microsoft 365, and it supports interaction through WhatsApp, Telegram, Discord, a desktop PWA and web chat. Use the services and channel you have connected.

Write down the boundaries before you ask for automation. For example: include today’s meetings and tasks due today; flag overdue work; summarize only emails that need a reply; keep the result short. Specify the time and time zone, and name the messaging destination. If you want weather included, give AIDA the location and check whether the result is suitable before making it part of a routine you depend on.

2. Ask AIDA to create a briefing skill

In a chat with AIDA, describe the briefing as a repeatable task. AIDA supports creating custom AI skills by asking for them in chat. A useful request is direct and specific:

“Create a morning briefing skill. Summarize today’s calendar events and tasks due today, call out overdue tasks, and list emails that appear to need a reply. Keep it concise, use headings, and do not guess when information is missing. Include weather for [your location] only if you can retrieve it.”

This is a starting brief, not a guarantee that every source is connected or every requested item is available. If AIDA asks for clarification, answer it. After the skill is created, run it manually. Check the dates, task status and email selection against the source records. Edit the instructions if it includes too much detail, misses a useful category or presents uncertainty as fact.

Personal preferences can make these instructions more useful over time, but memory should not replace verification. For a closer look at the trade-offs, see how persistent memory affects day-to-day agent work.

3. Set a recurring run

Once the manual result is dependable, ask AIDA to schedule the skill as a recurring morning task. AIDA supports cron automations created through chat. Include the exact schedule, time zone, destination and the name or description of the briefing skill. For example:

“Schedule this morning briefing to run every weekday at 7:00 a.m. [time zone] and send the result to [messaging destination]. Use the morning briefing skill I just created.”

Do not assume the schedule was saved just because the request was understood. Check AIDA’s response for a clear confirmation of what will run, when it will run and where it will be delivered. If the response is ambiguous, ask AIDA to restate the schedule. Also ask it to confirm that the scheduled task can invoke the custom skill. The product supports both custom skills and recurring automations, but a confirmation is a sensible check before building your routine around their combination.

4. Test the delivery, then refine

Let one scheduled run complete, or ask AIDA to run the task once more before relying on the next morning’s delivery. Confirm that the message arrives in the chosen channel and that the date, calendar items and tasks match what you expect. If the briefing is too long, narrow the requested fields. If it misses an important item, clarify which source or priority to check.

Be especially careful with weather and urgency rules. AIDA’s published description of its daily briefing includes weather, meetings, tasks and priority emails, but a location, connected source or individual setup can affect what is available. Treat the first few results as a test, not as proof that every future briefing will be complete.

Keep the routine maintainable

A briefing works best when its instructions stay simple and its schedule reflects how you actually work. Start with one delivery time and one destination. Change the skill when your priorities change, and review the automation if your calendar or task setup changes. AIDA’s self-hosted model lets it run on your server; it does not remove the need to check connected accounts, model configuration and the accuracy of the output.

After the routine is stable, you can decide whether to add other recurring summaries. Keep each one narrow enough to verify. A dependable short briefing is more useful than a long report that quietly mixes missing data with confident conclusions.