Actions106
- 日历 Actions
- 多维表格 Actions
- 知识库 Actions
- 通讯录 Actions
- 任务 Actions
- 电子表格 Actions
- 云空间 Actions
- 消息 Actions
- 云文档 Actions
Overview
This node is designed to interact with the Feishu platform, specifically to perform operations related to messages. The provided operation "批量撤回消息" (Batch Recall Messages) allows users to revoke or recall a batch of previously sent messages identified by a batch message task ID. This is useful in scenarios where multiple messages were sent in bulk and need to be withdrawn, for example, if incorrect information was sent or a campaign needs to be stopped.
Practical examples include:
- Revoking a marketing campaign's batch messages after discovering an error.
- Withdrawing notifications sent in bulk due to updated information.
- Managing message recalls efficiently without handling each message individually.
Properties
| Name | Meaning |
|---|---|
| 待撤回的批量消息任务ID | The batch message task ID to recall. This ID corresponds to the message_id field returned by the batch send message API, used to identify a single batch sending request. |
Output
The node outputs JSON data representing the result of the batch recall operation for each input item. Each output item contains the response from the Feishu API regarding the recall request. If errors occur and the node is set to continue on failure, error details are included in the output JSON.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Feishu platform.
- The node depends on the Feishu API endpoints for batch message recall.
- Proper configuration of the Feishu API credentials within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or expired API credentials may cause authentication failures.
- Providing an incorrect or non-existent batch message ID will result in errors from the Feishu API.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors thrown by the Feishu API are captured and can be output as part of the node’s error handling.
- If the node is not set to continue on failure, it will throw an error stopping execution; enabling "continue on fail" allows processing subsequent items.
- Typical error messages might indicate invalid parameters or permission issues; verify the batch message ID and API permissions accordingly.