Feishu Node icon

Feishu Node

Feishu Node

Actions106

Overview

This node integrates with Feishu's task management API, specifically allowing users to update existing tasks. It is useful in automation workflows where task details need to be programmatically modified based on dynamic inputs or external triggers. For example, you could update the status, description, or other fields of a task when a related event occurs elsewhere in your system.

Properties

Name Meaning
任务ID The unique identifier of the task to update.
用户 ID 类型 The type of user ID used for identification. Options: Open ID, Union ID, User ID.
请求体 The JSON request body containing the fields to update in the task. Must follow Feishu's API specification for task updates.

Output

The node outputs an array of JSON objects representing the updated task data returned from Feishu after the update operation. Each item corresponds to one input item processed and contains the updated task information as per Feishu's API response.

If an error occurs during processing and "Continue On Fail" is enabled, the output will include an error object with the error message instead of task data for that item.

Dependencies

  • Requires an API key credential for authenticating with Feishu's API.
  • The node depends on Feishu's task management API v2 for updating tasks.
  • Proper configuration of credentials within n8n is necessary to authorize requests.

Troubleshooting

  • Common issues:

    • Invalid or missing task ID will cause the update to fail.
    • Incorrect user ID type may result in authorization or identification errors.
    • Malformed JSON in the request body can cause API rejection.
    • Network or authentication failures if API credentials are not set correctly.
  • Error messages:

    • Errors thrown by the Feishu API will be surfaced, often including details about invalid parameters or permission issues.
    • If "Continue On Fail" is disabled, the node execution will stop on the first error encountered.
    • To resolve errors, verify the task ID exists, ensure the user ID type matches the expected format, and confirm the request body adheres to Feishu's API schema.

Links and References

Discussion