WTS Chat icon

WTS Chat

Get data from Wts API

Actions39

Overview

The Panel → Update Card operation in this n8n node allows you to update specific fields of a card within a panel (CRM board) in the WTS Chat system. This is useful for automating CRM workflows, such as updating deal information, changing responsible users, moving cards between steps, or modifying custom fields and metadata based on triggers or other automation logic.

Practical examples:

  • Automatically update a card's status or assign it to a new user when a lead reaches a certain stage.
  • Change the monetary amount or due date of a deal card after receiving updated information from another system.
  • Add or remove tags, update descriptions, or attach additional contacts to a card as part of a sales process.

Properties

Below are the supported input properties for the "Update Card" operation, with their display names, types, and meanings:

Display Name Type Meaning
Fields multiOptions Select which fields you want to update on the card. Only selected fields will be updated.
Card ID string The unique identifier of the card you wish to update.
Include Archived boolean Whether to include archived items (shown if "Archived" is selected in Fields).
Contacts ID collection List of contact IDs to associate with the card (shown if "ContactIds" is selected in Fields).
Custom Fields fixedCollection Key-value pairs for custom fields to update (shown if "CustomFields" is selected in Fields).
Description string New description for the card (shown if "Description" is selected in Fields).
Due Date dateTime Set or update the card's due date (shown if "DueDate" is selected in Fields).
Monetary Amount number Set or update the monetary value associated with the card (shown if "MonetaryAmount" is selected in Fields).
Position number Set the position/order of the card (shown if "Position" is selected in Fields).
User Name or ID options Assign a responsible user by selecting from a list or specifying an ID (shown if "ResponsibleUserId" is selected in Fields).
Step ID string Move the card to a different step/stage (shown if "StepId" is selected in Fields).
Tag Names or IDs multiOptions Add or update tags on the card (shown if "TagIds" is selected in Fields).
Title string Update the card's title (shown if "Title" is selected in Fields).
Session ID string Associate a session ID with the card (shown if "SessionId" is selected in Fields).
Metadata fixedCollection Key-value pairs for additional metadata (shown if "Metadata" is selected in Fields).

Note: Only the fields selected in the "Fields" property will be updated; others will remain unchanged.

Output

The output is a single item per execution, with the following structure:

{
  "json": {
    // The updated card object as returned by the WTS API.
    // Example fields may include:
    "id": "string",
    "title": "string",
    "description": "string",
    "monetaryAmount": "number",
    "position": "number",
    "stepId": "string",
    "dueDate": "string",
    "tagIds": ["string"],
    "responsibleUserId": "string",
    "contactIds": ["string"],
    "customFields": { /* key-value pairs */ },
    "metadata": { /* key-value pairs */ },
    // ...other card fields depending on what was updated and returned by the API
  }
}
  • The exact structure depends on the WTS API response, but it will always be under the json property.
  • No binary data is produced by this operation.

Dependencies

  • External Service: Requires access to the WTS Chat API.
  • API Key: You must configure valid credentials (wtsApi) in n8n with your WTS API key.
  • n8n Configuration: No special environment variables beyond standard credential setup.

Troubleshooting

Common Issues:

  • Missing Card ID: If "Card ID" is empty, the node will throw an error:
    "Fill in CardID"
  • No Fields Selected: If no fields are selected in "Fields", the node will throw an error:
    "Fill in Fields"
  • Invalid Field Values: If required values for selected fields are missing, the node may throw errors indicating which field is missing or invalid.
  • API Errors: Any issues with authentication or connectivity to the WTS API will result in an error message from the API, wrapped by n8n.

How to resolve:

  • Ensure all required fields are filled out, especially "Card ID" and at least one field in "Fields".
  • Double-check that your API credentials are correct and have sufficient permissions.
  • For custom fields or tags, ensure the IDs/names exist in your WTS system.

Links and References

Discussion