Feature Request: Wekan Node - "Update A Card" Function Custom Node

by ADMIN 67 views

Introduction

As a user of Wekan, a popular Kanban board application, and n8n, a powerful workflow automation tool, we often find ourselves looking for ways to integrate these two platforms seamlessly. One of the key features that would greatly enhance our workflow automation experience is the ability to update custom fields on Wekan cards using n8n's Wekan node. In this article, we will explore the current limitations of the Wekan node and propose a feature request for a custom node that can update Wekan card custom fields.

Current Limitations of the Wekan Node

The Wekan node in n8n is a powerful tool that allows us to interact with Wekan boards, lists, and cards. However, one of the key limitations of this node is its inability to update custom fields on Wekan cards. Custom fields are a crucial feature in Wekan, allowing users to add additional metadata to their cards. This metadata can be used to track various aspects of the card, such as its status, priority, or due date.

The Need for a Custom Node

The Wekan API provides a way to update custom fields on cards, as documented in the Wekan API v7.85 documentation. Specifically, the editCardCustomField endpoint allows us to update a card's custom field values. However, this endpoint is not currently supported by the Wekan node in n8n.

To overcome this limitation, we propose the development of a custom node that can update Wekan card custom fields. This node would allow users to interact with the editCardCustomField endpoint, enabling them to update custom fields on Wekan cards.

Benefits of a Custom Node

A custom node that can update Wekan card custom fields would bring several benefits to users of Wekan and n8n. Some of the key benefits include:

  • Improved workflow automation: With the ability to update custom fields on Wekan cards, users can automate more complex workflows that involve updating card metadata.
  • Increased flexibility: A custom node would provide users with more flexibility in how they interact with Wekan cards, allowing them to update custom fields in a more granular and controlled manner.
  • Enhanced integration: A custom node would enable users to integrate Wekan with other tools and services more seamlessly, using the editCardCustomField endpoint to update custom fields on Wekan cards.

Implementation Details

To implement a custom node that can update Wekan card custom fields, we would need to:

  • Develop a new node: Create a new node in n8n that can interact with the editCardCustomField endpoint.
  • Implement authentication: Implement authentication mechanisms to ensure that the node can authenticate with the Wekan API and access the editCardCustomField endpoint.
  • Handle errors and exceptions: Handle errors and exceptions that may occur when updating custom fields on Wekan cards.
  • Test and validate: Thoroughly test and validate the custom node to ensure that it works as expected and does not introduce any bugs or security vulnerabilities.

Conclusion

In conclusion, a custom node that can update Wekan card custom fields would greatly enhance the workflow automation experience for of Wekan and n8n. By providing users with the ability to update custom fields on Wekan cards, we can improve workflow automation, increase flexibility, and enhance integration with other tools and services. We propose the development of a custom node that can interact with the editCardCustomField endpoint, and we believe that this feature would be a valuable addition to the Wekan node in n8n.

Future Development

We believe that the development of a custom node that can update Wekan card custom fields is a worthwhile investment for the Wekan and n8n communities. We propose that the development of this node be prioritized in future development cycles, and that it be made available to users as soon as possible.

Community Involvement

We invite the Wekan and n8n communities to participate in the development of this custom node. We believe that community involvement is essential to ensuring that the node meets the needs of users and is developed in a way that is consistent with the values and principles of both Wekan and n8n.

Conclusion

Introduction

In our previous article, we discussed the need for a custom node that can update Wekan card custom fields. We proposed the development of a custom node that can interact with the editCardCustomField endpoint, enabling users to update custom fields on Wekan cards. In this article, we will answer some of the most frequently asked questions about this custom node.

Q: What is the purpose of a custom node that can update Wekan card custom fields?

A: The purpose of a custom node that can update Wekan card custom fields is to provide users with the ability to automate more complex workflows that involve updating card metadata. This node would allow users to update custom fields on Wekan cards, enabling them to track various aspects of the card, such as its status, priority, or due date.

Q: How would the custom node interact with the Wekan API?

A: The custom node would interact with the Wekan API using the editCardCustomField endpoint. This endpoint allows users to update a card's custom field values. The custom node would send a request to the Wekan API to update the custom field values, and the API would respond with the updated values.

Q: What are the benefits of a custom node that can update Wekan card custom fields?

A: The benefits of a custom node that can update Wekan card custom fields include:

  • Improved workflow automation: With the ability to update custom fields on Wekan cards, users can automate more complex workflows that involve updating card metadata.
  • Increased flexibility: A custom node would provide users with more flexibility in how they interact with Wekan cards, allowing them to update custom fields in a more granular and controlled manner.
  • Enhanced integration: A custom node would enable users to integrate Wekan with other tools and services more seamlessly, using the editCardCustomField endpoint to update custom fields on Wekan cards.

Q: How would the custom node handle errors and exceptions?

A: The custom node would handle errors and exceptions that may occur when updating custom fields on Wekan cards. This would include checking for errors in the API response, handling authentication failures, and providing users with clear error messages.

Q: Can the custom node be used with other Wekan features?

A: Yes, the custom node can be used with other Wekan features, such as boards, lists, and cards. The node would allow users to update custom fields on Wekan cards, which can be used in conjunction with other Wekan features to automate more complex workflows.

Q: How would the custom node be implemented?

A: The custom node would be implemented as a new node in n8n, using the Wekan API to interact with the editCardCustomField endpoint. The node would be developed using a programming language such as JavaScript, and would be tested and validated to ensure that it works as expected.

Q: What are the next steps for the custom node?

A: The next steps for the custom node would include:

  • Development: Developing the custom as a new node in n8n.
  • Testing and validation: Testing and validating the custom node to ensure that it works as expected.
  • Release: Releasing the custom node to users, and providing support and maintenance for the node.

Conclusion

In conclusion, a custom node that can update Wekan card custom fields would be a valuable addition to the Wekan node in n8n. We believe that this feature would greatly enhance the workflow automation experience for users of Wekan and n8n, and we look forward to seeing it become a reality in the future.