Workspace icon

Workspace

Get and change data from Workspace API
Join our community

Actions22

Overview

The "Create Kanban Card" operation in the Workspace node allows users to create a new card on a Kanban board within the Workspace API. This is useful for task and project management scenarios where teams track work items visually using Kanban methodology. Users can specify details such as title, description, due date, priority, checklist items, and assign responsible users.

Practical examples include:

  • Adding a new task card to a project board with a deadline and priority.
  • Creating a bug report card with checklist steps for resolution.
  • Assigning a feature development card to a specific team member with status tracking.

Properties

Name Meaning
Kanban Card Data Collection of fields describing the Kanban card to create.
- Title Title of the Kanban card (required).
- Creator ID Unique identifier of the user creating the card (required).
- Description Detailed description of the card.
- Done Boolean indicating if the card is initially completed (required).
- Due Date Due date for the card in ISO 8601 format.
- Priority Priority level of the card; options: High, Normal, Low.
- Responsible User ID Unique identifier of the user responsible for the card.
- Status Initial status of the card; if omitted, defaults to the first available status.
- Checklist Entries List of checklist items; each item is a string representing a single checklist entry.

Output

The node outputs JSON data representing the newly created Kanban card as returned by the Workspace API. This typically includes all the properties sent plus additional metadata such as unique card ID, timestamps, and possibly links or references to related resources.

If binary data were involved (not indicated here), it would represent attachments or files associated with the card, but this operation focuses on JSON data only.

Dependencies

  • Requires an API key credential and tenant information for authenticating with the Workspace API.
  • The node expects the Workspace API base URL and authentication headers to be configured in the n8n credentials.
  • No other external dependencies are indicated.

Troubleshooting

  • Missing Required Fields: Errors may occur if required fields like "Title", "Creator ID", or "Done" are not provided. Ensure these are set before execution.
  • Invalid Dates: The "Due Date" must be in valid ISO 8601 format; otherwise, the API may reject the request.
  • Authentication Failures: Verify that the API key and tenant credentials are correctly configured and have sufficient permissions.
  • Status Field Issues: If an invalid or unavailable status is provided, the API might default to the first available status or return an error.
  • Checklist Format: Checklist entries must be provided as an array of strings; incorrect formatting could cause errors.

Links and References

Discussion