Kanban-Pro

Integração com a API Chatwoot Kanban

Kanban Item → Change Status

AI-generated

Overview

This node integrates with the Chatwoot Kanban API to manage Kanban items within a specified account. Specifically, the 'Change Status' operation allows users to update the status of a Kanban item to 'Open', 'Closed', or 'Archived'. This is useful for workflow automation where task or item statuses need to be programmatically updated based on external triggers or conditions, such as marking a task as completed or archiving old items.

Use Case Examples

  1. Automatically change the status of a Kanban item to 'Closed' when a related support ticket is resolved.
  2. Set the status of a Kanban item to 'Archived' after a certain period of inactivity to keep the board clean.

Properties

Name Meaning
Account ID The ID of the Chatwoot account where the Kanban item exists.
Item ID The unique identifier of the Kanban item whose status is to be changed.
Status The new status to assign to the Kanban item. Options are 'Open', 'Closed', or 'Archived'.

Output

JSON

  • status - The updated status of the Kanban item after the change operation.
  • id - The unique identifier of the Kanban item.
  • title - The title of the Kanban item.
  • funnel_id - The ID of the funnel to which the Kanban item belongs.
  • stage_id - The ID of the stage within the funnel where the item is currently located.
  • priority - The priority level of the Kanban item.
  • conversation_id - The ID of the conversation linked to the Kanban item, if any.

Dependencies

  • Requires an API key credential for authentication with the Chatwoot Kanban API.

Troubleshooting

  • Ensure the Account ID and Item ID are correct and exist in the Chatwoot account to avoid 'not found' errors.
  • Verify that the API key credential is valid and has the necessary permissions to update Kanban items.
  • If the status value is invalid or missing, the API will reject the request; use only 'open', 'closed', or 'archived'.
  • Network or connectivity issues may cause request failures; check your network and API endpoint availability.

Links

Discussion