Actions38
- 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 management 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.
Typical use cases include:
- Updating task details when a status changes.
- Assigning or reassigning responsible users.
- Adding or modifying tags and custom metadata for better categorization.
- Adjusting card position or monetary values related to the card.
- Archiving or unarchiving cards based on workflow conditions.
For example, a project management automation could update a card's due date and responsible user when a task is reassigned or delayed.
Properties
| Name | Meaning |
|---|---|
| Fields | Select which fields to update on the card. Options: Archived, ContactIds, CustomFields, Description, DueDate, MonetaryAmount, Position, ResponsibleUserId, SessionId, StepId, TagIds, Title |
| Card ID | The unique identifier of the card to update. |
| Include Archived | Whether to include archived items (only shown if "Archived" field is selected). |
| Contacts ID | List of contact IDs to associate with the card (shown if "ContactIds" field is selected). |
| Custom Fields | Key-value pairs for custom fields to update on the card (shown if "CustomFields" field is selected). The keys can be selected from existing custom fields linked to the card. |
| Description | Text description of the card (shown if "Description" field is selected). |
| Due Date | Due date and time for the card in YYYY-MM-DD hh:mm format (shown if "DueDate" field is selected). |
| Monetary Amount | Numeric value representing monetary amount related to the card (shown if "MonetaryAmount" field is selected). |
| Position | Numeric position/order of the card within its step or panel (shown if "Position" field is selected). |
| User Name or ID | Responsible user assigned to the card. Can be chosen from a list or specified by ID (shown if "ResponsibleUserId" field is selected). |
| Step ID | Identifier of the step/stage the card belongs to (shown if "StepId" field is selected). |
| Tag Names or IDs | Tags associated with the card. Multiple tags can be selected or specified by ID (shown if "TagIds" field is selected). |
| Title | Title or name of the card (shown if "Title" field is selected). |
| Session ID | Identifier of the session related to the card (shown if "SessionId" field is selected). |
| Metadata | Additional key-value metadata pairs to attach to the card. |
Output
The node outputs an array with one item containing a json object representing the updated card data returned from the API after the update operation. This JSON includes all relevant fields of the card as updated, such as IDs, titles, descriptions, dates, tags, custom fields, metadata, and other properties.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the WTS API service via an API key credential.
- The node uses the WTS CRM service API endpoints to perform card updates.
- Proper permissions and valid card IDs are necessary to successfully update cards.
- Some fields like custom fields and tags require loading options dynamically from the API, so network connectivity and correct API configuration are essential.
Troubleshooting
- Missing Card ID: If the Card ID is not provided, the node will throw an error indicating that the Card ID must be filled in.
- Empty Fields Selection: If no fields are selected to update, the node will throw an error asking to fill in the fields.
- Invalid Field Values: Providing invalid values for fields like dates or user IDs may cause API errors.
- API Errors: Network issues, invalid API keys, or permission problems will result in API errors wrapped as node errors.
- Custom Fields Loading: If custom fields do not load properly, ensure the card ID is correct and the API credentials have access to fetch these fields.
- Tags Loading: Similar to custom fields, tag options depend on the card ID and API access.
To resolve errors:
- Verify all required parameters are set.
- Check API key validity and permissions.
- Confirm card ID exists and is accessible.
- Ensure proper formatting for dates and numeric fields.
- Review API response messages for specific error details.
Links and References
- WTS API Documentation (general reference for API endpoints)
- n8n Expressions Documentation (for using expressions in property fields)
- WTS CRM Service - Cards API (if available, for detailed card update API info)