Actions19
- Agent Actions
- Campaign Actions
- Contact Actions
- Custom Field Actions
- Label Actions
- WhatsApp Actions
Overview
This node integrates with the Wasapi API, specifically providing functionality to update a custom field within the Wasapi system. It is useful when you need to modify existing custom fields dynamically as part of an automation workflow, such as updating metadata or attributes associated with contacts, tickets, or other entities managed via Wasapi.
A practical example would be updating the name of a custom field after a user input or external event triggers a change in your CRM or support system, ensuring that the custom field labels remain relevant and accurate.
Properties
| Name | Meaning |
|---|---|
| Custom Field ID | The unique identifier of the custom field to update. This tells the node which specific custom field should be modified. |
| Field Name | The new name to assign to the custom field. This updates the label or title of the custom field in the Wasapi system. |
Output
The node outputs JSON data representing the result of the update operation on the custom field. This typically includes confirmation details such as the updated custom field's ID, name, and possibly other metadata returned by the Wasapi API.
If the node supports binary data output (not indicated here), it would represent any file or media content related to the custom field update, but this is not applicable based on the provided code and properties.
Dependencies
- Requires an active connection to the Wasapi API.
- Needs an API authentication token or API key credential configured in n8n for accessing Wasapi services.
- The base URL for API requests is
https://api-ws.wasapi.io/api/v1. - Relies on helper modules and an operation factory internally to handle the execution logic for different resources and operations.
Troubleshooting
Common Issues:
- Invalid or missing Custom Field ID will cause the update to fail because the node cannot identify which field to update.
- Incorrect API credentials or expired tokens will result in authentication errors.
- Network connectivity issues can prevent communication with the Wasapi API endpoint.
Error Messages:
"Resource "customFields" with operation "update" is not supported": This indicates either a misconfiguration in resource or operation parameters or that the operation is not implemented. Verify the resource and operation names are correct.- Authentication errors usually mention invalid credentials or unauthorized access; ensure the API key/token is valid and has sufficient permissions.
- Validation errors from the API may indicate that the new field name does not meet Wasapi’s requirements (e.g., length or character restrictions).
Links and References
- Wasapi Official API Documentation (for detailed API endpoints and payload structures)
- n8n Documentation on Creating Custom Nodes (for understanding how nodes interact with APIs)
- General REST API best practices for error handling and authentication management