Introduction
Hermes includes scheduled automation and messaging integrations. Together, they can turn a tested one-off report into a daily or weekly briefing that runs while your laptop is offline.
Examples
Useful briefings include a weekday project-status digest, a weekly competitor update, a morning list of relevant support issues, or a recurring audit of public documentation links.
Start with a manual request:
Review the project notes changed during the last seven days. Summarize completed work, blocked work, and decisions needed next week. Link each item to its source file. Write the report only; do not send it yet.
Schedule it only after the manual result is accurate.
In-depth guide
1. Make one run reliable
Define the exact sources, time window, output format, and maximum length. Run the request manually several times with different inputs. Resolve missing-data and empty-result behavior before adding a schedule.
2. Choose a delivery channel
Hermes supports a messaging gateway for platforms including Telegram, Discord, Slack, WhatsApp, and Signal. Configure only the channel and recipients that need the report. Follow the official Hermes messaging guide for platform credentials and access controls.
3. Create the schedule
Tell Hermes the timezone, recurrence, request, and delivery destination. Ask it to repeat the interpreted schedule before saving it. Prefer an explicit timezone and time, such as “09:00 Europe/Berlin every weekday,” over “each morning.”
4. Define failure behavior
A scheduled task should report when a source is unavailable rather than silently inventing a complete result. Set a useful empty-state message, limit retries, and avoid sending partial reports as if they were final.
5. Observe the first runs
Check the first delivery time, source window, links, and recipient. Compare at least one scheduled result with a manual run. Review model-credit consumption in the Parlant Agents dashboard and adjust frequency or model choice if needed.
6. Pause before changing
Pause a schedule before changing its sources, credentials, or destination. Test the revised prompt manually, update the scheduled task, and confirm its interpreted recurrence again. Remove obsolete schedules so that they do not continue consuming model credit.
See the official Hermes cron guide and messaging guide for current runtime commands.