Multiplatform Delivery

12.5. Multiplatform Delivery — Delivering Results to Multiple Platforms

One job, many destinations at once

hermes cron create "0 9 * * 1" "Weekly report" --deliver telegram,discord,slack

As already said in 18.6, a single job can deliver its result to multiple platforms at once using a comma-separated list — useful when you need both a team channel (Discord) and a personal alert (Telegram) for the same event, or a local file for storage in parallel with a real-time notification.

Available delivery targets

Telegram, Discord, Slack, Signal, or a local file — the same set of platforms the gateway supports (chapter 5), keeping things consistent between where you interact daily and where automated reports land.

Per-platform permission requirements — the most common silent source of errors

Each platform needs the right permissions to receive messages (for example, a Discord bot needs permission to send messages in the exact target channel) — missing permissions cause delivery to fail silently, with no obvious error shown even though the job “reports success” at the agent level.

Notes

• For important jobs that distribute to multiple channels, check the send permissions on each target platform before activating the job for the first time — do not wait until you notice a channel received nothing and then have to debug backwards.
• Name jobs clearly (--name) when many kinds of alerts land in the same channel — it helps distinguish the origin when several jobs send to the same place.
• For the “local file” target, consider using it for reports that need long-term storage/audit, in parallel with a chat channel for instant notification — there is no need to choose one or the other.