Automations & notices
Notifications & Feishu
Distinguish app notices, messaging connections and Android system push.
Three notification paths#
The app bell provides version and account notices. Feishu connections can link conversations according to configuration. Android system push reminds you to inspect approvals or results. A notification does not approve an action.
Connect Feishu#
- Open desktop Settings → Messaging and inspect the supported connection entry.
- Enter the required application configuration and complete relevant permissions, events and availability settings in Feishu.
- Follow the connection flow to associate the account/conversation, then inspect connection status and linked conversations.
- Test a non-sensitive message and confirm it reaches the intended conversation. The precise association flow depends on deployment and interface. Messaging support does not imply the complete remote-approval feature set.
WeCom notifications#
The current messaging settings page has no separate WeCom configuration card. Existing WeCom notifications may use an API source or automation webhook. A one-way notification endpoint does not provide two-way conversations, tool approvals or computer control.
Missing Android notifications#
Open the app and inspect the actual conversation first. Then check operating-system permissions, the app toggle, push configuration and network. Online synchronization and offline push are separate capabilities.
Before external sending#
Confirm recipients, summary content and source scope. Keep credential-bearing notification URLs in connection settings, not in public tutorials or conversation text.