Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Update Card" operation in the Panel resource allows users to modify various attributes of a card within a panel system. This node is useful for workflows that need to programmatically update task or project cards with new information such as title, description, due date, assigned users, tags, custom fields, and metadata.
Common scenarios include:
- Updating task details when new information becomes available.
- Changing the responsible user or reassigning tasks.
- Adding or modifying tags and custom fields to better categorize or describe the card.
- Adjusting the position or step of the card within a workflow.
- Archiving or unarchiving cards based on status changes.
Practical example: Automatically update a project management card's due date and responsible user when a related event occurs, ensuring the team stays informed and deadlines are adjusted dynamically.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to update. |
| Fields | The list of card fields to update. Options include: Archived, ContactIds, CustomFields, Description, DueDate, Metadata, MonetaryAmount, Position, ResponsibleUserId, SessionId, StepId, TagIds, Title. |
| Include Archived | Whether to include archived items (only applicable if updating the "Archived" field). |
| Contacts ID | List of contact IDs to associate with the card (applicable if updating "ContactIds"). |
| Custom Fields | Key-value pairs for custom fields to set on the card (applicable if updating "CustomFields"). Keys can be selected from existing custom fields linked to the card. |
| Description | Text description of the card (applicable if updating "Description"). |
| Due Date | Due date and time for the card in YYYY-MM-DD hh:mm format according to the user's timezone (applicable if updating "DueDate"). |
| Monetary Amount | Numeric monetary value associated with the card (applicable if updating "MonetaryAmount"). |
| Position | Numeric position of the card within its step or panel (applicable if updating "Position"). |
| User Name or ID | Responsible user for the card; can be selected from a list or specified by ID (applicable if updating "ResponsibleUserId"). |
| Step ID | Identifier of the step within the panel where the card belongs (applicable if updating "StepId"). |
| Tag Names or IDs | Tags to assign to the card; can be selected from a list or specified by IDs (applicable if updating "TagIds"). |
| Title | Title of the card (applicable if updating "Title"). |
| Session ID | Identifier of the session associated with the card (applicable if updating "SessionId"). |
| Metadata | Key-value pairs of metadata to attach to the card (applicable if updating "Metadata"). |
Output
The node outputs an array of JSON objects representing the updated card(s). Each output item contains the full response from the API after updating the card, including all updated fields and their current values.
If binary data were involved (not applicable here), it would represent files or attachments related to the card, but this operation deals only with JSON data.
Dependencies
- Requires an API key credential for authenticating requests to the external WTS API service.
- The node depends on the WTS CRM service module to perform card updates.
- Proper configuration of the API base URL and credentials in n8n is necessary.
Troubleshooting
- Missing Card ID: If the Card ID is not provided or empty, the node throws an error prompting to fill in the Card ID.
- No Fields Selected: If no fields are selected to update, the node will throw an error asking to fill in the fields.
- Invalid Field Values: Ensure that values for fields like dates, numbers, and IDs are valid and correctly formatted.
- API Errors: Any errors returned by the external API during the update process are caught and reported as node errors.
- Metadata and Custom Fields Handling: Metadata and custom fields must be provided as key-value pairs; improper formatting may cause errors.
- Include Archived Usage: The "Include Archived" option only applies when updating the "Archived" field; using it otherwise has no effect.
Links and References
- WTS API Documentation (generic reference, replace with actual link if available)
- n8n Expressions Documentation - for dynamic expressions used in property inputs
- Working with Custom Fields (hypothetical link for understanding custom fields usage)
This summary is based solely on static analysis of the provided source code and input properties definition.