Notifications & Delivery
Anyy can publish immediate notifications and user-visible messages through the resident Gateway. Delivery is routing-aware: the assistant can address the current user or the trusted origin of the current Channel conversation, not arbitrary external contacts.
Two Message Actions
| Action | Use it for |
|---|---|
| Notification | A title and message that should become immediately visible to the user |
| Message | Text and supported attachments sent to the current user or trusted Channel origin |
Both actions are audited. Sending is non-idempotent: retrying can produce a duplicate message.
Delivery Targets
Scheduled jobs and notifications can use these delivery targets:
| Target | Meaning |
|---|---|
gateway | Publish to the resident Gateway event stream |
origin | Route back to the trusted origin of the current Channel conversation |
current_user_default | Resolve the current user's default Channel binding, optionally by platform |
none | Do not deliver a user-facing result |
Anyy does not treat platform names as arbitrary recipient addresses. A configured and authorized Channel binding must resolve the route.
Ask Anyy to Send
Examples:
When this check finishes, notify me with the title “Backup verified” and a one-line result.
Send this summary back to the current Channel conversation.
Send the generated report to my default Telegram binding.
If no trusted origin or default binding exists, Anyy reports that the route is unavailable instead of guessing a recipient.
Receipts and Delivery State
A successful publish proves that Anyy accepted and dispatched the event into its delivery pipeline. It does not by itself prove final receipt by Telegram, email, SMS, or another external service.
Message sends can create a receipt that later reflects adapter delivery progress. Channel capabilities differ: some adapters report acknowledgements while others can report only dispatch.
Check the message receipt or Channel health before retrying an uncertain send. A second send can create a duplicate when the first one reached the provider but its acknowledgement was delayed.
Attachments
Message delivery can include Anyy outbound attachments when the selected Channel declares support for that media kind. Unsupported attachments are rejected rather than silently discarded.
Configure a Default Route
Connect the Channel in Dashboard → Channel or with anyy setup channel, verify its access policy, and test it. Scheduled jobs can then select current_user_default plus a delivery channel.
See Messaging Platforms and Scheduled Automations.
Troubleshooting
| Problem | Fix |
|---|---|
| No default route | Configure and verify a Channel binding for the current user |
| Origin delivery unavailable | Start the request from a trusted Channel conversation |
| Publish succeeds but no external message appears | Check the receipt, Gateway status, and Channel doctor output |
| Duplicate message | Stop retrying automatically and inspect the earlier receipt/event |
| Attachment rejected | Use a media kind supported by the selected Channel |