Actions25
Overview
This node integrates with a corporate messaging platform to update template card messages that have been previously sent. It is designed for scenarios where interactive message cards need to be dynamically updated after delivery, such as modifying button labels or refreshing content based on user actions or backend events.
Practical examples include:
- Updating the text of a button on a task card after the task status changes.
- Refreshing information displayed in a notification card without sending a new message.
- Changing call-to-action prompts dynamically in response to workflow progress.
Properties
| Name | Meaning |
|---|---|
| *企业应用的ID (agentid) | The internal ID of the enterprise application; can be found in the app's settings page. |
| 企业的成员ID列表 (userids) | List of member UserIDs within the enterprise who will receive the updated card (up to 1000 members). |
| 企业的部门ID列表 (partyids) | List of department IDs within the enterprise to receive the updated card (up to 100 departments). |
| 企业的标签ID列表 (tagids) | List of tag IDs within the enterprise to receive the updated card (up to 100 tags). |
| 更新整个任务接收人员 (atall) | Boolean flag indicating whether to update all recipients of the task. |
| *更新卡片所需要消费的Code (response_code) | A unique code required to update the card; obtained from the send message API or callback interface. Each code can only be used once and must be used within 72 hours. |
| *需要更新的按钮的文案 (button.replace_name) | The new label text for the button that needs to be updated on the card. |
Output
The node outputs JSON data representing the result of the update operation. This typically includes success or error information returned by the messaging platform's API. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating with the corporate messaging platform.
- The node depends on the platform's API endpoint to update template card messages using the provided
response_code. - Proper configuration of credentials with valid permissions to send and update messages is necessary.
Troubleshooting
Common issues:
- Using an expired or already consumed
response_codewill cause the update to fail. Codes are valid for only 72 hours and can be used once. - Providing invalid or empty
agentidor recipient lists may result in errors or no updates being applied. - Exceeding the maximum allowed number of recipients (1000 users, 100 departments, or 100 tags) will likely cause request rejection.
- Using an expired or already consumed
Error messages:
- Errors related to authentication usually indicate incorrect or missing API credentials.
- "Code already used" or "Code expired" errors mean the
response_codeis invalid for updating. - Validation errors on recipient IDs suggest malformed or non-existent user/department/tag identifiers.
To resolve these issues:
- Ensure the
response_codeis fresh and unused. - Verify all IDs and parameters conform to platform requirements.
- Confirm API credentials are correctly configured and have sufficient permissions.
Links and References
- Official documentation for the corporate messaging platform's template card update API (refer to your platform's developer portal).
- Guidelines on managing
response_codelifecycle and usage limits. - Best practices for constructing and updating interactive message cards.