Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Create Card" operation under the "Panel" resource allows users to create a new card within a specified panel step in a CRM-like system. This node is useful for managing tasks, projects, or workflows where cards represent individual items or actions that need tracking. Users can assign responsibility, add tags, link contacts, set monetary values, and include custom fields and metadata.
Practical examples:
- Creating a task card in a project management board with assigned team member and due date.
- Adding a sales opportunity card linked to a contact with estimated revenue.
- Logging a support ticket card with relevant tags and detailed description.
Properties
| Name | Meaning |
|---|---|
| Responsible Name or ID | Select or specify the user responsible for the card. Optionally choose from a list or provide an expression. |
| Contact ID | Specify the ID of a contact to associate with the card. |
| Panel Name or ID | Choose or specify the panel where the card will be created. |
| Step Name or ID | Choose or specify the step within the panel where the card belongs. |
| Tag Names or IDs | Select multiple tags to categorize or label the card. Options depend on the selected step. |
| Title | The title or name of the card. This is a required field. |
| Description | A detailed description of the card's content or purpose. |
| Monetary Amount | A numeric value representing an amount related to the card (e.g., budget, cost, revenue). |
| Position | Numeric position/order of the card within the step. |
| Custom Fields | Add one or more custom key-value pairs specific to the panel. Keys are selectable or can be expressions. |
| Metadata | Add additional metadata as key-value pairs to store extra information about the card. |
Output
The output JSON contains the response from the API after creating the card. It typically includes details of the newly created card such as its ID, title, description, associated tags, responsible user, monetary amount, position, custom fields, metadata, and other relevant attributes returned by the service.
If binary data were involved (not applicable here), it would represent files or attachments related to the card.
Dependencies
- Requires an active connection to the WTS API via an API key credential.
- The node depends on the external WTS CRM service endpoints to create cards.
- Proper configuration of credentials in n8n is necessary to authenticate API requests.
Troubleshooting
- Missing Required Fields: Errors occur if the panel step or title is not provided. Ensure these fields are filled.
- Invalid Responsible User: If the responsible user ID is invalid or not found, the API may reject the request.
- API Key Issues: Authentication errors happen if the API key is missing, expired, or incorrect.
- Tag or Custom Field Loading: If dependent options like tags or custom fields fail to load, verify the panel and step selections are correct.
- Network or Service Errors: General API failures should be checked for network connectivity or service availability.
Common error messages:
"Choose a panel and its step": Indicates missing or invalid panel/step selection."Title is empty, please fill it in": The card title is mandatory.- API authentication errors: Check API key validity and permissions.
Links and References
- n8n Expressions Documentation
- WTS API documentation (not publicly linked here; refer to your service provider)
- n8n official docs on Credentials and HTTP Request Node for understanding API integrations