PopoOpenPlatform Api icon

PopoOpenPlatform Api

POPO OpenPlatform API

Actions59

消息卡片（旧） → 发送卡片消息

AI-generated

Overview

This node sends card messages using the POPO OpenPlatform API, specifically for the resource '消息卡片（旧）' and the operation '发送卡片消息'. It allows sending card messages either to individual users (P2P) or to teams (TEAM) by specifying the sender (robot account), recipients, and card template details. It supports customization through JSON options and variable maps for public and private card data, and optionally version control and callback configuration.

Use Case Examples

  1. Sending a card message to multiple individual users by specifying their emails.
  2. Sending a card message to a team by specifying the team ID.
  3. Customizing the card message with public and private variable maps in JSON format.

Properties

Name Meaning
From (机器人账号) The robot account sending the card message, required for authentication and identification.
To Type Specifies the recipient type, either individual users (P2P) or a team (TEAM).
To List (P2P 多个邮箱) A list of recipient emails when sending to individual users (P2P).
To Tid (群号) The team or group ID when sending to a team (TEAM).
Template Uuid The unique identifier of the card message template to use, required.
Instance Uuid The unique identifier of the card message instance, required.
CallBack Config Key Optional callback configuration key for message callbacks.
Options (JSON) Optional JSON string to configure additional message options like enableForward or lastMessage.
Public Variable Map (JSON) JSON string representing public variables for the card message.
Batch Private Variable Map (JSON) JSON string representing private variables for the card message, keyed by email.
Version Optional version string for enabling version control of the card message.

Output

JSON

  • response - The API response after sending the card message, containing status and details.

Dependencies

  • Requires an API key credential for POPO OpenPlatform API authentication.

Troubleshooting

  • Ensure the 'From' robot account is correctly configured and authorized to send messages.
  • Verify that the 'Template Uuid' and 'Instance Uuid' are valid and correspond to existing card templates and instances.
  • When sending to P2P, ensure the 'To List' contains valid email addresses.
  • For TEAM messages, ensure the 'To Tid' is a valid and accessible team ID.
  • Check the JSON format of 'Options (JSON)', 'Public Variable Map (JSON)', and 'Batch Private Variable Map (JSON)' to avoid parsing errors.

Discussion