企业微信(WeCom)-基础Install

Summary

Send a WeCom template-card application message to selected users, departments, tags, or the app’s visible audience. Build one of five card types with form fields or provide the complete template_card object as JSON; the node validates the card and submits it through the WeCom API.

Inputs

• recipientType — Choose the app-visible audience, selected members, departments, or tags. “组合选择” combines selected member, department, and tag IDs; “手动输入” accepts comma- or pipe-separated IDs in the relevant fields. Member, department, and tag lists are limited to 1,000, 100, and 100 entries respectively.
• touser / toparty / totag or manual ID fields — Select recipients from the loaded lists or enter their IDs, according to recipientType. These recipient fields determine who receives the message.
• template_card_input_mode — Choose form input or JSON input. In JSON mode, template_card_json is the complete required template_card object.
• card_type and card fields — In form mode, choose button_interaction, multiple_interaction, vote_interaction, news_notice, or text_notice, then configure its applicable content, choices, buttons, images, links, and actions. Some card types require particular fields; for example, news_notice requires either card_image or image_text_area, and multiple_interaction requires selectors.
• task_id — Optional task identifier; required when action_menu is configured. The UI notes that an ID must be unique per app and limited to 128 bytes.
• enable_id_trans — Optionally convert user IDs in the message to corresponding @mentions.
• enable_duplicate_check / duplicate_check_interval — Optionally suppress duplicate message content within a time interval. The interval defaults to 1,800 seconds and is limited by the UI to 14,400 seconds.

Output shape

A single WeCom API response record per input item.

The operation sends a message as a side effect. Form mode assembles the configured fields into a template_card; JSON mode parses the supplied complete object. The node validates card structure and recipient lists before sending; WeCom API errors fail the operation.

Links

• n8n community nodes installation guide