Actions61
- 电子表格 Actions
- 云空间 Actions
- 消息 Actions
- 云文档 Actions
- 日历 Actions
- 多维表格 Actions
Overview
This node allows you to recall (retract) a previously sent message in Feishu. It is useful in scenarios where a message was sent by mistake or contains incorrect information, and you need to remove it from the conversation for all participants. For example, if a sensitive file or wrong announcement was posted, this node can programmatically retract that message.
Properties
| Name | Type | Meaning |
|---|---|---|
| 待撤回的消息的ID | String | The ID of the message to be recalled. This identifies which message will be retracted from Feishu. |
Output
The output will be a JSON object for each processed input item. If the operation succeeds, the structure will reflect the response from the Feishu API regarding the recall action.
If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message, and possibly additional error details if available.
Example success output:
{
// ...fields returned by Feishu's recall message API
}
Example error output:
{
"error": "Error message here"
}
Dependencies
- Feishu Account: You must have valid Feishu credentials configured in n8n (
feishuCredentialsApi). - API Access: The Feishu app used must have permission to recall messages.
- n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
- Missing Method Error:
- Message:
未实现方法: 消息.撤回消息
This means the node does not support the selected resource/operation combination. Double-check that "消息" and "撤回消息" are implemented.
- Message:
- Authentication Errors:
- If your credentials are invalid or missing required permissions, the node will fail. Ensure your Feishu app has the correct scopes and the credentials are up to date.
- Invalid Message ID:
- If the provided message ID does not exist or cannot be recalled (e.g., due to time limits or permissions), the Feishu API will return an error.
- Error Handling:
- If "Continue On Fail" is enabled, errors will be included in the output as described above. Otherwise, the workflow will stop on error.