PopoOpenPlatform Api icon

PopoOpenPlatform Api

POPO OpenPlatform API

Actions59

消息卡片（旧） → 更新卡片消息

AI-generated

Overview

This node interacts with the POPO OpenPlatform API to perform various operations related to the resource "消息卡片（旧）" (Old Message Card). Specifically, for the operation "更新卡片消息" (Update Card Message), it updates the content of an existing message card by sending updated public and private variable data to the API. This is useful for dynamically modifying message cards in workflows, such as updating notification content or user-specific data in a card message.

Use Case Examples

  1. Updating a message card with new public data to reflect changes in a project status.
  2. Updating private data for specific users in a batch to personalize message card content.

Properties

Name Meaning
From (机器人账号) The robot account identifier that sends the update request.
Template Uuid The unique identifier of the message card template to update.
Instance Uuid The unique identifier of the specific message card instance to update.
Public Variable Map (JSON) A JSON string representing the public data fields to update in the message card.
Batch Private Variable Map (JSON) A JSON string representing private data fields to update for up to 20 users in the message card.
Public Update By Key Boolean flag indicating whether to update public variables by key.
Private Update By Key Boolean flag indicating whether to update private variables by key.
Version Optional version string to enable version control during the update.
Biz Code Optional business code for additional context or categorization.

Output

JSON

  • response - The API response after updating the message card, containing status and updated data details.

Dependencies

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

Troubleshooting

  • Ensure that the 'From', 'Template Uuid', and 'Instance Uuid' fields are correctly set and correspond to existing message card data.
  • Verify that the JSON strings for 'Public Variable Map' and 'Batch Private Variable Map' are valid JSON format to avoid parsing errors.
  • Check API permissions and credentials if the update request fails due to authorization issues.
  • If the update does not reflect, confirm that the version control (if used) matches the current version of the message card.

Links

Discussion