feishu-urgent

Feishu urgent message (buzz) notifications. Activate when user mentions urgent, buzz, remind, or escalation for messages.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "feishu-urgent" with this command: npx skills add m1heng/clawdbot-feishu/m1heng-clawdbot-feishu-feishu-urgent

Feishu Urgent Tool

Single tool feishu_urgent for sending urgent (buzz) notifications to recipients for an already-sent message.

Overview

Urgent notifications (also called "buzz" in Feishu) send a strong push notification to specified recipients. Use this to escalate important messages that require immediate attention.

Important: The message must already be sent before sending an urgent notification. You need the message_id from a previously sent message.

Urgency Types

TypeDescriptionCost
appIn-app buzz notification (popup + sound)Free
smsSMS push to recipient's phoneMay incur cost
phoneVoice call to recipient's phoneMay incur cost

Send App Urgent (Default)

{
  "message_id": "om_xxx",
  "user_ids": ["ou_xxx"],
  "urgent_type": "app"
}

Send SMS Urgent

{
  "message_id": "om_xxx",
  "user_ids": ["ou_xxx"],
  "urgent_type": "sms"
}

Send Phone Call Urgent

{
  "message_id": "om_xxx",
  "user_ids": ["ou_xxx"],
  "urgent_type": "phone"
}

Multiple Recipients

{
  "message_id": "om_xxx",
  "user_ids": ["ou_xxx", "ou_yyy", "ou_zzz"],
  "urgent_type": "app"
}

Parameters

ParameterRequiredDescription
message_idYesMessage ID to send urgent notification for (e.g., om_xxx). The message must already be sent.
user_idsYesList of open_id values to buzz. Minimum 1 recipient. Recipients must be members of the chat where the message was sent.
urgent_typeNoUrgency delivery method: app (default), sms, or phone.

Response

{
  "ok": true,
  "message_id": "om_xxx",
  "urgent_type": "app",
  "invalid_user_list": []
}
  • invalid_user_list: List of user IDs that could not receive the urgent notification (e.g., not in the chat, or invalid ID).

Configuration

channels:
  feishu:
    tools:
      urgent: true  # default: true

Permissions

  • im:message.urgent - Send in-app urgent notifications
  • im:message.urgent:sms - Send SMS urgent notifications (may incur cost)
  • im:message.urgent:phone - Send phone call urgent notifications (may incur cost)

Notes

  • Message must exist: The message_id must be from a message that has already been sent. You cannot send urgent notifications for messages being composed.
  • Recipients must be chat members: Users in user_ids must be members of the chat where the original message was sent.
  • Quota limits: Urgent notifications have quotas (especially sms and phone). Error 230024 ("Reach the upper limit of urgent message") indicates quota exhausted. Contact your tenant admin or check Feishu admin console > Cost Center > Quota.
  • Invalid user IDs: Returns HTTP 400 error if any user_id is invalid (not found or not in the chat).
  • Cost warning: sms and phone types may incur costs on the tenant. Use app (default) for free notifications.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

feishu-doc

No summary provided by upstream source.

Repository SourceNeeds Review
649-m1heng
Automation

feishu-drive

No summary provided by upstream source.

Repository SourceNeeds Review
380-m1heng
Automation

feishu-wiki

No summary provided by upstream source.

Repository SourceNeeds Review
251-m1heng
Automation

feishu-perm

No summary provided by upstream source.

Repository SourceNeeds Review
141-m1heng