Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The node interacts with the "Panel" resource of the WTS API, specifically supporting the operation to duplicate a card within a panel. This operation allows users to create a copy of an existing card and optionally archive the original card. It also supports selecting which fields from the original card should be included in the duplicated card.
This node is beneficial in scenarios where workflow automation requires replicating tasks, items, or cards in project management or CRM panels without manually recreating all details. For example, duplicating a task card to assign it to a different step or user while preserving key information like tags, contacts, or custom fields.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to duplicate. |
| Step ID | The ID of the step (or column) where the duplicated card will be placed. |
| Archive Original Card | Boolean flag indicating whether the original card should be archived after duplication. |
| Fields | Specifies which fields to include in the duplicated card. Options: All, Amount, Contacts, CustomFields, DueDate, MonetaryAmount, Notes, ResponsibleUser, Tags, Undefined |
Output
The output is a JSON object representing the duplicated card as returned by the WTS API. It contains the details of the newly created card including its identifiers, assigned step, and any included fields as specified in the input.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the WTS API.
- The node uses the
WtsCrmService.duplicateCardmethod internally to perform the duplication via the API. - Proper configuration of the API base URL and credentials in n8n is necessary.
Troubleshooting
- Missing Card ID: If the "Card ID" property is empty or not provided, the node throws an error stating "CardID is empty, please fill it in". Ensure this field is correctly set.
- API Errors: Any errors returned by the WTS API during duplication are wrapped and thrown as node errors. Check the API key validity and network connectivity.
- Invalid Step ID: Providing an invalid or non-existent Step ID may cause the duplication to fail or place the card incorrectly.
- Field Selection: Selecting incompatible or unsupported fields in the "Fields" property might result in incomplete duplication or API errors.
Links and References
- WTS API Documentation (general reference for the API endpoints)
- n8n documentation on Creating Custom Nodes
- Panel and Card management concepts in WTS CRM systems (refer to your platform's user guide)